From: Judith Mendez <jm@ti.com>
To: Moteen Shah <m-shah@ti.com>, Nishanth Menon <nm@ti.com>,
"Vignesh Raghavendra" <vigneshr@ti.com>
Cc: 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 v2] arm64: dts: ti: Add k3-am62p-wakeup.dtsi for AM62PX efuse GP_SW1
Date: Mon, 5 Oct 2026 17:33:32 -0500 [thread overview]
Message-ID: <8fbb7c50-6215-49cd-b2f6-5a067a0f96d0@ti.com> (raw)
In-Reply-To: <b82dec19-02a9-4b93-a2bb-3cbb6f33ae63@ti.com>
Hi Moteen,
On 10/5/26 10:44 AM, Moteen Shah wrote:
> Hey Judith,
> Thanks for the patch.
>
> On 22/09/26 22:27, Judith Mendez wrote:
>> Create k3-am62p-wakeup.dtsi which includes AM62P-specific WAKEUP
>> domain nodes.
>>
>> In k3-am62p-wakeup.dtsi, add the efuse node for GP_SW1 register at
>> offset 0x230. GP_SW1 will be used to determine AM62P silicon revision.
>
>
> Nit: Isn't GP_SW1 0x230 + offset? might need fixing of the msg.
>
>>
>> Signed-off-by: Judith Mendez <jm@ti.com>
>> ---
>> This patch adds GP_SW1 efuse node for AM62PX only now that bindings [0]
>> are in place.
>>
>> Changes since v1:
>> - Move gpsw_efuse from k3-am62p-j722s-common-wakeup.dtsi to the new
>> k3-am62p-wakeup.dtsi [1] since GP_SW efuse registers are marked
>> reserved for J722S.
>>
>> [0] https://lore.kernel.org/
>> all/178942274041.683176.599438200260103620.b4-ty@kernel.org/
>> [1] https://lore.kernel.org/all/5d4742fa-e26a-4b49-8eb4-
>> b6291c402334@ti.com/#t
>>
>> Link to v1:
>> https://lore.kernel.org/all/20260915001304.3781247-1-jm@ti.com/
>> ---
>> arch/arm64/boot/dts/ti/k3-am62p-wakeup.dtsi | 25 +++++++++++++++++++++
>> arch/arm64/boot/dts/ti/k3-am62p.dtsi | 1 +
>> 2 files changed, 26 insertions(+)
>> create mode 100644 arch/arm64/boot/dts/ti/k3-am62p-wakeup.dtsi
>>
>> diff --git a/arch/arm64/boot/dts/ti/k3-am62p-wakeup.dtsi b/arch/arm64/
>> boot/dts/ti/k3-am62p-wakeup.dtsi
>> new file mode 100644
>> index 0000000000000..c56fb3890c983
>> --- /dev/null
>> +++ b/arch/arm64/boot/dts/ti/k3-am62p-wakeup.dtsi
>> @@ -0,0 +1,25 @@
>> +// SPDX-License-Identifier: GPL-2.0-only OR MIT
>> +/*
>> + * Device Tree file for the AM62P WAKEUP domain peripherals
>> + *
>> + * Copyright (C) 2026 Texas Instruments Incorporated - https://
>> www.ti.com/
>> + */
>> +
>> +&wkup_conf {
>> + gpsw_efuse: efuse@230 {
>> + compatible = "ti,am62p-efuse", "socionext,uniphier-efuse";
>> + reg = <0x230 0x10>;
>> + #address-cells = <1>;
>> + bootph-all;
>
>
> Nit: I think the property ordering for bootph-all doesn't look correct.
>
> With the above two changes, if valid.
I ran a DT checker, and it says to put it before size-cells and after
address cells. If I revert, I get these warnings:
+arch/arm64/boot/dts/ti/k3-am62p-wakeup.dtsi:13: [property-order]
property '#address-cells' out of canonical order (should sort before
'bootph-all')
So Ill leave as is for now, I will fix the commit message though.
Thanks for reviewing.
~ Judith
>
> Reviewed-by: Moteen Shah <m-shah@ti.com>
>
> Regards,
> Moteen
>
>> + #size-cells = <1>;
>> +
>> + gpsw1: gpsw1@4 {
>> + reg = <0x4 0x4>;
>> + };
>> + };
>> +};
>> +
>> +&chipid {
>> + nvmem-cells = <&gpsw1>;
>> + nvmem-cell-names = "gpsw1";
>> +};
>> diff --git a/arch/arm64/boot/dts/ti/k3-am62p.dtsi b/arch/arm64/boot/
>> dts/ti/k3-am62p.dtsi
>> index 9d6266d6ddb82..058f264ee0646 100644
>> --- a/arch/arm64/boot/dts/ti/k3-am62p.dtsi
>> +++ b/arch/arm64/boot/dts/ti/k3-am62p.dtsi
>> @@ -154,3 +154,4 @@ cbass_wakeup: bus@b00000 {
>> /* Include AM62P specific peripherals */
>> #include "k3-am62p-main.dtsi"
>> +#include "k3-am62p-wakeup.dtsi"
prev parent reply other threads:[~2026-10-05 22:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 16:57 Judith Mendez
2026-10-05 15:44 ` Moteen Shah
2026-10-05 22:33 ` 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=8fbb7c50-6215-49cd-b2f6-5a067a0f96d0@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=m-shah@ti.com \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--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®