From: "Kumar, Udit" <u-kumar1@ti.com>
To: Manorit Chawdhry <m-chawdhry@ti.com>
Cc: Nishanth Menon <nm@ti.com>, 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>,
Neha Malcom Francis <n-francis@ti.com>,
Aniket Limaye <a-limaye@ti.com>, Beleswar Padhi <b-padhi@ti.com>,
Siddharth Vadapalli <s-vadapalli@ti.com>
Subject: Re: [PATCH v3 5/5] arm64: dts: ti: k3-j7200*: Add bootph-* properties
Date: Wed, 7 Aug 2024 14:45:24 +0530 [thread overview]
Message-ID: <e61d817b-8043-4c77-92fe-6faa27881d41@ti.com> (raw)
In-Reply-To: <20240807075039.w56deberpo4rfhjc@uda0497581>
On 8/7/2024 1:20 PM, Manorit Chawdhry wrote:
> Hi Udit,
>
> On 12:58-20240807, Kumar, Udit wrote:
>> On 7/30/2024 3:23 PM, Manorit Chawdhry wrote:
>>> [..]
>>> I think you should consider to mark hbmc node for boot phase as well
>>>
> It's already marked in k3-j7200-som-p0.dtsi file with bootph-all inside
> the flash node that describe it, is that okay?
yes
>
>>> @@ -652,6 +661,7 @@ wkup_vtm0: temperature-sensor@42040000 {
>>> <0x00 0x42050000 0x00 0x350>;
>>> power-domains = <&k3_pds 154 TI_SCI_PD_EXCLUSIVE>;
>>> #thermal-sensor-cells = <1>;
>>> + bootph-pre-ram;
>>> };
>>> mcu_esm: esm@40800000 {
>>> diff --git a/arch/arm64/boot/dts/ti/k3-j7200-som-p0.dtsi b/arch/arm64/boot/dts/ti/k3-j7200-som-p0.dtsi
>>> index 21fe194a5766..d78f86889bf9 100644
>>> --- a/arch/arm64/boot/dts/ti/k3-j7200-som-p0.dtsi
>>> +++ b/arch/arm64/boot/dts/ti/k3-j7200-som-p0.dtsi
>>> @@ -121,6 +121,7 @@ J721E_WKUP_IOPAD(0x20, PIN_INPUT, 1) /* (B8) MCU_OSPI0_D5.MCU_HYPERBUS0_DQ5 */
>>> J721E_WKUP_IOPAD(0x24, PIN_INPUT, 1) /* (A8) MCU_OSPI0_D6.MCU_HYPERBUS0_DQ6 */
>>> J721E_WKUP_IOPAD(0x28, PIN_INPUT, 1) /* (A7) MCU_OSPI0_D7.MCU_HYPERBUS0_DQ7 */
>>> >;
>>> [..]
>>> bucka2: buck2 {
>>> @@ -464,6 +470,7 @@ flash@0 {
>>> cdns,tchsh-ns = <60>;
>>> cdns,tslch-ns = <60>;
>>> cdns,read-delay = <4>;
>>> + bootph-all;
>>> partitions {
>>> compatible = "fixed-partitions";
>>
>> Please consider, adding bootph in ospi0 node as well around
>> "ospi.phypattern"
>>
> Okay sure, will move the bootph-all from flash@0 node to under
> ospi.phypattern node as putting it in the child node should propagate
> it.
>
> Thanks for reviewing Udit!
>
> Regards,
> Manorit
next prev parent reply other threads:[~2024-08-07 9:17 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 9:53 [PATCH v3 0/5] Add bootph-all property for J7 boards Manorit Chawdhry
2024-07-30 9:53 ` [PATCH v3 1/5] arm64: dts: ti: k3-j721s2*: Add bootph-* properties Manorit Chawdhry
2024-08-06 14:43 ` Andrew Davis
2024-08-06 15:05 ` Nishanth Menon
2024-08-06 15:07 ` Nishanth Menon
2024-08-07 5:26 ` Manorit Chawdhry
2024-08-07 5:33 ` Neha Malcom Francis
2024-08-07 5:42 ` Manorit Chawdhry
2024-08-07 5:48 ` Neha Malcom Francis
2024-08-07 6:36 ` Manorit Chawdhry
2024-08-07 11:49 ` Nishanth Menon
2024-08-07 5:49 ` Manorit Chawdhry
2024-08-07 11:47 ` Nishanth Menon
2024-08-07 5:31 ` Manorit Chawdhry
2024-07-30 9:53 ` [PATCH v3 2/5] arm64: dts: ti: k3-j784s4*: Remove bootph properties from parent nodes Manorit Chawdhry
2024-08-07 7:51 ` Kumar, Udit
2024-07-30 9:53 ` [PATCH v3 3/5] arm64: dts: ti: k3-am68*: Add bootph-* properties Manorit Chawdhry
2024-07-30 9:53 ` [PATCH v3 4/5] arm64: dts: ti: k3-j721e*: " Manorit Chawdhry
2024-08-07 7:37 ` Kumar, Udit
2024-08-07 8:35 ` Manorit Chawdhry
2024-08-07 9:16 ` Kumar, Udit
2024-08-07 9:24 ` Neha Malcom Francis
2024-08-07 9:47 ` Manorit Chawdhry
2024-07-30 9:53 ` [PATCH v3 5/5] arm64: dts: ti: k3-j7200*: " Manorit Chawdhry
2024-08-07 7:28 ` Kumar, Udit
2024-08-07 7:50 ` Manorit Chawdhry
2024-08-07 9:15 ` Kumar, Udit [this message]
2024-08-07 14:37 ` Limaye, Aniket
2024-08-08 9:20 ` Manorit Chawdhry
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=e61d817b-8043-4c77-92fe-6faa27881d41@ti.com \
--to=u-kumar1@ti.com \
--cc=a-limaye@ti.com \
--cc=b-padhi@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-chawdhry@ti.com \
--cc=n-francis@ti.com \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=s-vadapalli@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