Re: [PATCH 1/6 v14] gpio: Add a block GPIO API to gpiolib

2013-01-31 Thread Linus Walleij
On Mon, Jan 28, 2013 at 12:30 PM, Stijn Devriendt wrote: > This is one of the warts of the GPIO API, if you ask me (and probably > others too). > Using a resource without allocating it first is just asking for > trouble. It's one of those > things pinctl was designed to solve... I've been thinkin

Re: [PATCH 1/6 v14] gpio: Add a block GPIO API to gpiolib

2013-01-28 Thread Stijn Devriendt
On Sun, Jan 27, 2013 at 2:58 PM, Roland Stigge wrote: > On 27/01/13 14:19, Stijn Devriendt wrote: >>> +Block GPIO >>> +-- >>> + >>> +The above described interface concentrates on handling single GPIOs. >>> However, >>> +in applications where it is critical to set several GPIOs at once, t

Re: [PATCH 1/6 v14] gpio: Add a block GPIO API to gpiolib

2013-01-27 Thread Roland Stigge
On 27/01/13 14:19, Stijn Devriendt wrote: >> +Block GPIO >> +-- >> + >> +The above described interface concentrates on handling single GPIOs. >> However, >> +in applications where it is critical to set several GPIOs at once, this >> +interface doesn't work well, e.g. bit-banging protocols

Re: [PATCH 1/6 v14] gpio: Add a block GPIO API to gpiolib

2013-01-27 Thread Stijn Devriendt
On Tue, Jan 22, 2013 at 1:06 PM, Roland Stigge wrote: > The recurring task of providing simultaneous access to GPIO lines (especially > for bit banging protocols) needs an appropriate API. > > This patch adds a kernel internal "Block GPIO" API that enables simultaneous > access to several GPIOs. T

[PATCH 1/6 v14] gpio: Add a block GPIO API to gpiolib

2013-01-22 Thread Roland Stigge
The recurring task of providing simultaneous access to GPIO lines (especially for bit banging protocols) needs an appropriate API. This patch adds a kernel internal "Block GPIO" API that enables simultaneous access to several GPIOs. This is done by abstracting GPIOs to an n-bit word: Once requeste