From: Thierry Reding <thierry.reding@kernel.org>
To: Thierry Reding <thierry.reding@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jon Hunter <jonathanh@nvidia.com>,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: [PATCH 1/2] dt-bindings: fuse: Document compatible string for Tegra264 FUSE
Date: Sat, 21 Mar 2026 00:38:21 +0100 [thread overview]
Message-ID: <20260320233822.2578569-1-thierry.reding@kernel.org> (raw)
From: Thierry Reding <treding@nvidia.com>
This hardware block is mostly the same as the one found on earlier
generations. However, the exact register regions that can be accessed
differ, so a new compatible string is required.
Signed-off-by: Thierry Reding <treding@nvidia.com>
---
Documentation/devicetree/bindings/fuse/nvidia,tegra20-fuse.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/fuse/nvidia,tegra20-fuse.yaml b/Documentation/devicetree/bindings/fuse/nvidia,tegra20-fuse.yaml
index 02f0b0462377..bf9923b63852 100644
--- a/Documentation/devicetree/bindings/fuse/nvidia,tegra20-fuse.yaml
+++ b/Documentation/devicetree/bindings/fuse/nvidia,tegra20-fuse.yaml
@@ -22,6 +22,7 @@ properties:
- nvidia,tegra186-efuse
- nvidia,tegra194-efuse
- nvidia,tegra234-efuse
+ - nvidia,tegra264-efuse
- items:
- const: nvidia,tegra132-efuse
--
2.52.0
next reply other threads:[~2026-03-20 23:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 23:38 Thierry Reding [this message]
2026-03-20 23:38 ` [PATCH 2/2] arm64: tegra: Add FUSE block on Tegra264 Thierry Reding
2026-03-21 10:50 ` [PATCH 1/2] dt-bindings: fuse: Document compatible string for Tegra264 FUSE 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=20260320233822.2578569-1-thierry.reding@kernel.org \
--to=thierry.reding@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@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