From: Judith Mendez <jm@ti.com>
To: "Kumar, Udit" <u-kumar1@ti.com>, Nishanth Menon <nm@ti.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: ti: k3-am62p-j722s-common-wakeup: Add GP_SW1 efuse node for silicon revision
Date: Tue, 15 Sep 2026 17:42:38 -0500 [thread overview]
Message-ID: <5d4742fa-e26a-4b49-8eb4-b6291c402334@ti.com> (raw)
In-Reply-To: <b490c984-8fba-4b92-96f0-8e4a4cc811b0@ti.com>
Hi Udit,
On 9/15/26 11:40 AM, Kumar, Udit wrote:
>
> Hi Judith,
>
> On 9/15/2026 5:43 AM, Judith Mendez wrote:
>> Add efuse node for GP_SW1 register at offset 0x230. The GP_SW1
>> efuse register is used to determine AM62Px silicon revision.
>> Reference efuse cell from chipid node via nvmem-cells.
>>
>> Signed-off-by: Judith Mendez <jm@ti.com>
>> ---
>> .../boot/dts/ti/k3-am62p-j722s-common-wakeup.dtsi | 14 ++++++++++++++
>> 1 file changed, 14 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/ti/k3-am62p-j722s-common-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-am62p-j722s-common-wakeup.dtsi
>> index 8612b45e665cf..0f00e9d87f8ba 100644
>> --- a/arch/arm64/boot/dts/ti/k3-am62p-j722s-common-wakeup.dtsi
>> +++ b/arch/arm64/boot/dts/ti/k3-am62p-j722s-common-wakeup.dtsi
>> @@ -19,9 +19,23 @@ wkup_conf: bus@43000000 {
>> chipid: chipid@14 {
>> compatible = "ti,am654-chipid";
>> reg = <0x14 0x4>;
>> + nvmem-cells = <&gpsw1>;
>> + nvmem-cell-names = "gpsw1";
>> bootph-all;
>> };
>>
>> + gpsw_efuse: efuse@230 {
>> + compatible = "ti,am62p-efuse", "socionext,uniphier-efuse";
>> + reg = <0x230 0x10>;
>> + #address-cells = <1>;
>> + #size-cells = <1>;
>> + bootph-all;
>> +
>> + gpsw1: gpsw1@4 {
>> + reg = <0x4 0x4>;
>> + };
>
> For J722S, this register this marked as reserved,
> Could you update in am62-p specific dt.
Right, let me see what I can do.
Thanks for reviewing.
~ Judith
>
> Thanks
>
>> + };
>> +
>> opp_efuse_table: syscon@18 {
>> compatible = "ti,am62-opp-efuse-table", "syscon";
>> reg = <0x18 0x4>;
>
prev parent reply other threads:[~2026-09-15 22:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 0:13 Judith Mendez
2026-09-15 16:40 ` Kumar, Udit
2026-09-15 22:42 ` Judith Mendez [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=5d4742fa-e26a-4b49-8eb4-b6291c402334@ti.com \
--to=jm@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.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
all inboxes | Powered by JetHome®