Re: [PATCH] gpiolib: fix a few issues with gpiochip_remove

2014-09-24 Thread Octavian Purdila
On Wed, Sep 24, 2014 at 11:51 AM, Linus Walleij wrote: > On Fri, Sep 5, 2014 at 5:22 PM, Octavian Purdila > wrote: > >> The current implementation of gpiochip_remove() does not check to see >> if the GPIO pins are busy before removing the associated irqchip and >> this is causing the following wa

Re: [PATCH] gpiolib: fix a few issues with gpiochip_remove

2014-09-24 Thread Linus Walleij
On Fri, Sep 5, 2014 at 5:22 PM, Octavian Purdila wrote: > The current implementation of gpiochip_remove() does not check to see > if the GPIO pins are busy before removing the associated irqchip and > this is causing the following warning: (...) > A retry operation is needed in the case of MFD de

Re: [PATCH] gpiolib: fix a few issues with gpiochip_remove

2014-09-19 Thread Octavian Purdila
On Fri, Sep 19, 2014 at 11:31 AM, Alexandre Courbot wrote: > On Sat, Sep 6, 2014 at 12:22 AM, Octavian Purdila > wrote: >> The current implementation of gpiochip_remove() does not check to see >> if the GPIO pins are busy before removing the associated irqchip and >> this is causing the following

Re: [PATCH] gpiolib: fix a few issues with gpiochip_remove

2014-09-19 Thread Alexandre Courbot
On Sat, Sep 6, 2014 at 12:22 AM, Octavian Purdila wrote: > The current implementation of gpiochip_remove() does not check to see > if the GPIO pins are busy before removing the associated irqchip and > this is causing the following warning: > > WARNING: CPU: 3 PID: 553 at fs/proc/generic.c:521 >

[PATCH] gpiolib: fix a few issues with gpiochip_remove

2014-09-05 Thread Octavian Purdila
The current implementation of gpiochip_remove() does not check to see if the GPIO pins are busy before removing the associated irqchip and this is causing the following warning: WARNING: CPU: 3 PID: 553 at fs/proc/generic.c:521 remove_proc_entry+0x19f/0x1b0() remove_proc_entry: removing non-empty