From: Chun Ng <chunn@nvidia.com>
To: <linux-tegra@vger.kernel.org>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<thierry.reding@gmail.com>, <jonathanh@nvidia.com>,
<chunn@nvidia.com>, <ankitag@nvidia.com>
Subject: [PATCH 0/4] arm64: tegra: add initial Tegra238 and E2426-1099+E2423-1099 support
Date: Wed, 25 Mar 2026 21:26:24 +0000 [thread overview]
Message-ID: <20260325212628.1234082-1-chunn@nvidia.com> (raw)
Hi all,
This series adds initial support for the NVIDIA Tegra238 SoC and the
E2426-1099+E2423-1099 engineering reference platform. The series follows
the pattern used for Tegra234 and other recent Tegra SoCs.
It introduces Tegra238 clock and reset binding headers, documents the
E2426-1099+E2423-1099 platform compatibles, relaxes the tegra186-hsp
binding schema for HSP configurations used on Tegra238, and adds the
initial Tegra238 SoC device tree plus board DTS.
The device tree added here is minimal scaffolding only. It is not yet
bootable, and further enablement will follow in later series.
The patch order puts bindings before implementation: clock/reset IDs
first, then platform documentation, then the HSP schema update required
by tegra238.dtsi, and finally the SoC and board device trees.
This series is based on linux-next commit 785f0eb2f85d
("Add linux-next specific files for 20260320").
Tested with:
- make ARCH=arm64 CHECK_DTBS=yes nvidia/tegra238-e2426-1099+e2423-1099.dtb
- make ARCH=arm64 dt_binding_check
Chun Ng (4):
dt-bindings: tegra: Add Tegra238 clock and reset definitions
dt-bindings: tegra: Document E2426-1099+E2423-1099 platform
dt-bindings: mailbox: tegra186-hsp: allow doorbell+shared or
shared-only
arm64: tegra: add e2426-1099+e2423-1099 support
.../devicetree/bindings/arm/tegra.yaml | 4 +
.../bindings/mailbox/nvidia,tegra186-hsp.yaml | 7 +
arch/arm64/boot/dts/nvidia/Makefile | 2 +
.../nvidia/tegra238-e2426-1099+e2423-1099.dts | 16 +
arch/arm64/boot/dts/nvidia/tegra238.dtsi | 190 ++++++++++++
include/dt-bindings/clock/nvidia,tegra238.h | 279 ++++++++++++++++++
include/dt-bindings/reset/nvidia,tegra238.h | 125 ++++++++
7 files changed, 623 insertions(+)
create mode 100644 arch/arm64/boot/dts/nvidia/tegra238-e2426-1099+e2423-1099.dts
create mode 100644 arch/arm64/boot/dts/nvidia/tegra238.dtsi
create mode 100644 include/dt-bindings/clock/nvidia,tegra238.h
create mode 100644 include/dt-bindings/reset/nvidia,tegra238.h
base-commit: 785f0eb2f85decbe7c1ef9ae922931f0194ffc2e
--
2.43.0
next reply other threads:[~2026-03-25 21:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 21:26 Chun Ng [this message]
2026-03-25 21:26 ` [PATCH 1/4] dt-bindings: tegra: Add Tegra238 clock and reset definitions Chun Ng
2026-03-26 10:19 ` Krzysztof Kozlowski
2026-03-25 21:26 ` [PATCH 2/4] dt-bindings: tegra: Document E2426-1099+E2423-1099 platform Chun Ng
2026-03-25 21:26 ` [PATCH 3/4] dt-bindings: mailbox: tegra186-hsp: allow doorbell+shared or shared-only Chun Ng
2026-03-26 10:22 ` Krzysztof Kozlowski
2026-03-25 21:26 ` [PATCH 4/4] arm64: tegra: add e2426-1099+e2423-1099 support Chun Ng
2026-03-26 10:18 ` Krzysztof Kozlowski
2026-03-26 11:03 ` Thierry Reding
2026-03-26 11:12 ` 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=20260325212628.1234082-1-chunn@nvidia.com \
--to=chunn@nvidia.com \
--cc=ankitag@nvidia.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.com \
/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