[PATCH v2] leds: leds-gpio: adopt pinctrl support
linus.walleij at linaro.org
Fri Sep 7 17:57:59 EDT 2012
On Fri, Sep 7, 2012 at 6:00 PM, Domenico Andreoli <cavokz at gmail.com> wrote:
> On Fri, Sep 07, 2012 at 02:30:59PM +0000, AnilKumar, Chimata wrote:
>> How can gpio driver knows that leds-gpio driver require
>> these 4 pins?
> because leds-gpio requests each gpio (specified in the DT against a specific
> gpio controller) before assuming it is available? gpiolib then asks to
> pinctrl if those pins are available for gpio and possibly reserve them
> (configuring the mux, if necessary) for the device.
So this is not an either-or situation but a both-and case.
So all muxing and configuration of pins can be handled by
the pinctrl handle, and that may require setting up a single
pinctrl function for every single pin, and that list can get long.
But it works fine.
In that case you don't write your pinctrl driver to do anything
special with the GPIO callbacks, leave the
.gpio_request_enable(), .gpio_disable_free() and
.gpio_set_direction() callbacks in the vtable undefined.
If all you need to to is to multiplex the pins into GPIO mode,
then the gpio_get() call on this driver *can* call through to
pinctrl_request_gpio() which will in turn fall through to the
above pinmux driver calls (.gpio_request_enable, etc).
Likewise for pinctrl_free_gpio(), pinctrl_gpio_direction_input()
But that's as far as it goes! The GPIO abstraction cannot
call through to e.g. set some specific biasing on the pins
(pull up etc). Doing that would require us to reimplement
every interface that pinctrl already has again in the
GPIO layer, which is not a good idea.
So the pinctrl handle can be used for such config, and it
can also be used for multiplexing if that is desired - if not
done by the fall through functions pinctrl_gpio_*().
You can use a combination of both too, Stephen patched
pinctrl some time back so that a pin can be muxed for a
certain function and used as GPIO at the same time, so
these two are now orthogonal, it's a bit relaxed and gives some
feeling of loss of control but was necessary for certain
usecases. (For example we can snoop on a I2C pin using
its corresponding GPIO registers in the U300...)
There is some flexibility here, I hope it's not too confusing :-/
More information about the linux-arm-kernel