On 9/4/25 22:02, E Shattow wrote: > Rename visionfive2 per-cpu jh7110-u-boot.dtsi to > starfive-visionfive2-u-boot.dtsi for inclusion by search order for whole > starfive_visionfive2 target. There is expected to be support for multiple > CPUs and boards, so let's use the automatic dtsi inclusion that is a > better match for this. > > Depends on patch: "scripts/Makefile.lib: add CONFIG_SYS_CONFIG_NAME prefix > to dtsi search" [1]. > 1: https://lore.kernel.org/u-boot/[email protected]/ > > Signed-off-by: E Shattow <[email protected]> > --- > .../dts/{jh7110-u-boot.dtsi => starfive-visionfive2-u-boot.dtsi} | 0 > 1 file changed, 0 insertions(+), 0 deletions(-) > rename arch/riscv/dts/{jh7110-u-boot.dtsi => > starfive-visionfive2-u-boot.dtsi} (100%) > > diff --git a/arch/riscv/dts/jh7110-u-boot.dtsi > b/arch/riscv/dts/starfive-visionfive2-u-boot.dtsi > similarity index 100% > rename from arch/riscv/dts/jh7110-u-boot.dtsi > rename to arch/riscv/dts/starfive-visionfive2-u-boot.dtsi
N.B. I guessed wrong the SYS_CONFIG_NAME is not representative of any defconfig name. v3 replaces this patch 4/4 and refers to starfive-visionfive2-u-boot.dtsi via CONFIG_DEVICE_TREE_INCLUDES extra .dtsi include in defconfig. That unfortunately makes it less visible for DEVICE_TREE_DEBUG=1 so I am also having a look at improving the dtsi automatic inclusion and DEVICE_TREE_INCLUDES handling. Anyhow "config name" in context of SYS_CONFIG_NAME is perhaps referring to the Kconfig config fragment include '.h' file no relation to any defconfig. -E
