From: Philipp Zabel <p.zabel@pengutronix.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-renesas-soc@vger.kernel.org,
	Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	linux-kernel@vger.kernel.org, Bartosz Golaszewski <brgl@bgdev.pl>
Subject: Re: [PATCH v2 2/2] reset: always include RESET_GPIO driver if possible
Date: Fri, 17 Oct 2025 11:42:42 +0200	[thread overview]
Message-ID: <96d66ea4890b5f0d5c0961f8c8fac781a15865b9.camel@pengutronix.de> (raw)
In-Reply-To: <CAMuHMdXqHncXxBZ00mxV=pzdgQEU4ju2F9XMejnibbu=QnLfDg@mail.gmail.com>
On Do, 2025-10-16 at 15:02 +0200, Geert Uytterhoeven wrote:
> Hi Wolfram,
> 
> On Thu, 16 Oct 2025 at 14:16, Wolfram Sang
> <wsa+renesas@sang-engineering.com> wrote:
> > Reset core uses the reset_gpio driver for a fallback mechanism. So,
> > include it always once its dependencies are met to enable the fallback
> > mechanism whenever possible. This avoids regressions when drivers remove
> > open coded solutions in favor of this fallback.
> > 
> > Reported-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> > Closes: https://lore.kernel.org/r/87a51um1y1.wl-kuninori.morimoto.gx@renesas.com
> > Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> 
> Thanks for your patch!
> 
> > --- a/drivers/reset/Kconfig
> > +++ b/drivers/reset/Kconfig
> > @@ -5,6 +5,7 @@ config ARCH_HAS_RESET_CONTROLLER
> >  menuconfig RESET_CONTROLLER
> >         bool "Reset Controller Support"
> >         default y if ARCH_HAS_RESET_CONTROLLER
> > +       select RESET_GPIO if GPIOLIB
> >         help
> >           Generic Reset Controller support.
> > 
> 
> Makes sense, so
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
> 
> This does mean RESET_GPIO will never be modular anymore, while it could
> still work as a module (the reset core creates the platform device,
> which can be probed later), albeit in a non-intuitive way.
Btw, Bartosz (added to Cc:) is reworking reset-gpio into an auxiliary
device driver.
[1] https://lore.kernel.org/all/20251006-reset-gpios-swnodes-v1-0-6d3325b9af42@linaro.org/
> BTW, could we run into a circular dependency?
> 
>     config RESET_TI_TPS380X
>             tristate "TI TPS380x Reset Driver"
>             select GPIOLIB
> 
> I guess this should be changed from select to depends on?
The drivers referencing GPIOLIB seem to be split in the middle between
select and depends...
regards
Philipp
next prev parent reply	other threads:[~2025-10-17  9:42 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
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 [this message]
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=96d66ea4890b5f0d5c0961f8c8fac781a15865b9.camel@pengutronix.de \
    --to=p.zabel@pengutronix.de \
    --cc=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=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).