Messages in this thread |  | | Date | Thu, 27 Feb 2014 11:48:02 +0200 | From | Mika Westerberg <> | Subject | Re: [PATCH 1/6] gpiolib: Allow GPIO chips to request their own GPIOs |
| |
On Wed, Feb 26, 2014 at 02:47:58PM +0100, Rafael J. Wysocki wrote: > > Sounds good. Only thing I'm not sure about is the fact that > > __gpiod_request() releases the lock when it calls chip driver callbacks > > (and takes it back of course). Is that acceptable practice to take the lock > > outside of a function and release it inside for a while? > > Yes, you can do that. > > There even are sparse annotations for that: __releases() and __acquires() > (__rpm_callback() in drivers/base/power/runtime.c uses them among other things).
Ah, good to know. Thanks!
|  |