From: Yixun Lan <dlan@kernel.org>
To: Junhui Liu <junhui.liu@pigmoral.tech>
Cc: u-boot@lists.u-boot-project.org, Yao Zi <me@ziyao.cc>,
u-boot-spacemit@groups.io, Tom Rini <trini@konsulko.com>,
Tim Ouyang <tim609@andestech.com>,
Leo Liang <leo.liang@sifive.com>, E Shattow <e@freeshell.de>,
Huan Zhou <pericycle.cc@gmail.com>,
Eric Chung <eric.chung@riscstar.com>
Subject: Re: [PATCH 3/5] riscv: dts: spacemit: k3: Add SPL device and image descriptions
Date: Fri, 6 Nov 2026 06:59:16 +0000 [thread overview]
Message-ID: <20261106065916-GKC249737@kernel.org> (raw)
In-Reply-To: <20261106-k3-ddr-v1-3-1e60e1d78020@pigmoral.tech>
Hi Junhui,
On 00:40 Fri 06 Nov , Junhui Liu wrote:
> Add the DDR controller node and mark the UART, I2C EEPROM and required
> clock and reset providers for use before DRAM initialization.
>
> Add a binman description for spl/u-boot-spl-mkimage.bin, combining SPL
> with the external LPDDR5 PMU IMEM firmware and wrapping the payload in
> a SpacemiT K3 boot image header.
>
> Signed-off-by: Junhui Liu <junhui.liu@pigmoral.tech>
> ---
> arch/riscv/dts/spacemit-k3-binman.dtsi | 24 +++++++++++++++
> arch/riscv/dts/spacemit-k3-u-boot.dtsi | 54 ++++++++++++++++++++++++++++++++++
> 2 files changed, 78 insertions(+)
>
..
> diff --git a/arch/riscv/dts/spacemit-k3-u-boot.dtsi b/arch/riscv/dts/spacemit-k3-u-boot.dtsi
> index 352e85e7de8..0976b2647b5 100644
> --- a/arch/riscv/dts/spacemit-k3-u-boot.dtsi
> +++ b/arch/riscv/dts/spacemit-k3-u-boot.dtsi
> @@ -4,3 +4,57 @@
> */
>
> #include "spacemit-k3-binman.dtsi"
> +
> +&{/soc} {
> + ddrc@cb000000 {
> + compatible = "spacemit,k3-ddrc";
> + reg = <0x0 0xcb000000 0x0 0x01000000>,
> + <0x0 0xcc000000 0x0 0x01000000>;
> + spacemit,apmu = <&syscon_apmu 0x4e8>;
> + bootph-pre-ram;
> + };
> +};
> +
I'm not sure if it's a good idea to also move "ddrc" to mainline kernel
dts, at least to reach a consensus about stable compatible name..
> +&i2c2 {
> + bootph-pre-ram;
> +
> + eeprom@50 {
> + bootph-pre-ram;
> + };
> +};
> +
For adding all "bootph-pre-ram" properties, I'd like to see patch
submission to mainline kernel tree, see similar thread for K1 SoC[1]
so eventually it will get synced to a proper directory under dts/upstream/..
But, I know it would take long time for the upstream dts hit into U-Boot
tree, so a compromised solution is that we temporarily accept this patch
before the sync, then fix it up later accordingly..
Link: https://lore.kernel.org/r/20261024092558.143621-1-alan.tseng.cs@gmail.com [1]
--
Yixun Lan (dlan)
next prev parent reply other threads:[~2026-11-06 6:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 16:40 [PATCH 0/5] riscv: spacemit: k3: Add SPL LPDDR5 initialization Junhui Liu
2026-11-05 16:40 ` [PATCH 1/5] ram: spacemit: Add DDR driver for K3 SoC Junhui Liu
2026-11-05 16:40 ` [PATCH 2/5] riscv: spacemit: k3: Add SPL initialization support Junhui Liu
2026-11-05 16:40 ` [PATCH 3/5] riscv: dts: spacemit: k3: Add SPL device and image descriptions Junhui Liu
2026-11-06 6:59 ` Yixun Lan [this message]
2026-11-07 9:06 ` Junhui Liu
2026-11-07 11:08 ` E Shattow
2026-11-05 16:40 ` [PATCH 4/5] configs: spacemit: k3: Enable SPL support Junhui Liu
2026-11-05 16:40 ` [PATCH 5/5] doc: spacemit: k3: Add SPL build instructions Junhui Liu
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=20261106065916-GKC249737@kernel.org \
--to=dlan@kernel.org \
--cc=e@freeshell.de \
--cc=eric.chung@riscstar.com \
--cc=junhui.liu@pigmoral.tech \
--cc=leo.liang@sifive.com \
--cc=me@ziyao.cc \
--cc=pericycle.cc@gmail.com \
--cc=tim609@andestech.com \
--cc=trini@konsulko.com \
--cc=u-boot-spacemit@groups.io \
--cc=u-boot@lists.u-boot-project.org \
/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