[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAMRc=McuAJLXdJq+=-bjCsjrSiWrrXr=A9NT+odX+E0P16VWjA@mail.gmail.com>
Date: Fri, 9 Jan 2026 10:36:52 +0100
From: Bartosz Golaszewski <brgl@...nel.org>
To: Linus Walleij <linusw@...nel.org>
Cc: Bartosz Golaszewski <bartosz.golaszewski@....qualcomm.com>,
Neil Armstrong <neil.armstrong@...aro.org>, Kevin Hilman <khilman@...libre.com>,
Jerome Brunet <jbrunet@...libre.com>,
Martin Blumenstingl <martin.blumenstingl@...glemail.com>, linux-gpio@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-amlogic@...ts.infradead.org,
linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH] pinctrl: meson: amlogic-a4: mark the GPIO controller as sleeping
On Fri, Jan 9, 2026 at 10:35 AM Linus Walleij <linusw@...nel.org> wrote:
>
> On Tue, Jan 6, 2026 at 9:53 AM Bartosz Golaszewski
> <bartosz.golaszewski@....qualcomm.com> wrote:
>
> > The GPIO controller is configured as non-sleeping but it uses generic
> > pinctrl helpers which use a mutex for synchronization. This will cause
> > lockdep splats when used together with shared GPIOs going through the
> > GPIO shared proxy driver.
>
> BTW it is a very *welcome* side-effect of the new shared GPIO rework
> that it just happens to find these old bugs, I'm very pleased with this :)
>
Actually, I was surprised I was getting so many bug reports and then
it turned out, there was a bug that caused a lot of false-positives to
turn up when scanning the devicetree for shared pins. I just queued a
fix for that so it should slow down now.
Bart
Powered by blists - more mailing lists