From: "Kumar, Udit" <u-kumar1@ti.com>
To: Anurag Dutta <a-dutta@ti.com>, <nm@ti.com>, <vigneshr@ti.com>,
<kristo@kernel.org>
Cc: <vaishnav.a@ti.com>, <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: ti: k3-j721e-common-proc-board: Add bootph-all to HBMC nodes
Date: Sat, 19 Apr 2025 09:28:57 +0530 [thread overview]
Message-ID: <80b5867b-958a-41ff-854a-6a3173ddbdc0@ti.com> (raw)
In-Reply-To: <20250411082637.2271746-1-a-dutta@ti.com>
On 4/11/2025 1:56 PM, Anurag Dutta wrote:
> Add bootph-all to HBMC controller and hyperflash nodes for successful
> hyperflash boot on j721e-evm.
>
> Signed-off-by: Anurag Dutta <a-dutta@ti.com>
> ---
>
> Test logs : https://gist.github.com/anuragdutta731/90a492589557c2ec2881e1de50a62006
>
> arch/arm64/boot/dts/ti/k3-j721e-common-proc-board.dts | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-j721e-common-proc-board.dts b/arch/arm64/boot/dts/ti/k3-j721e-common-proc-board.dts
> index 4421852161dd..9ada749f16ba 100644
> --- a/arch/arm64/boot/dts/ti/k3-j721e-common-proc-board.dts
> +++ b/arch/arm64/boot/dts/ti/k3-j721e-common-proc-board.dts
> @@ -570,6 +570,13 @@ &usb1 {
> maximum-speed = "high-speed";
> };
>
> +&hbmc {
> + bootph-all;
> + flash@0,0 {
> + bootph-all;
> + };
> +};
Could you check once , if this is duplicated
commit fbdb8aa4eab84 "arm64: dts: ti: k3-j721e-evm*: Add bootph-*
properties"
adds bootph-all in arch/arm64/boot/dts/ti/k3-j721e-som-p0.dtsi file for
flash.
AFAIK, parent node should inherit property of child for bootph.
In case you are not getting in u-boot then u-boot shall fix this[0]
[0] : https://lore.kernel.org/all/20250327080642.2269856-1-m-shah@ti.com/
> +
> &ospi1 {
> pinctrl-names = "default";
> pinctrl-0 = <&mcu_fss0_ospi1_pins_default>;
prev parent reply other threads:[~2025-04-19 3:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 8:26 Anurag Dutta
2025-04-11 11:26 ` Nishanth Menon
2025-04-19 3:58 ` Kumar, Udit [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=80b5867b-958a-41ff-854a-6a3173ddbdc0@ti.com \
--to=u-kumar1@ti.com \
--cc=a-dutta@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=vaishnav.a@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®