From: Nishanth Menon <nm@ti.com>
To: Anurag Dutta <a-dutta@ti.com>
Cc: <vigneshr@ti.com>, <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] arm64: dts: ti: k3-j721e-som-p0: Add bootph-all to HBMC node
Date: Mon, 21 Apr 2025 06:44:21 -0500 [thread overview]
Message-ID: <20250421114421.pj6vceavzjl2qkky@filing> (raw)
In-Reply-To: <20250416060754.2393701-1-a-dutta@ti.com>
On 11:37-20250416, Anurag Dutta wrote:
> Add bootph-all to HBMC controller node for successful hyperflash
> boot on j721e-evm
>
> Signed-off-by: Anurag Dutta <a-dutta@ti.com>
> ---
> Test log : https://gist.github.com/anuragdutta731/103e84e84f013093fa089803719d997d
>
> Changelog : v1:
> 1. Added bootph-all to hbmc node in k3-j721e-som-p0.dtsi
> 2. Removed bootph-all from v1 patch from flash@0,0 node
>
> Link to v1 : https://lore.kernel.org/all/20250411082637.2271746-1-a-dutta@ti.com/
>
> arch/arm64/boot/dts/ti/k3-j721e-som-p0.dtsi | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-j721e-som-p0.dtsi b/arch/arm64/boot/dts/ti/k3-j721e-som-p0.dtsi
> index 0722f6361cc8..5665b9490003 100644
> --- a/arch/arm64/boot/dts/ti/k3-j721e-som-p0.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-j721e-som-p0.dtsi
> @@ -440,6 +440,7 @@ &hbmc {
> pinctrl-0 = <&mcu_fss0_hpb0_pins_default>;
> ranges = <0x00 0x00 0x05 0x00000000 0x4000000>, /* 64MB Flash on CS0 */
> <0x01 0x00 0x05 0x04000000 0x800000>; /* 8MB RAM on CS1 */
> + bootph-all;
>
> flash@0,0 {
> compatible = "cypress,hyperflash", "cfi-flash";
This node already has bootph-all, only the child nodes need bootph
properties. Am i missing something?
> --
> 2.34.1
>
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
prev parent reply other threads:[~2025-04-21 11:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 6:07 Anurag Dutta
2025-04-21 11:44 ` Nishanth Menon [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=20250421114421.pj6vceavzjl2qkky@filing \
--to=nm@ti.com \
--cc=a-dutta@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.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®