On Thu, Jun 20, 2013 at 4:42 PM, Javier Martinez Canillas
<javier.marti...@collabora.co.uk> wrote:
> IGEP boards have a number of LED connected to OMAP or TWL GPIO
> lines. The actual wiring is different on each board so each board
> DT has need to configure the mux correctly.
>
> Even though it works with the current DT, the kernel complains with:
>
> [2.305023] leds-gpio leds.18: pins are not configured from the driver
>
> Add an empty pinmux_leds_pins pinctrl child node so boards can
> override with the correct mux configuration and not depend on
> default values for the GPIO LEDs to work.
>
> Signed-off-by: Javier Martinez Canillas <javier.marti...@collabora.co.uk>
> ---
> arch/arm/boot/dts/omap3-igep.dtsi | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/boot/dts/omap3-igep.dtsi
> b/arch/arm/boot/dts/omap3-igep.dtsi
> index bc48b11..55f9f61 100644
> --- a/arch/arm/boot/dts/omap3-igep.dtsi
> +++ b/arch/arm/boot/dts/omap3-igep.dtsi
> @@ -68,6 +68,8 @@
> 0x1a2 (PIN_INPUT | MUX_MODE4) /*
> mcspi1_cs2.gpio_176 */
> >;
> };
> +
> + leds_pins: pinmux_leds_pins { };
> };
>
> &i2c1 {
> --
> 1.7.7.6
>
> --
Hi Benoit,
Any feedback about this patch-set?
Thanks a lot and best regards,
Javier
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
