Re: [PATCH 3/4] gpio: max732x: Fix possible deadlock

2015-01-15 Thread Linus Walleij
On Tue, Jan 13, 2015 at 2:41 PM, Semen Protsenko wrote: > This patch was derived from next one: > "gpio: fix pca953x set_type 'scheduling while atomic' bug". > > After adding entry that consumes max732x GPIO as interrupt line to dts > file, deadlock appears somewhere in max732x probe function.

Re: [PATCH 3/4] gpio: max732x: Fix possible deadlock

2015-01-15 Thread Linus Walleij
On Tue, Jan 13, 2015 at 2:41 PM, Semen Protsenko semen.protse...@globallogic.com wrote: This patch was derived from next one: gpio: fix pca953x set_type 'scheduling while atomic' bug. After adding entry that consumes max732x GPIO as interrupt line to dts file, deadlock appears somewhere in

[PATCH 3/4] gpio: max732x: Fix possible deadlock

2015-01-13 Thread Semen Protsenko
This patch was derived from next one: "gpio: fix pca953x set_type 'scheduling while atomic' bug". After adding entry that consumes max732x GPIO as interrupt line to dts file, deadlock appears somewhere in max732x probe function. Deadlock caught by lockdep (from kernel log):

[PATCH 3/4] gpio: max732x: Fix possible deadlock

2015-01-13 Thread Semen Protsenko
This patch was derived from next one: gpio: fix pca953x set_type 'scheduling while atomic' bug. After adding entry that consumes max732x GPIO as interrupt line to dts file, deadlock appears somewhere in max732x probe function. Deadlock caught by lockdep (from kernel log): cut here [