linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
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,
	Philipp Zabel <p.zabel@pengutronix.de>
Subject: Re: [PATCH v2 2/2] reset: always include RESET_GPIO driver if possible
Date: Fri, 17 Oct 2025 12:48:55 +0200	[thread overview]
Message-ID: <aPIfF-3SgzW5V_gs@shikoro> (raw)
In-Reply-To: <CAMRc=McsbAirEYjoo455mbKU495VEvPmMEqBmZCq2hw113YHOg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 977 bytes --]


> > Interesting topic. In fact, I think we should make RESET_GPIO bool. I
> > think the fallback mechanism of the core should work without any module
> > loading infrastructure. It should be there whenever possible.
> >
> 
> You have not said *why*. How is this different from any other device
> whose driver is only loaded when actually needed?

? I just did that, but let me repeat:

I think the fallback mechanism of the core should work without any
module loading infrastructure. It should be there whenever possible.

I might add that module loading infrastructure might be broken in
userspace. Been there. Also, some drivers might need their reset early?

Looking more into it, I can't find any 'request_module'. Am I
overlooking something? The fallback feature is only present if the user
loads the driver manually? If that is true, it would make it rather
useless IMHO because consumer drivers cannot rely on it. I must be
missing something...


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2025-10-17 10:48 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 [this message]
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
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=aPIfF-3SgzW5V_gs@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;
as well as URLs for NNTP newsgroup(s).