From: Suneel Garapati <suneelg@nvidia.com>
To: <linux-tegra@vger.kernel.org>
Cc: Suneel Garapati <suneelg@nvidia.com>
Subject: [PATCH 1/3] dt-bindings: timestamp: Add Tegra264 support
Date: Tue, 31 Mar 2026 20:04:54 +0000 [thread overview]
Message-ID: <20260331200454.186649-1-suneelg@nvidia.com> (raw)
Add timestamp provider support for the Tegra264 in devicetree
bindings. Tegra264 has two generic timestamping engines (GTE)
which are the always-on GTE (AON) and legacy interrupt
controller (LIC) GTE.
Signed-off-by: Suneel Garapati <suneelg@nvidia.com>
---
.../devicetree/bindings/timestamp/nvidia,tegra194-hte.yaml | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/timestamp/nvidia,tegra194-hte.yaml b/Documentation/devicetree/bindings/timestamp/nvidia,tegra194-hte.yaml
index 456797967adc..210200421a38 100644
--- a/Documentation/devicetree/bindings/timestamp/nvidia,tegra194-hte.yaml
+++ b/Documentation/devicetree/bindings/timestamp/nvidia,tegra194-hte.yaml
@@ -25,6 +25,8 @@ properties:
- nvidia,tegra194-gte-lic
- nvidia,tegra234-gte-aon
- nvidia,tegra234-gte-lic
+ - nvidia,tegra264-gte-aon
+ - nvidia,tegra264-gte-lic
reg:
maxItems: 1
@@ -112,6 +114,7 @@ allOf:
contains:
enum:
- nvidia,tegra234-gte-aon
+ - nvidia,tegra264-gte-aon
then:
required:
- nvidia,gpio-controller
--
2.34.1
next reply other threads:[~2026-03-31 20:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 20:04 Suneel Garapati [this message]
2026-04-01 7:52 ` [PATCH 1/3] dt-bindings: timestamp: Add Tegra264 support Krzysztof Kozlowski
-- strict thread matches above, loose matches on Subject: below --
2026-04-01 21:38 [PATCH 0/3] Add Tegra264 HTE provider Suneel Garapati
2026-04-01 21:38 ` [PATCH 1/3] dt-bindings: timestamp: Add Tegra264 support Suneel Garapati
2026-04-02 8:47 ` Krzysztof Kozlowski
2026-04-02 8:47 ` Krzysztof Kozlowski
2026-04-02 9:49 ` Jon Hunter
2026-04-02 9:53 ` Krzysztof Kozlowski
2026-04-02 10:21 ` Jon Hunter
2026-04-02 10:24 ` 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=20260331200454.186649-1-suneelg@nvidia.com \
--to=suneelg@nvidia.com \
--cc=linux-tegra@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.