From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-renesas-soc@vger.kernel.org,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] reset: always include RESET_GPIO driver if possible
Date: Thu, 23 Oct 2025 11:37:59 +0200 [thread overview]
Message-ID: <CAMRc=MejA6DsnOW3hS+aFtecXn38UypJU2TUrAWPoo9Ly341uw@mail.gmail.com> (raw)
In-Reply-To: <aPnz6U-fcodRoobU@shikoro>
On Thu, Oct 23, 2025 at 11:22 AM Wolfram Sang
<wsa+renesas@sang-engineering.com> wrote:
>
> Hi Philipp,
>
> > > > I dunno for how many drivers this is really applicable, but I really
> > > > liked the cleanup of the pca954x driver.
> >
> > That cleanup might have been a little premature, given that the reset-
> > gpio driver currently only works on OF-based platforms, and even there
> > only with gpio controllers with #gpio-cells = <2>.
>
> I see. That kind of spoils my assumption that it is a fallback supported
> by the core. Darn, I would still like to have it, but it seems more
> complicated than I have time for it :(
>
As soon as my two other reset series land in next, I will finish my
work on converting the reset core to fwnode which should help.
Bart
next prev parent reply other threads:[~2025-10-23 9:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 20:59 [PATCH v2 0/2] reset: handle RESET_GPIO better to provide the fallback Wolfram Sang
2025-10-15 20:59 ` [PATCH v2 1/2] reset: always bail out on missing RESET_GPIO driver Wolfram Sang
2025-10-17 9:35 ` Philipp Zabel
2025-10-30 11:59 ` Philipp Zabel
2025-10-30 12:54 ` Philipp Zabel
2025-10-15 20:59 ` [PATCH v2 2/2] reset: always include RESET_GPIO driver if possible Wolfram Sang
2025-10-16 13:02 ` Geert Uytterhoeven
2025-10-16 14:27 ` Wolfram Sang
2025-10-17 10:16 ` Bartosz Golaszewski
2025-10-17 10:48 ` Wolfram Sang
2025-10-17 11:09 ` Bartosz Golaszewski
2025-10-17 11:25 ` Wolfram Sang
2025-10-17 17:02 ` Bartosz Golaszewski
2025-10-22 9:07 ` Philipp Zabel
2025-10-23 9:22 ` Wolfram Sang
2025-10-23 9:37 ` Bartosz Golaszewski [this message]
2025-10-23 11:18 ` Wolfram Sang
2025-10-23 12:04 ` Bartosz Golaszewski
2025-10-23 12:51 ` Wolfram Sang
2025-10-17 9:42 ` Philipp Zabel
2025-10-17 9:46 ` Wolfram Sang
2025-10-17 9:35 ` Philipp Zabel
2025-10-17 9:43 ` Wolfram Sang
2025-10-16 0:02 ` [PATCH v2 0/2] reset: handle RESET_GPIO better to provide the fallback Kuninori Morimoto
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=MejA6DsnOW3hS+aFtecXn38UypJU2TUrAWPoo9Ly341uw@mail.gmail.com' \
--to=brgl@bgdev.pl \
--cc=geert@linux-m68k.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=wsa+renesas@sang-engineering.com \
/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).