[PATCH] gpio: extend gpiod_get*() with flags parameter

2014-07-25 Thread Alexandre Courbot
On Fri, Jul 25, 2014 at 1:23 AM, Laurent Pinchart wrote: >> diff --git a/Documentation/gpio/consumer.txt >> b/Documentation/gpio/consumer.txt index 7ff30d2..a3fb1d7 100644 >> --- a/Documentation/gpio/consumer.txt >> +++ b/Documentation/gpio/consumer.txt >> @@ -29,13 +29,24 @@ gpiod_get()

[PATCH] gpio: extend gpiod_get*() with flags parameter

2014-07-25 Thread Alexandre Courbot
On Fri, Jul 25, 2014 at 1:10 AM, Arnd Bergmann wrote: > On Friday 25 July 2014 00:04:58 Alexandre Courbot wrote: >> I'm not sure how this could be applied harmlessly though - maybe through >> a dedicated branch for -next? Problem is that a lot of new code is not >> yet merged into mainline, and

[PATCH] gpio: extend gpiod_get*() with flags parameter

2014-07-25 Thread Lee Jones
On Thu, 24 Jul 2014, Greg Kroah-Hartman wrote: > On Fri, Jul 25, 2014 at 12:04:58AM +0900, Alexandre Courbot wrote: > > The huge majority of GPIOs have their direction and initial value set > > right after being obtained by one of the gpiod_get() functions. The > > integer GPIO API had

[PATCH] gpio: extend gpiod_get*() with flags parameter

2014-07-25 Thread Alexandre Courbot
The huge majority of GPIOs have their direction and initial value set right after being obtained by one of the gpiod_get() functions. The integer GPIO API had gpio_request_one() that took a convenience flags parameter allowing to specify an direction and value applied to the returned GPIO. This

[PATCH] gpio: extend gpiod_get*() with flags parameter

2014-07-24 Thread Laurent Pinchart
Hi Alexandre, Thank you for the patch. On Friday 25 July 2014 00:04:58 Alexandre Courbot wrote: > The huge majority of GPIOs have their direction and initial value set > right after being obtained by one of the gpiod_get() functions. The > integer GPIO API had gpio_request_one() that took a

[PATCH] gpio: extend gpiod_get*() with flags parameter

2014-07-24 Thread Arnd Bergmann
On Friday 25 July 2014 00:04:58 Alexandre Courbot wrote: > I'm not sure how this could be applied harmlessly though - maybe through > a dedicated branch for -next? Problem is that a lot of new code is not > yet merged into mainline, and conflicts are very likely to occur. Linus, > do you have any

[PATCH] gpio: extend gpiod_get*() with flags parameter

2014-07-24 Thread Greg Kroah-Hartman
On Fri, Jul 25, 2014 at 12:04:58AM +0900, Alexandre Courbot wrote: > The huge majority of GPIOs have their direction and initial value set > right after being obtained by one of the gpiod_get() functions. The > integer GPIO API had gpio_request_one() that took a convenience flags > parameter