[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0a347beb6d3b6adea2f9c78721d33732b8e85724.camel@pengutronix.de>
Date: Fri, 17 Oct 2025 11:35:14 +0200
From: Philipp Zabel <p.zabel@...gutronix.de>
To: Wolfram Sang <wsa+renesas@...g-engineering.com>,
linux-renesas-soc@...r.kernel.org
Cc: Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>, Krzysztof
Kozlowski <krzysztof.kozlowski@...aro.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/2] reset: always include RESET_GPIO driver if
possible
On Mi, 2025-10-15 at 22:59 +0200, Wolfram Sang 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@...esas.com>
> Closes: https://lore.kernel.org/r/87a51um1y1.wl-kuninori.morimoto.gx@renesas.com
> Signed-off-by: Wolfram Sang <wsa+renesas@...g-engineering.com>
> ---
>
> Changes since RFC v1:
> * new patch
>
> drivers/reset/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/reset/Kconfig b/drivers/reset/Kconfig
> index 78b7078478d4..7319bcd251dc 100644
> --- 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
Thank you, what was the reason to go with this instead of
default y if GPIOLIB
?
regards
Philipp
Powered by blists - more mailing lists