summaryrefslogtreecommitdiffstats
path: root/arch/arm/mach-sunxi
diff options
context:
space:
mode:
authorThomas Petazzoni <thomas.petazzoni@free-electrons.com>2013-05-24 11:44:53 +0200
committerJason Cooper <jason@lakedaemon.net>2013-05-27 15:33:22 +0000
commit7a2c9bb57dc7298d3e545a8ca487b77d8ef3cc24 (patch)
treef44effb44169300b4d41e28a6c0bb10b00157782 /arch/arm/mach-sunxi
parent3d98a7884bff06fd34079461771f4630188e57a3 (diff)
downloadtalos-obmc-linux-7a2c9bb57dc7298d3e545a8ca487b77d8ef3cc24.tar.gz
talos-obmc-linux-7a2c9bb57dc7298d3e545a8ca487b77d8ef3cc24.zip
arm: kirkwood: nsa310: 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> Signed-off-by: Jason Cooper <jason@lakedaemon.net>
Diffstat (limited to 'arch/arm/mach-sunxi')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud