All of lore.kernel.org
 help / color / mirror / Atom feed
From: E Shattow <e@freeshell.de>
To: Minda Chen <minda.chen@starfivetech.com>,
	Hal Feng <hal.feng@starfivetech.com>,
	Tom Rini <trini@konsulko.com>
Cc: u-boot@lists.denx.de, E Shattow <e@freeshell.de>
Subject: [RFC v1 0/4] Add upstream boards Milk-V Mars CM and Mars CM Lite
Date: Wed, 24 Sep 2025 22:32:04 -0700	[thread overview]
Message-ID: <20250925053233.1874027-1-e@freeshell.de> (raw)

Milk-V Mars CM and Mars CM Lite SoM's were formerly supported v2024.07 to
v2025.01 and then absent since the OF_UPSTREAM transition of starfive
visionfive2 multi-board support. Upstream patches are now queued up for the
next merge window to Linux v6.18, so let's re-introduce support for these
boards.

Sorting of OF_LIST is kept consistent with `LANG=C sort`, and callbacks in
SPL for dts selection are ordered the same. Logic for setting fdtfile env
variable corresponds with the sorting of OF_LIST and not the representative
EEPROM value comparisons.

This series does violate some norms as it modifies the dts/upstream tree,
and generally is introducing as upstream something which is not quite yet
stable or release candidate in upstream devicetree-rebasing. RFC patches
sent this way for review would benefit from not modifying dts/upstream
tree at all but here it is done with empty files to pacify the build
system. Actual dts content is simply copied to arch/$ARCH/dts as automatic
inclusion dtsi. This pretends that if merged, then when upstream changes
appear in devicetree-rebasing it would be only this updated content which
can easily be reverted and empty placeholder files in dts/upstream be
merged with less tedious conflict resolution.

For development with a local Linux source tree, the dtsi files for
automatic inclusion may simply have a 1-liner include to the location of
the corresponding dts file from that Linux source tree.

Open to comments about how best to encourage early review of series like
this (notable is StarFive VisionFive2 Lite new product recently posted)
when there is a hard dependency on both the OF_LIST of a multi-board
target as starfive visionfive2 is and the dts which may not yet be
available from dts/upstream devicetree-rebasing.

E Shattow (4):
  riscv: dts: starfive: Add Milk-V Mars CM and Mars CM Lite from
    upstream Linux for-next
  board: starfive: visionfive2: Add Milk-V Mars CM and Mars CM Lite
    selection by product_id
  riscv: dts: Add placeholder files for pending upstream Milk-V Mars CM
    and Mars CM Lite
  configs: starfive: Add Milk-V Mars CM and Mars CM Lite to visionfive2

 .../dts/jh7110-milkv-marscm-emmc-u-boot.dtsi  |  12 ++
 .../dts/jh7110-milkv-marscm-lite-u-boot.dtsi  |  25 +++
 arch/riscv/dts/jh7110-milkv-marscm.dtsi       | 159 ++++++++++++++++++
 board/starfive/visionfive2/spl.c              |   8 +
 .../visionfive2/starfive_visionfive2.c        |   6 +
 configs/starfive_visionfive2_defconfig        |   2 +-
 .../starfive/jh7110-milkv-marscm-emmc.dts     |   0
 .../starfive/jh7110-milkv-marscm-lite.dts     |   0
 8 files changed, 211 insertions(+), 1 deletion(-)
 create mode 100644 arch/riscv/dts/jh7110-milkv-marscm-emmc-u-boot.dtsi
 create mode 100644 arch/riscv/dts/jh7110-milkv-marscm-lite-u-boot.dtsi
 create mode 100644 arch/riscv/dts/jh7110-milkv-marscm.dtsi
 create mode 100644 dts/upstream/src/riscv/starfive/jh7110-milkv-marscm-emmc.dts
 create mode 100644 dts/upstream/src/riscv/starfive/jh7110-milkv-marscm-lite.dts


base-commit: e482fdbbca935de32400054eb532de45b1cc01cb
-- 
2.50.0


             reply	other threads:[~2025-09-25  5:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-25  5:32 E Shattow [this message]
2025-09-25  5:32 ` [RFC v1 1/4] riscv: dts: starfive: Add Milk-V Mars CM and Mars CM Lite from upstream Linux for-next E Shattow
2025-09-25  5:32 ` [RFC v1 2/4] board: starfive: visionfive2: Add Milk-V Mars CM and Mars CM Lite selection by product_id E Shattow
2025-09-25  5:32 ` [RFC v1 3/4] riscv: dts: Add placeholder files for pending upstream Milk-V Mars CM and Mars CM Lite E Shattow
2025-09-25  5:32 ` [RFC v1 4/4] configs: starfive: Add Milk-V Mars CM and Mars CM Lite to visionfive2 E Shattow
2025-10-02  6:28 ` [RFC v1 0/4] Add upstream boards Milk-V Mars CM and Mars CM Lite E Shattow

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=20250925053233.1874027-1-e@freeshell.de \
    --to=e@freeshell.de \
    --cc=hal.feng@starfivetech.com \
    --cc=minda.chen@starfivetech.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.