From: Nishanth Menon <nm@ti.com>
To: Prasanth Babu Mantena <p-mantena@ti.com>
Cc: <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <vigneshr@ti.com>,
<kristo@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <linux-kernel@vger.kernel.org>,
<u-kumar1@ti.com>
Subject: Re: [PATCH v2] arm64: dts: ti: k3-j721e-common-proc-board: Enable OSPI1 on J721E
Date: Fri, 9 May 2025 03:25:09 -0500 [thread overview]
Message-ID: <20250509082509.ogfs2ulyfgk6etxc@unshaved> (raw)
In-Reply-To: <20250507050701.3007209-1-p-mantena@ti.com>
On 10:37-20250507, Prasanth Babu Mantena wrote:
> J721E SoM has MT25QU512AB Serial NOR flash connected to
> OSPI1 controller. Enable ospi1 node in device tree.
>
> Fixes: cb27354b38f3b ("arm64: dts: ti: k3-j721e: Add DT nodes for few peripherials")
Yes, cb27354b38f3b ("arm64: dts: ti: k3-j721e: Add DT nodes for few
peripherials") did not enable the node, But back then, we used to
ensure all nodes were left default (okay) and then disable unused
nodes in board dts.
BUT, we ended up having a bunch of maintenance issues and board bring
up problems and looking at the rest of the ARM ecosystems (you can
check the mailing list for all the discussions on the topic), we
flipped the order for peripherals that need board level connectivity
for functionality to be disabled in SoC.dtsi and enabled explicitly at
board level and when that occurred, specifically:
73676c480b72 ("arm64: dts: ti: k3-j721e: Enable OSPI nodes at the board
level") which enabled ospi0 at SoM level, but missed fixing this up,
whoops!
I will fix this up locally when I apply this patch. but FYI.
> Signed-off-by: Prasanth Babu Mantena <p-mantena@ti.com>
> ---
> Test log : https://gist.github.com/PrasanthBabuMantena/9dda540dce88282117de7e0e945e24ca
> arch/arm64/boot/dts/ti/k3-j721e-common-proc-board.dts | 1 +
> 1 file changed, 1 insertion(+)
>
> 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 e3d0ef6913b2..45311438315f 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
> @@ -573,6 +573,7 @@ &usb1 {
> &ospi1 {
> pinctrl-names = "default";
> pinctrl-0 = <&mcu_fss0_ospi1_pins_default>;
> + status = "okay";
>
> flash@0 {
> compatible = "jedec,spi-nor";
> --
> 2.34.1
>
>
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2025-05-09 9:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 5:07 [PATCH v2] arm64: dts: ti: k3-j721e-common-proc-board: Enable OSPI1 on J721E Prasanth Babu Mantena
2025-05-09 8:25 ` Nishanth Menon [this message]
2025-05-09 12:19 ` Nishanth Menon
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=20250509082509.ogfs2ulyfgk6etxc@unshaved \
--to=nm@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=p-mantena@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