[PATCH 1/2] gpio: add pin biasing and drive mode to gpiolib
Linus Walleij
linus.walleij at linaro.org
Wed Apr 20 08:38:01 EDT 2011
2011/4/20 Ben Nizette <bn at niasdigital.com>:
> On 19/04/2011, at 6:38 PM, Alan Cox wrote:
>> Leaving aside the current input/output and on/off bits I would go for
>> being able to do
>>
>> gpio_get_property(gpio, GPIO_BIAS, GPIO_BIAS_WHATEVER);
>> gpio_set_property(gpio, GPIO_BIAS, GPIO_BIAS_WHATEVER_ELSE);
>
> Yeah I'm all for that so long as the capability constants are defined by the gpio
> provider, eg <linux/gpio/mygpioexpander.h>. There's no way gpiolib should be
> keeping a big ole list of every possible config option for every gpio provider.
OK I buy that. I will refactor this solution to some opaque call instead
and start from there.
> Well, maybe gpiolib can know about the options (eg GPIO_BIAS) so long
> as it doesn't have to enumerate every possible value.
I will drop that even, one parameter is better than two if one of them
is custom nevertheless. What difference does it make..
Yours,
Linus Walleij
More information about the linux-arm-kernel
mailing list