1. 27 5月, 2013 1 次提交
    • T
      arm: kirkwood: ns2: move pinmux configs to the right devices · ef519a43
      Thomas Petazzoni 提交于
      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: NThomas Petazzoni <thomas.petazzoni@free-electrons.com>
      Acked-by: NAndrew Lunn <andrew@lunn.ch>
      Signed-off-by: NJason Cooper <jason@lakedaemon.net>
      ef519a43
  2. 22 11月, 2012 1 次提交