summaryrefslogtreecommitdiffstats
path: root/drivers/pinctrl/meson
diff options
context:
space:
mode:
authorLudovic Desroches <ludovic.desroches@microchip.com>2018-06-29 10:15:33 +0200
committerLinus Walleij <linus.walleij@linaro.org>2018-07-16 14:46:11 +0200
commitff10e353a4c0c83a28c89c182462b3c8dc7f70cc (patch)
tree332bb94416582cc5176ada527626285507ba694c /drivers/pinctrl/meson
parente12fa73c97a4c5fbc77b28e6436277fdc4f9b3b5 (diff)
downloadblackbird-op-linux-ff10e353a4c0c83a28c89c182462b3c8dc7f70cc.tar.gz
blackbird-op-linux-ff10e353a4c0c83a28c89c182462b3c8dc7f70cc.zip
pinctrl: at91-pio4: add support for drive strength
Add support for the drive strength configuration. Usually, this value is expressed in mA. Since the numeric value depends on VDDIOP voltage, a value we can't retrieve at runtime, the controller uses low, medium and high to define the drive strength. The PIO controller accepts two values for the low drive configuration: 0 and 1. Most of the time, we don't care about the drive strength. So we keep the default value which is 0. The drive strength is advertised through the sysfs only when it has been explicitly set in the device tree i.e. if its value is different from 0. Signed-off-by: Ludovic Desroches <ludovic.desroches@microchip.com> Acked-by: Rob Herring <robh@kernel.org> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Diffstat (limited to 'drivers/pinctrl/meson')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud