[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aPIfF-3SgzW5V_gs@shikoro>
Date: Fri, 17 Oct 2025 12:48:55 +0200
From: Wolfram Sang <wsa+renesas@...g-engineering.com>
To: Bartosz Golaszewski <brgl@...ev.pl>
Cc: Geert Uytterhoeven <geert@...ux-m68k.org>,
linux-renesas-soc@...r.kernel.org,
Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
linux-kernel@...r.kernel.org,
Philipp Zabel <p.zabel@...gutronix.de>
Subject: Re: [PATCH v2 2/2] reset: always include RESET_GPIO driver if
possible
> > 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...
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists