From: "Kumar, Udit" <u-kumar1@ti.com>
To: "Dutta, Anurag" <a-dutta@ti.com>, <nm@ti.com>, <vigneshr@ti.com>,
<kristo@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<gehariprasath@ti.com>
Subject: Re: [PATCH] arm64: dts: ti: k3-j721s2-common-proc-board: Add QSPI flash partition details
Date: Tue, 3 Feb 2026 10:35:51 +0530 [thread overview]
Message-ID: <10988add-dd63-47ca-ba5d-809694171f33@ti.com> (raw)
In-Reply-To: <9675d81c-12f5-4798-bad9-ecbb2349bb60@ti.com>
On 1/30/2026 1:30 PM, Dutta, Anurag wrote:
>
> On 22-01-2026 08:53, Kumar, Udit wrote:
>>
>> On 1/21/2026 10:48 AM, Anurag Dutta wrote:
>>> J721S2 EVM has MT25QU512AB 64 MiB Quad SPI NOR flash connected
>>> to OSPI1. Add the partition information as per bootloader.
>>>
>>> Signed-off-by: Anurag Dutta <a-dutta@ti.com>
>>> ---
>>> Test logs:
>>> https://gist.github.com/anuragdutta731/b65f63f22c69317d714b65a201438cbc
>>
>>
>> Thanks for logs, but these are for boot-loader and I don't think
>> u-boot consumes partition details.
>>
>> could you share logs for kernel as well.
>>
> Hi Udit
> Here are kernel logs :
> https://gist.github.com/anuragdutta731/d4ee38df3ed8889f44bf28ab163b1baf
Thanks Anurag,
I think, you need qspi.phypattern under bootph-all, as I see u-boot
stage will/may do phy-tuning.
While at this, same thing needs to be cascaded to ospi flash as well.
>>
>>
>>>
>>> .../dts/ti/k3-j721s2-common-proc-board.dts | 41
>>> +++++++++++++++++++
>>> 1 file changed, 41 insertions(+)
>>>
>>> diff --git a/arch/arm64/boot/dts/ti/k3-j721s2-common-proc-board.dts
>>> b/arch/arm64/boot/dts/ti/k3-j721s2-common-proc-board.dts
>>> index 4fea99519113..7faf9367dbb2 100644
>>> --- a/arch/arm64/boot/dts/ti/k3-j721s2-common-proc-board.dts
>>> +++ b/arch/arm64/boot/dts/ti/k3-j721s2-common-proc-board.dts
>>> @@ -530,6 +530,47 @@ flash@0 {
>>> cdns,tchsh-ns = <60>;
>>> cdns,tslch-ns = <60>;
>>> cdns,read-delay = <2>;
>>> +
>>> + partitions {
>>> + compatible = "fixed-partitions";
>>> + #address-cells = <1>;
>>> + #size-cells = <1>;
>>> +
>>> + partition@0 {
>>> + label = "qspi.tiboot3";
>>> + reg = <0x0 0x80000>;
>>> + };
>>> +
>>> + partition@80000 {
>>> + label = "qspi.tispl";
>>> + reg = <0x80000 0x200000>;
>>> + };
>>> +
>>> + partition@280000 {
>>> + label = "qspi.u-boot";
>>> + reg = <0x280000 0x400000>;
>>> + };
>>> +
>>> + partition@680000 {
>>> + label = "qspi.env";
>>> + reg = <0x680000 0x40000>;
>>> + };
>>> +
>>> + partition@6c0000 {
>>> + label = "qspi.env.backup";
>>> + reg = <0x6c0000 0x40000>;
>>> + };
>>> +
>>> + partition@800000 {
>>> + label = "qspi.rootfs";
>>> + reg = <0x800000 0x37c0000>;
>>> + };
>>> +
>>> + partition@3fc0000 {
>>> + label = "qspi.phypattern";
>>> + reg = <0x3fc0000 0x40000>;
>>> + };
>>> + };
>>> };
>>> };
prev parent reply other threads:[~2026-02-03 5:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 5:18 Anurag Dutta
2026-01-22 3:23 ` Kumar, Udit
2026-01-30 8:00 ` Dutta, Anurag
2026-02-03 5:05 ` 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=10988add-dd63-47ca-ba5d-809694171f33@ti.com \
--to=u-kumar1@ti.com \
--cc=a-dutta@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=gehariprasath@ti.com \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@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®