From: Yixun Lan <dlan@kernel.org>
To: Yao Zi <me@ziyao.cc>
Cc: Aurelien Jarno <aurelien@aurel32.net>,
linux-kernel@vger.kernel.org, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"open list:RISC-V ARCHITECTURE" <linux-riscv@lists.infradead.org>,
"open list:RISC-V SPACEMIT SoC Support"
<spacemit@lists.linux.dev>
Subject: Re: [PATCH 4/6] riscv: dts: spacemit: enable QSPI and add SPI NOR on Milk-V Jupiter
Date: Wed, 25 Mar 2026 05:59:37 +0800 [thread overview]
Message-ID: <20260324215937-GKA767626@kernel.org> (raw)
In-Reply-To: <acLE5xnEBoCtW4Vw@pie>
Hi Yao,
On 17:07 Tue 24 Mar , Yao Zi wrote:
> On Tue, Mar 24, 2026 at 05:02:20PM +0800, Yixun Lan wrote:
> > Hi Aurelien,
> >
> > On 21:28 Sun 22 Mar , Aurelien Jarno wrote:
> > > Add the QSPI controller node for the Milk-V Jupiter board and describe
> > > the attached SPI NOR flash (GD25Q64E).
> > >
> > > The flash supports a frequency up to 133MHz (80 MHz for reads), and the
> > > SoC supports a frequency up to 104 MHz. However tests have shown that
> > > the flash is not reliably detected above 26.5 MHz, consistent with
> > > frequency used in the vendor kernel. Therefore, use this frequency.
> > >
> > ..
> > > The m25p,fast-read properties is taken from the vendor kernel.
> > >
> > So long as this is verified and works fine on board?
> >
> > > Add a corresponding flash partition layout, matching the layout and the
> > > names used in the vendor U-Boot.
> > >
> > ..
> > > Also add the bootph-pre-ram property to make the device tree usable by
> > > early firmware/bootloaders without modification, as U-Boot is stored on
> > > this NOR flash.
> > Is the dtb file actually used by U-Boot? I'd highly doubt about this,
> > if not the case or has not been tested, I'd suggest then not to add
> > this property..
>
> Currently no, but it would be a bogus if we could do it at introduction
> of the device, if it's really necessary in pre-DRAM stages of
> bootloaders, e.g. U-Boot SPL. This would reduce the duplicated work of
> downstream projects if they decide to switch to Linux upstream
> devicetree.
>
All above arguments are based on assumption, I object to add things randomly
without real test proved.
Let's wait once U-Boot actually switch to use upstream devicetree.
> As SpacemiT K1 supports booting from flash, the description of flash
> nodes are likely useful for pre-DRAM bootloaders.
>
This is still a 'likely' ..
> > >
> > > Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
>
> Best regards,
> Yao Zi
--
Yixun Lan (dlan)
next prev parent reply other threads:[~2026-03-24 21:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-22 20:28 [PATCH 0/6] riscv: dts: spacemit: enable more devices Aurelien Jarno
2026-03-22 20:28 ` [PATCH 1/6] riscv: dts: spacemit: add LEDs for Milk-V Jupiter board Aurelien Jarno
2026-03-24 7:54 ` Javier Martinez Canillas
2026-03-22 20:28 ` [PATCH 2/6] riscv: dts: spacemit: add 24c04 eeprom on Milk-V Jupiter Aurelien Jarno
2026-03-24 7:55 ` Javier Martinez Canillas
2026-03-22 20:28 ` [PATCH 3/6] riscv: dts: spacemit: add i2c aliases " Aurelien Jarno
2026-03-24 7:56 ` Javier Martinez Canillas
2026-03-22 20:28 ` [PATCH 4/6] riscv: dts: spacemit: enable QSPI and add SPI NOR " Aurelien Jarno
2026-03-24 9:02 ` Yixun Lan
2026-03-24 17:07 ` Yao Zi
2026-03-24 21:59 ` Yixun Lan [this message]
2026-03-24 21:19 ` Aurelien Jarno
2026-03-24 22:09 ` Yixun Lan
2026-03-22 20:28 ` [PATCH 5/6] riscv: dts: spacemit: enable USB 3 ports " Aurelien Jarno
2026-03-24 8:01 ` Javier Martinez Canillas
2026-03-22 20:28 ` [PATCH 6/6] riscv: dts: spacemit: enable PCIe " Aurelien Jarno
2026-03-24 8:02 ` Javier Martinez Canillas
2026-03-26 7:34 ` Yixun Lan
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=20260324215937-GKA767626@kernel.org \
--to=dlan@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=aurelien@aurel32.net \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=me@ziyao.cc \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=robh@kernel.org \
--cc=spacemit@lists.linux.dev \
/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