From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Val Packett <val@packett.cool>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH] gpio: shared: handle the reset-gpios corner case
Date: Mon, 24 Nov 2025 16:36:12 +0100 [thread overview]
Message-ID: <CAMRc=MfQhu9GY2+3G+Ba71JnXUnU4akAfNbsMDnwkCRNzAXQCw@mail.gmail.com> (raw)
In-Reply-To: <CAMRc=MdW3AkkivE=sA4STZAmmee7bCBkD5oEsXiRcKA80Ggd4A@mail.gmail.com>
On Mon, Nov 24, 2025 at 9:38 AM Bartosz Golaszewski <brgl@bgdev.pl> wrote:
>
> On Sun, Nov 23, 2025 at 2:03 AM Val Packett <val@packett.cool> wrote:
> >
> > > ---
> > > This is targetting linux-next where the reset-gpio driver is now using
> > > the auxiliary bus and software nodes rather than the platform bus and
> > > GPIO machine lookup. The bug is the same in both cases but the fix would
> > > be completely different.
> > > ---
> > > [..]
> >
> > Tried applying only this, as well as this +
> > https://lore.kernel.org/all/20251120-reset-gpios-swnodes-v7-0-a100493a0f4b@linaro.org/
> > + https://lore.kernel.org/all/20251121135739.66528-1-brgl@bgdev.pl/ (on
> > top of next-20251120) and the issue is still present.. am I missing
> > something?
> >
>
> Can you try this branch?
>
> https://github.com/brgl/linux test/gpiolib-shared-reset-gpio-fix
>
> I confirmed it works on my setup and fixes the problem with multiple
> users of reset-gpio AND shared GPIOs enabled.
>
Actually linux-next got updated with all the prerequisites so you can
try this patch on top of next-20251124. I tested it and it works for
me. If it still doesn't for you, can you enable GPIO debug messages
and send me the entire kernel log?
Bartosz
next prev parent reply other threads:[~2025-11-24 15:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 13:46 [PATCH] gpio: shared: handle the reset-gpios corner case Bartosz Golaszewski
2025-11-23 1:03 ` Val Packett
2025-11-24 8:38 ` Bartosz Golaszewski
2025-11-24 15:36 ` Bartosz Golaszewski [this message]
2025-11-24 23:05 ` Val Packett
2025-11-25 10:20 ` Bartosz Golaszewski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMRc=MfQhu9GY2+3G+Ba71JnXUnU4akAfNbsMDnwkCRNzAXQCw@mail.gmail.com' \
--to=brgl@bgdev.pl \
--cc=bartosz.golaszewski@linaro.org \
--cc=krzk@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=val@packett.cool \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).