From: Thierry Reding <thierry.reding@gmail.com>
To: Aniruddha Rao <anrao@nvidia.com>
Cc: thierry.reding@kernel.org, jonathanh@nvidia.com,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/6] soc/tegra: Add Tegra410 SoC Kconfig symbol
Date: Fri, 10 Jul 2026 11:34:26 +0200 [thread overview]
Message-ID: <alC7m7aQ8iVgraod@orome> (raw)
In-Reply-To: <20260615083731.888055-2-anrao@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 1742 bytes --]
On Mon, Jun 15, 2026 at 08:37:26AM +0000, Aniruddha Rao wrote:
> Add a dedicated ARCH_TEGRA_410_SOC symbol in the Tegra SoC Kconfig so
> Tegra410-specific support can be selected independently.
>
> The Tegra BPMP driver will use this symbol to build Tegra410-specific
> BPMP support, including the Tegra410 Memory Bandwidth Throttler helpers,
> without enabling that code for other Tegra SoCs.
That paragraph is not useful. We want this in general for Tegra410, any
specific features are irrelevant at this point.
>
> Signed-off-by: Aniruddha Rao <anrao@nvidia.com>
> ---
> drivers/soc/tegra/Kconfig | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/drivers/soc/tegra/Kconfig b/drivers/soc/tegra/Kconfig
> index 073346c1542b..72b7f5db8179 100644
> --- a/drivers/soc/tegra/Kconfig
> +++ b/drivers/soc/tegra/Kconfig
> @@ -149,6 +149,16 @@ config ARCH_TEGRA_241_SOC
> help
> Enable support for the NVIDIA Tegra241 SoC.
>
> +config ARCH_TEGRA_410_SOC
> + bool "NVIDIA Tegra410 SoC"
> + help
> + Enable support for the NVIDIA Tegra410 SoC.
> +
> + This option enables Tegra410-specific platform support in
> + drivers shared across NVIDIA Tegra SoCs.
> + It should be selected when building a kernel for Tegra410
> + systems.
> +
> config ARCH_TEGRA_264_SOC
> bool "NVIDIA Tegra264 SoC"
> default ARCH_TEGRA
We have traditionally sorted these chronologically (with some exceptions
like Tegra238 which is sorted after Tegra234 because it's from the same
family), so this should go after Tegra264. There's also some benefit in
grouping this with Tegra241, so I suppose we could move both into a
separate section to highlight their relationship.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-07-10 9:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 8:37 [PATCH 0/6] firmware: tegra: bpmp: Add Tegra410 ACPI MBWT support Aniruddha Rao
2026-06-15 8:37 ` [PATCH 1/6] soc/tegra: Add Tegra410 SoC Kconfig symbol Aniruddha Rao
2026-07-10 9:34 ` Thierry Reding [this message]
2026-06-15 8:37 ` [PATCH 2/6] firmware: tegra: bpmp: Move channel, resource init to helper Aniruddha Rao
2026-07-10 9:39 ` Thierry Reding
2026-06-15 8:37 ` [PATCH 3/6] firmware: tegra: bpmp: Add ACPI support Aniruddha Rao
2026-07-10 10:08 ` Thierry Reding
2026-06-15 8:37 ` [PATCH 4/6] firmware: tegra: bpmp: Add the Memory Bandwidth Throttler ABI definitions Aniruddha Rao
2026-07-10 10:13 ` Thierry Reding
2026-06-15 8:37 ` [PATCH 5/6] firmware: tegra: bpmp: Add Tegra410 MBWT BPMP helpers Aniruddha Rao
2026-07-10 10:19 ` Thierry Reding
2026-06-15 8:37 ` [PATCH 6/6] firmware: tegra: bpmp: Add Tegra410 MBWT sysfs interface Aniruddha Rao
2026-07-10 10:46 ` Thierry Reding
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=alC7m7aQ8iVgraod@orome \
--to=thierry.reding@gmail.com \
--cc=anrao@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@kernel.org \
/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