Messages in this thread | | | Date | Tue, 9 Aug 2011 12:11:51 +0200 | Subject | Re: [PATCH] GPIOLIB: add generic gpio_set_pull API | From | Linus Walleij <> |
| |
On Tue, Aug 9, 2011 at 3:45 AM, Rohit Vaswani <rvaswani@codeaurora.org> wrote:
> If we add this API - the remaining gpio controls like drive strength and > function select could also be added,
I agree.
> which eats into the pinmux domain.
That's not so bad, since the pinctrl/pinmux subsystem is just a prototype people may want to wrap up their drivers into gpio_chip/gpiolib as they stand today to atleast get some isolation. Later on they can refactor and migrate to a pinctrl/pinmux subsystem.
The latter will take some time to provide anyway, since I have been asked to restructure it so as not to use a global pin number space.
> Linus W. had a patch earlier which added an API for a gpio config to be > specified through gpiolib. " gpio: add a custom configuration mechanism to > gpiolib" which is sort of an extensible model of this API.
Yes I think I have already suggested a bunch of ways to skin this cat but somehow none of them seem to win general approval.
Yours, Linus Walleij
| |