summaryrefslogtreecommitdiff
path: root/arch/arm/boot/dts/kirkwood-ns2max.dts
diff options
context:
space:
mode:
authorThomas Petazzoni <thomas.petazzoni@free-electrons.com>2013-05-24 11:44:47 +0200
committerJason Cooper <jason@lakedaemon.net>2013-05-27 15:32:25 +0000
commit4d05871a78399535faabc209800f2f22444cd7d4 (patch)
treeb021a98dc8e06b7658c6b3b114fccb44f8c46c22 /arch/arm/boot/dts/kirkwood-ns2max.dts
parentedd2718f15b157e3200fcbc8bbc4df31ac476cbb (diff)
arm: kirkwood: iomega ix2-200: move pinmux configs to the right devices
When the pinmux mechanism was added in Kirkwood, the device driver core was not yet providing the possibility of attaching pinmux configurations to all devices, drivers had to do it explicitly, and not all drivers were doing this. Now that the driver core does that in a generic way, it makes sense to attach the pinmux configuration to their corresponding devices. Note that some of the LEDs pinmux configurations are kept in the pinctrl node, because they are not used by the gpio-leds driver. This allows the pinctrl subsystem to show in debugfs to which device is related which pins, for example: pin 41 (PIN41): gpio-leds.1 mvebu-gpio:41 function gpio group mpp41 pin 42 (PIN42): gpio-leds.1 mvebu-gpio:42 function gpio group mpp42 pin 43 (PIN43): gpio-leds.1 mvebu-gpio:43 function gpio group mpp43 Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Acked-by: Andrew Lunn <andrew@lunn.ch> Signed-off-by: Jason Cooper <jason@lakedaemon.net>
Diffstat (limited to 'arch/arm/boot/dts/kirkwood-ns2max.dts')
0 files changed, 0 insertions, 0 deletions