Hi Yixun, On 10/1/26 18:03, Yixun Lan wrote: > SpacemiT K3 follow the standard riscv binman layout, which has opensbi > and U-Boot proper, so include the common binman dtsi file. > > Signed-off-by: Yixun Lan <[email protected]> > --- > arch/riscv/dts/k3-u-boot.dtsi | 6 ++++++ > 1 file changed, 6 insertions(+) > > diff --git a/arch/riscv/dts/k3-u-boot.dtsi b/arch/riscv/dts/k3-u-boot.dtsi > new file mode 100644 > index 00000000000..f1c1c3ee6fd > --- /dev/null > +++ b/arch/riscv/dts/k3-u-boot.dtsi > @@ -0,0 +1,6 @@ > +// SPDX-License-Identifier: GPL-2.0+ OR MIT > +/* > + * Copyright (C) 2026 Yixun Lan <[email protected]> > + */ > + > +#include "binman.dtsi" >
Please rename k3-u-boot.dtsi as similar to the target defconfig (e.g. spacemit-k3-u-boot.dtsi) while avoiding any matches for the automatic SOC/CPU/VENDOR inclusion routine of scripts/Makefile.lib:222. Add the CONFIG_DEVICE_TREE_INCLUDES="spacemit-k3-u-boot.dtsi" board defconfig option to ensure its inclusion. The automatic inclusion of per-CPU -u-boot.dtsi does short-circuit any automatic inclusion of per-target-board -u-boot.dtsi, and so becomes a blocker in the situation where we would need to override something per-board on a multi-board capable u-boot target (Pico-ITX, CoM260, FML13v05, so I think this is likely). Essentially repeating here my previous advice to Hal about adding a new multi-board target from https://lore.kernel.org/u-boot/[email protected]/ Thanks, -E
