arm: kirkwood: openblocks_a6: move pinmux configs to the right devices
authorThomas Petazzoni <thomas.petazzoni@free-electrons.com>
Fri, 24 May 2013 09:44:54 +0000 (11:44 +0200)
committerJason Cooper <jason@lakedaemon.net>
Mon, 27 May 2013 15:33:32 +0000 (15:33 +0000)
commitc5a36c96583a01a7994f90d0a5ecd0fd7d815bfb
tree71a87c6c46a54f275dc9f8b662faa1e346b201ed
parent7a2c9bb57dc7298d3e545a8ca487b77d8ef3cc24
arm: kirkwood: openblocks_a6: 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.

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>
Tested-by: Atsushi Yamagata <yamagata@plathome.co.jp>
Signed-off-by: Jason Cooper <jason@lakedaemon.net>
arch/arm/boot/dts/kirkwood-openblocks_a6.dts