[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c4a44c39-5448-47d5-aeb1-32bab6e57047@kernel.org>
Date: Thu, 27 Feb 2025 12:48:34 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Thierry Bultel <thierry.bultel.yh@...renesas.com>,
Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: "thierry.bultel@...atsea.fr" <thierry.bultel@...atsea.fr>,
"linux-renesas-soc@...r.kernel.org" <linux-renesas-soc@...r.kernel.org>,
Paul Barker <paul.barker.ct@...renesas.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 13/13] arm64: defconfig: Enable Renesas RZ/T2H SoC
option
On 27/02/2025 11:48, Thierry Bultel wrote:
>>
>> This is fine, I am not against fine-grained SoC-enable options. However
>> all your SoCs should be enabled by default (default y if ARCH_RENESAS or
>> any other option which works for you) thus you won't be growing user-
>> selectable choices.
>>
>> Strictly speaking this still will be choice, because you need to trim
>> config, but all people and all distros will just ignore it and don't see
>> it in defconfig.
>>
>
> I understand.
>
> All the ARCH_XXX SoC options are already under a menuconfig section, which
> is defaulted to 'y' if ARCH_RENESAS.
Indeed and it actually cannot have "if ARCH_RENESAS" due to how compile
test is enabled there.
>
> So I guess that this simple additional change would make it:
>
> diff --git a/drivers/soc/renesas/Kconfig b/drivers/soc/renesas/Kconfig
> index 91a815e0a522..231880c21aa7 100644
> --- a/drivers/soc/renesas/Kconfig
> +++ b/drivers/soc/renesas/Kconfig
> @@ -358,6 +358,7 @@ config ARCH_R9A09G057
>
> config ARCH_R9A09G077
> bool "ARM64 Platform support for RZ/T2H"
> + default y
> help
> This enables support for the Renesas RZ/T2H SoC variants.
Yes and then run savedefconfig and check if defconfig needs this symbol.
Best regards,
Krzysztof
Powered by blists - more mailing lists