arm: kirkwood: ts219: move pinmux configs to the right devices
authorThomas Petazzoni <thomas.petazzoni@free-electrons.com>
Fri, 24 May 2013 09:44:56 +0000 (11:44 +0200)
committerJason Cooper <jason@lakedaemon.net>
Mon, 27 May 2013 15:34:23 +0000 (15:34 +0000)
commita4936cfa5dcd4ef9b40857ac415bb83865dc4225
tree0584cf399af86b02fd00e88bbc1f92abe5169683
parentfaf76128a815cdbdb516924640579366befa6f01
arm: kirkwood: ts219: 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: Andrew Lunn <andrew@lunn.ch>
Signed-off-by: Jason Cooper <jason@lakedaemon.net>
arch/arm/boot/dts/kirkwood-ts219-6281.dts
arch/arm/boot/dts/kirkwood-ts219-6282.dts
arch/arm/boot/dts/kirkwood-ts219.dtsi