Re: [PATCH 0/2] gpio: fix sleeping-in-atomic in shared-proxy; restore meson non-sleeping
Viacheslav <[email protected]>
| Newsgroups | org.infradead.lists.linux-amlogic,org.infradead.lists.linux-arm-kernel,org.infradead.lists.linux-rockchip,org.kernel.vger.linux-gpio,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
Hi! 24.06.2026 10:25, Bartosz Golaszewski wrote: > On Tue, 23 Jun 2026 17:16:44 +0200, Robin Murphy <[email protected]> said: >> On 11/06/2026 9:26 am, Marek Szyprowski wrote: >>> Hi Viachesla, >>> >>> On 10.06.2026 17:32, Viacheslav Bocharov wrote: >>>> gpio-shared-proxy chooses its descriptor lock (mutex vs spinlock) from >>>> the underlying chip's can_sleep, but under that lock it calls config and >>>> direction ops that reach sleeping pinctrl paths. On a controller with >>>> non-sleeping MMIO value ops the lock is a spinlock, so a sleeping call >>>> runs from atomic context: >>>> > > ... > >>> >>> I've checked this patchset with these two reverted and no warning was reported. >> >> If it hadn't already been fixed (...) >> > > About that - Viacheslav, do you still plan to submit v2 of this? Thanks for review. I prepared and sent the second version of the patch today > > Bart > > _______________________________________________ > linux-amlogic mailing list > [email protected] > http://lists.infradead.org/mailman/listinfo/linux-amlogic _______________________________________________ linux-amlogic mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-amlogic