[PATCH] pinctrl: meson: amlogic-a4: mark the GPIO controller as sleeping

Bartosz Golaszewski brgl at kernel.org
Tue Jan 6 02:40:30 PST 2026


On Tue, Jan 6, 2026 at 10:32 AM Xianwei Zhao <xianwei.zhao at amlogic.com> wrote:
>
> Hi Bartosz,
>     Could you explain the reproduction method for this problem ?
>

Please don't top-post on the mailing list.

If you have a pin shared by multiple devices in device-tree, it will
now go through a dedicated gpio-shared-proxy driver. It will use a
locking mechanism depending on the can_sleep flag of the GPIO
controller device - spinlock or mutex. If the flag is wrong - like is
the case here - it may happen that we take a spinlock and then descend
into pinctrl where a mutex is taken resulting in a lockdep splat.

Bart



More information about the linux-amlogic mailing list