From: Krzysztof Kozlowski <krzk@kernel.org>
To: Thierry Bultel <thierry.bultel.yh@bp.renesas.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "thierry.bultel@linatsea.fr" <thierry.bultel@linatsea.fr>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
Paul Barker <paul.barker.ct@bp.renesas.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 13/13] arm64: defconfig: Enable Renesas RZ/T2H SoC option
Date: Thu, 27 Feb 2025 12:48:34 +0100 [thread overview]
Message-ID: <c4a44c39-5448-47d5-aeb1-32bab6e57047@kernel.org> (raw)
In-Reply-To: <TYCPR01MB11492DBCAD461B83B3CBE75E68ACD2@TYCPR01MB11492.jpnprd01.prod.outlook.com>
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
next prev parent reply other threads:[~2025-02-27 11:48 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250226130935.3029927-1-thierry.bultel.yh@bp.renesas.com>
2025-02-26 13:09 ` [PATCH v3 01/13] dt-bindings: soc: Add Renesas RZ/T2H (R9A09G077) SoC Thierry Bultel
2025-02-26 14:26 ` Krzysztof Kozlowski
2025-02-26 13:09 ` [PATCH v3 02/13] dt-bindings: clock: Add cpg for the Renesas RZ/T2H SoC Thierry Bultel
2025-02-26 14:44 ` Rob Herring (Arm)
2025-02-26 13:09 ` [PATCH v3 03/13] dt-bindings: serial: Add compatible for Renesas RZ/T2H SoC in sci Thierry Bultel
2025-03-03 13:35 ` Rob Herring
2025-03-03 15:10 ` Thierry Bultel
2025-03-03 15:42 ` Geert Uytterhoeven
2025-02-26 13:09 ` [PATCH v3 04/13] soc: renesas: Add RZ/T2H (R9A09G077) config option Thierry Bultel
2025-03-06 14:13 ` Geert Uytterhoeven
2025-02-26 13:09 ` [PATCH v3 05/13] clk: renesas: Pass sub struct of cpg_mssr_priv to cpg_clk_register Thierry Bultel
2025-02-26 13:09 ` [PATCH v3 06/13] clk: renesas: Add support for R9A09G077 SoC Thierry Bultel
2025-02-27 14:55 ` kernel test robot
2025-02-27 16:32 ` kernel test robot
2025-02-26 13:09 ` [PATCH v3 07/13] serial: sh-sci: Fix a comment about SCIFA Thierry Bultel
2025-02-26 13:09 ` [PATCH v3 08/13] serial: sh-sci: Introduced function pointers Thierry Bultel
2025-02-27 14:15 ` kernel test robot
2025-02-26 13:09 ` [PATCH v3 09/13] serial: sh-sci: Introduced sci_of_data Thierry Bultel
2025-02-27 13:23 ` kernel test robot
2025-03-06 10:17 ` Geert Uytterhoeven
2025-02-26 13:09 ` [PATCH v3 10/13] serial: sh-sci: Add support for RZ/T2H SCI Thierry Bultel
2025-02-26 13:09 ` [PATCH v3 11/13] arm64: dts: renesas: Add initial support for renesas RZ/T2H SoC Thierry Bultel
2025-02-26 13:09 ` [PATCH v3 12/13] arm64: dts: renesas: Add initial support for renesas RZ/T2H eval board Thierry Bultel
2025-02-26 14:23 ` Krzysztof Kozlowski
2025-02-26 14:46 ` Paul Barker
2025-02-26 15:13 ` Krzysztof Kozlowski
2025-02-26 13:09 ` [PATCH v3 13/13] arm64: defconfig: Enable Renesas RZ/T2H SoC option Thierry Bultel
2025-02-26 14:22 ` Krzysztof Kozlowski
2025-02-26 14:32 ` Thierry Bultel
2025-02-26 14:39 ` Krzysztof Kozlowski
2025-02-26 15:44 ` Thierry Bultel
2025-02-27 9:24 ` Geert Uytterhoeven
2025-02-27 9:43 ` Krzysztof Kozlowski
2025-02-27 10:48 ` Thierry Bultel
2025-02-27 11:48 ` Krzysztof Kozlowski [this message]
2025-02-27 13:25 ` Geert Uytterhoeven
2025-02-27 13:34 ` Krzysztof Kozlowski
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=c4a44c39-5448-47d5-aeb1-32bab6e57047@kernel.org \
--to=krzk@kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=paul.barker.ct@bp.renesas.com \
--cc=thierry.bultel.yh@bp.renesas.com \
--cc=thierry.bultel@linatsea.fr \
/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
all inboxes | Powered by JetHome®