From: Srinivas Kandagatla <srini@kernel.org>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Kunihiko Hayashi <hayashi.kunihiko@socionext.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Judith Mendez <jm@ti.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: (subset) [PATCH v3 0/3] Support AM62P silicon revision detection via uniphier-efuse
Date: Mon, 14 Sep 2026 22:52:20 +0100 [thread overview]
Message-ID: <178942274041.683176.599438200260103620.b4-ty@kernel.org> (raw)
In-Reply-To: <20260910155509.1425682-1-jm@ti.com>
On Thu, 10 Sep 2026 10:55:06 -0500, Judith Mendez wrote:
> This series adds support for reading AM62P silicon revision from the
> efuse GP_SW register. The solution reuses the existing uniphier-efuse
> driver by adding ti,am62p-efuse as a compatible string. The three patches
> update the devicetree binding to document the new compatible, configure
> the driver as mandatory builtin for K3 architectures, and extend the driver
> to support AM62P devices. The uniphier-efuse driver is simple enough to be
> reused for efuse register reads on the AM62P SoC.
>
> [...]
Applied, thanks!
[1/3] dt-bindings: nvmem: uniphier-efuse: Add ti,am62p-efuse compatible
commit: c66d971968218d7f746e85701d4c226746654690
[2/3] nvmem: uniphier-efuse: Enable for K3 SoCs
commit: 0bf05ce85c82783c103a3beb28fa6607dae8ea79
Best regards,
--
Srinivas Kandagatla <srini@kernel.org>
prev parent reply other threads:[~2026-09-14 21:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 15:55 Judith Mendez
2026-09-10 15:55 ` [PATCH v3 1/3] dt-bindings: nvmem: uniphier-efuse: Add ti,am62p-efuse compatible Judith Mendez
2026-09-13 8:57 ` Krzysztof Kozlowski
2026-09-10 15:55 ` [PATCH v3 2/3] nvmem: uniphier-efuse: Enable for K3 SoCs Judith Mendez
2026-09-10 15:55 ` [PATCH v3 3/3] nvmem: uniphier-efuse: Add ti,am62p-efuse compatible Judith Mendez
2026-09-13 8:57 ` Krzysztof Kozlowski
2026-09-14 21:58 ` Judith Mendez
2026-09-14 21:52 ` Srinivas Kandagatla [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=178942274041.683176.599438200260103620.b4-ty@kernel.org \
--to=srini@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hayashi.kunihiko@socionext.com \
--cc=jm@ti.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@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
all inboxes | Powered by JetHome®