summaryrefslogtreecommitdiff
path: root/arch/arm/boot/dts/omap3-igep.dtsi
diff options
context:
space:
mode:
authorJavier Martinez Canillas <javier.martinez@collabora.co.uk>2013-06-20 16:42:30 +0200
committerBenoit Cousson <bcousson@baylibre.com>2013-10-08 17:51:39 +0200
commit00964a90728d752abe61ad134dac8c13491c3595 (patch)
tree2926c5005127fea3e8a8c5ad2919073f8c81c43b /arch/arm/boot/dts/omap3-igep.dtsi
parenta4d4b15363ea31236e557c471d9aa95202fed88a (diff)
ARM: dts: omap3-igep: add pinmux node for GPIO LED configuration
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.martinez@collabora.co.uk> Signed-off-by: Benoit Cousson <bcousson@baylibre.com>
Diffstat (limited to 'arch/arm/boot/dts/omap3-igep.dtsi')
-rw-r--r--arch/arm/boot/dts/omap3-igep.dtsi2
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 2326d11462a5..0f92224dc4fc 100644
--- a/arch/arm/boot/dts/omap3-igep.dtsi
+++ b/arch/arm/boot/dts/omap3-igep.dtsi
@@ -77,6 +77,8 @@
0x1a2 (PIN_INPUT | MUX_MODE4) /* mcspi1_cs2.gpio_176 */
>;
};
+
+ leds_pins: pinmux_leds_pins { };
};
&i2c1 {