From: Thierry Reding <thierry.reding@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@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 0/3] soc/tegra: fuse: Add Tegra264 support
Date: Mon, 21 Sep 2026 12:24:07 +0200 [thread overview]
Message-ID: <arEFuSVya1BcQcrN@orome> (raw)
In-Reply-To: <20260917-tegra-tegra264-fuse-v2-0-4936068c2168@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 1393 bytes --]
On Thu, Sep 17, 2026 at 10:16:00AM +0100, Jon Hunter wrote:
> This series adds support for the FUSE block found on Tegra264. The first
> two patches were originally posted by Thierry Reding and add the device
> tree binding and FUSE node. The third patch adds the Tegra264 FUSE SoC
> data, including the register range and keepouts.
>
> Changes in v2:
> - Reword the device tree binding commit message following review
> feedback
> - Correct the register range for the efuse block to map the complete
> address space.
> - Add Tegra264 FUSE driver support
>
> Link: https://lore.kernel.org/linux-tegra/20260320233822.2578569-1-thierry.reding@kernel.org/
> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
> ---
> Jon Hunter (1):
> soc/tegra: fuse: Add Tegra264 support
>
> Thierry Reding (2):
> dt-bindings: fuse: Document compatible string for Tegra264 FUSE
> arm64: tegra: Add FUSE block on Tegra264
>
> .../bindings/fuse/nvidia,tegra20-fuse.yaml | 1 +
> arch/arm64/boot/dts/nvidia/tegra264.dtsi | 7 +
> drivers/soc/tegra/fuse/fuse-tegra.c | 11 +-
> drivers/soc/tegra/fuse/fuse-tegra30.c | 168 ++++++++++++++++++++-
> drivers/soc/tegra/fuse/fuse.h | 7 +-
> 5 files changed, 191 insertions(+), 3 deletions(-)
All there patches applied, thanks.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-09-21 10:24 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
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 ` Thierry Reding [this message]
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=arEFuSVya1BcQcrN@orome \
--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-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.com \
--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 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.