From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: 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, 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:46:21 +0200 [thread overview]
Message-ID: <aPIQbaoNyXEcX2tn@shikoro> (raw)
In-Reply-To: <96d66ea4890b5f0d5c0961f8c8fac781a15865b9.camel@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 682 bytes --]
> > 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.
Thanks for the pointer, but this is too much side-tracking for me ;)
> > 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...
:(
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-10-17 9:46 UTC|newest]
Thread overview: 35+ 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-11-03 14:53 ` Krzysztof Kozlowski
2025-11-03 15:12 ` Wolfram Sang
2025-11-03 15:13 ` Krzysztof Kozlowski
2025-11-03 17:10 ` Wolfram Sang
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
2025-10-17 9:46 ` Wolfram Sang [this message]
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
2025-11-03 15:08 ` Krzysztof Kozlowski
2025-11-03 15:25 ` Wolfram Sang
2025-11-03 15:26 ` Krzysztof Kozlowski
2025-11-03 15:12 ` Krzysztof Kozlowski
2025-11-03 15:23 ` Wolfram Sang
2025-11-03 15:26 ` Krzysztof Kozlowski
2025-11-03 15:52 ` Wolfram Sang
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=aPIQbaoNyXEcX2tn@shikoro \
--to=wsa+renesas@sang-engineering.com \
--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=p.zabel@pengutronix.de \
/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