From: Prateek Agarwal <praagarwal@nvidia.com>
To: Linus Walleij <linusw@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Thierry Reding <thierry.reding@kernel.org>,
Jon Hunter <jonathanh@nvidia.com>
Cc: Prathamesh Shete <pshete@nvidia.com>,
Prateek Agarwal <praagarwal@nvidia.com>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 1/3] soc/tegra: Add Tegra268 Kconfig symbol
Date: Sun, 4 Oct 2026 19:29:19 +0000 [thread overview]
Message-ID: <20261004192921.2460405-2-praagarwal@nvidia.com> (raw)
In-Reply-To: <20261004192921.2460405-1-praagarwal@nvidia.com>
From: Prathamesh Shete <pshete@nvidia.com>
The NVIDIA Tegra268 SoC is an upcoming new chip. Add a Kconfig symbol to
allow fine-grained selection of support code for this chip.
Signed-off-by: Prathamesh Shete <pshete@nvidia.com>
Signed-off-by: Prateek Agarwal <praagarwal@nvidia.com>
---
drivers/soc/tegra/Kconfig | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/drivers/soc/tegra/Kconfig b/drivers/soc/tegra/Kconfig
index 8b6fdb9ad1ea..d856f9efea71 100644
--- a/drivers/soc/tegra/Kconfig
+++ b/drivers/soc/tegra/Kconfig
@@ -158,6 +158,15 @@ config ARCH_TEGRA_264_SOC
help
Enable support for the NVIDIA Tegra264 SoC.
+config ARCH_TEGRA_268_SOC
+ bool "NVIDIA Tegra268 SoC"
+ default ARCH_TEGRA
+ depends on !CPU_BIG_ENDIAN
+ select MAILBOX
+ select SOC_TEGRA_PMC
+ help
+ Enable support for the NVIDIA Tegra268 SoC.
+
endif
endif
--
2.17.1
next prev parent reply other threads:[~2026-10-04 19:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 19:29 [PATCH 0/3] Add Tegra268 pinmux support Prateek Agarwal
2026-10-04 19:29 ` Prateek Agarwal [this message]
2026-10-04 19:29 ` [PATCH 2/3] dt-bindings: pinctrl: Document Tegra268 pin controllers Prateek Agarwal
2026-10-04 19:29 ` [PATCH 3/3] pinctrl: tegra: Add support for Tegra268 Prateek Agarwal
2026-10-04 19:45 ` sashiko-bot
2026-10-07 10:40 ` [PATCH 0/3] Add Tegra268 pinmux support Linus Walleij
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=20261004192921.2460405-2-praagarwal@nvidia.com \
--to=praagarwal@nvidia.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=pshete@nvidia.com \
--cc=robh@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