public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: E Shattow <e@freeshell.de>
Cc: u-boot@lists.denx.de, E Shattow <e@freeshell.de>,
	Rick Chen <rick@andestech.com>, Leo <ycliang@andestech.com>,
	Minda Chen <minda.chen@starfivetech.com>,
	Hal Feng <hal.feng@starfivetech.com>,
	Tom Rini <trini@konsulko.com>,
	Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Subject: [PATCH v3 0/4] riscv: dts: starfive: prune redundant jh7110-common
Date: Tue, 16 Sep 2025 17:02:21 -0700	[thread overview]
Message-ID: <20250917000254.1134031-1-e@freeshell.de> (raw)

There are more than a few additional JH7110 CPU boards that may soon be
upstreamed. Each new variant supported by U-Boot has the burden of adding
a per-dts stub file for automatic dtsi inclusion by the build system. Also
i.e. the JH7110S CPU board introduced by StarFive is to be supported by
the same U-Boot starfive_visionfive2 target. Let's prepare for and clean
out (remove) per-dts file -u-boot.dtsi automatic inclusion stubs for all
dts that exist in dts/upstream/src subtree, making these per-dts
-u-boot.dtsi files unnecessary for future additions.

The last patch in this series anticipates additional CPU models for
starfive_visionfive2 config, changing from SYS_CPU automatic inclusion
dtsi to a filename more similar to the defconfig name via config Extra
dtsi inclusion. This also allows that any supported board for this config
which does need to use the per-dts automatic dtsi inclusion by the build
system may do so without having to include this common dtsi again.

Changes since v2:
- Drop PATCH 4/4 "visionfive2 depend on SYS_CONFIG_NAME automatic dtsi
inclusion"
- Add patch "Use visionfive2 DEVICE_TREE_INCLUDES dtsi named similar to
defconfig"
- Revise cover letter descriptions

E Shattow (4):
  riscv: dts: starfive: prune redundant jh7110-common overrides
  riscv: dts: starfive: sync visionfive2 overrides with upstream Linux
    for-next
  riscv: dts: starfive: visionfive2 depend on SYS_CPU automatic dtsi
    inclusion
  configs: starfive: Use visionfive2 DEVICE_TREE_INCLUDES dtsi named
    similar to defconfig

 arch/riscv/dts/jh7110-common-u-boot.dtsi      | 99 -------------------
 .../jh7110-deepcomputing-fml13v01-u-boot.dtsi |  7 --
 arch/riscv/dts/jh7110-milkv-mars-u-boot.dtsi  |  7 --
 .../dts/jh7110-pine64-star64-u-boot.dtsi      |  7 --
 ...10-starfive-visionfive-2-v1.2a-u-boot.dtsi |  7 --
 ...10-starfive-visionfive-2-v1.3b-u-boot.dtsi |  7 --
 ....dtsi => starfive-visionfive2-u-boot.dtsi} | 82 ++++++---------
 configs/starfive_visionfive2_defconfig        |  1 +
 8 files changed, 33 insertions(+), 184 deletions(-)
 delete mode 100644 arch/riscv/dts/jh7110-common-u-boot.dtsi
 delete mode 100644 arch/riscv/dts/jh7110-deepcomputing-fml13v01-u-boot.dtsi
 delete mode 100644 arch/riscv/dts/jh7110-milkv-mars-u-boot.dtsi
 delete mode 100644 arch/riscv/dts/jh7110-pine64-star64-u-boot.dtsi
 delete mode 100644 arch/riscv/dts/jh7110-starfive-visionfive-2-v1.2a-u-boot.dtsi
 delete mode 100644 arch/riscv/dts/jh7110-starfive-visionfive-2-v1.3b-u-boot.dtsi
 rename arch/riscv/dts/{jh7110-u-boot.dtsi => starfive-visionfive2-u-boot.dtsi} (54%)


base-commit: b82fa9d752b025d3b5305b5b07debe6808a5d027
-- 
2.50.0


             reply	other threads:[~2025-09-17  0:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-17  0:02 E Shattow [this message]
2025-09-17  0:02 ` [PATCH v3 1/4] riscv: dts: starfive: prune redundant jh7110-common overrides E Shattow
2025-09-19 10:51   ` Leo Liang
2025-09-17  0:02 ` [PATCH v3 2/4] riscv: dts: starfive: sync visionfive2 overrides with upstream Linux for-next E Shattow
2025-09-17  2:59   ` E Shattow
2025-09-19 10:58   ` Leo Liang
2025-09-17  0:02 ` [PATCH v3 3/4] riscv: dts: starfive: visionfive2 depend on SYS_CPU automatic dtsi inclusion E Shattow
2025-09-19 10:58   ` Leo Liang
2025-09-17  0:02 ` [PATCH v3 4/4] configs: starfive: Use visionfive2 DEVICE_TREE_INCLUDES dtsi named similar to defconfig E Shattow
2025-09-19 10:59   ` Leo Liang

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=20250917000254.1134031-1-e@freeshell.de \
    --to=e@freeshell.de \
    --cc=hal.feng@starfivetech.com \
    --cc=heinrich.schuchardt@canonical.com \
    --cc=minda.chen@starfivetech.com \
    --cc=rick@andestech.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=ycliang@andestech.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