From: Suneel Garapati <suneelg@nvidia.com>
To: <dipenp@nvidia.com>, <jonathanh@nvidia.com>,
<thierry.reding@gmail.com>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <amhetre@nvidia.com>, <sheetal@nvidia.com>,
<kkartik@nvidia.com>, <robh@kernel.org>, <pshete@nvidia.com>,
<timestamp@lists.linux.dev>, <devicetree@vger.kernel.org>,
<linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: Suneel Garapati <suneelg@nvidia.com>
Subject: [PATCH v2 0/3] Add Tegra264 HTE provider
Date: Wed, 8 Apr 2026 21:24:10 +0000 [thread overview]
Message-ID: <20260408212413.217692-1-suneelg@nvidia.com> (raw)
This patch series mainly adds support for the Tegra264 HTE provider.
- Update devicetree bindings to add Tegra264 support
- Add support in driver for Tegra264 chip including new tsc clock
parameters setup per SoC as values differ for Tegra264
- Populate device-tree nodes for Tegra264 GTE instances
- One of devicetree nodes has reference to gpio_aon node that is
dependent on this series [1]
1 - https://patchwork.ozlabs.org/project/linux-gpio/patch/20260128085114.1137725-3-pshete@nvidia.com/
---
Changes in v2:
- Devicetree bindings has nvidia,slices property deprecated for Tegra264
Suneel Garapati (3):
dt-bindings: timestamp: Add Tegra264 support
hte: tegra194: Add Tegra264 GTE support
arm64: tegra: Add GTE nodes for Tegra264
.../timestamp/nvidia,tegra194-hte.yaml | 14 ++
arch/arm64/boot/dts/nvidia/tegra264.dtsi | 19 +++
drivers/hte/hte-tegra194.c | 133 +++++++++++++++++-
3 files changed, 161 insertions(+), 5 deletions(-)
--
2.34.1
next reply other threads:[~2026-04-08 21:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 21:24 Suneel Garapati [this message]
2026-04-08 21:24 ` [PATCH v2 1/3] dt-bindings: timestamp: Add Tegra264 support Suneel Garapati
2026-04-08 21:24 ` [PATCH v2 2/3] hte: tegra194: Add Tegra264 GTE support Suneel Garapati
2026-04-08 21:24 ` [PATCH v2 3/3] arm64: tegra: Add GTE nodes for Tegra264 Suneel Garapati
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=20260408212413.217692-1-suneelg@nvidia.com \
--to=suneelg@nvidia.com \
--cc=amhetre@nvidia.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dipenp@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=kkartik@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=pshete@nvidia.com \
--cc=robh@kernel.org \
--cc=sheetal@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=timestamp@lists.linux.dev \
/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