From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Thierry Reding <thierry.reding@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org,
Thierry Reding <treding@nvidia.com>
Subject: Re: [PATCH v2 1/3] dt-bindings: fuse: Document compatible string for Tegra264 FUSE
Date: Sun, 20 Sep 2026 13:03:33 +0200 [thread overview]
Message-ID: <20260920-celestial-scorpion-of-certainty-aa0954@quoll> (raw)
In-Reply-To: <20260917-tegra-tegra264-fuse-v2-1-4936068c2168@nvidia.com>
On Thu, Sep 17, 2026 at 10:16:01AM +0100, Jon Hunter wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> Add the compatible string for the fuse device on Tegra264. This hardware
> block is mostly the same as the one found on earlier generations,
> however, the exact register regions that can be accessed differ.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
> ---
> Documentation/devicetree/bindings/fuse/nvidia,tegra20-fuse.yaml | 1 +
> 1 file changed, 1 insertion(+)
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-09-20 11:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 9:16 [PATCH v2 0/3] soc/tegra: fuse: Add Tegra264 support Jon Hunter
2026-09-17 9:16 ` [PATCH v2 1/3] dt-bindings: fuse: Document compatible string for Tegra264 FUSE Jon Hunter
2026-09-20 11:03 ` Krzysztof Kozlowski [this message]
2026-09-17 9:16 ` [PATCH v2 2/3] arm64: tegra: Add FUSE block on Tegra264 Jon Hunter
2026-09-17 9:16 ` [PATCH v2 3/3] soc/tegra: fuse: Add Tegra264 support Jon Hunter
2026-09-21 10:24 ` [PATCH v2 0/3] " Thierry Reding
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=20260920-celestial-scorpion-of-certainty-aa0954@quoll \
--to=krzk@kernel.org \
--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 \
--cc=thierry.reding@kernel.org \
--cc=treding@nvidia.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