From: Conor Dooley <conor@kernel.org>
To: soc@kernel.org
Cc: conor@kernel.org, linux-riscv@lists.infradead.org, kernel@esmil.dk
Subject: [GIT PULL] RISC-V Devicetrees for v6.19
Date: Thu, 27 Nov 2025 17:21:12 +0000 [thread overview]
Message-ID: <20251127-unthread-probable-75bbd4e737f5@spud> (raw)
[-- Attachment #1: Type: text/plain, Size: 4244 bytes --]
Hey folks,
Please pull my devicetree updates for 6.19.
Cheers,
Conor.
The following changes since commit 3a8660878839faadb4f1a6dd72c3179c1df56787:
Linux 6.18-rc1 (2025-10-12 13:42:36 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/ riscv-dt-for-v6.19
for you to fetch changes up to 5b70764e10190d57e6cd3287d3a3b06f8c89f69c:
riscv: dts: starfive: add Orange Pi RV (2025-11-25 22:20:54 +0000)
----------------------------------------------------------------
RISC-V Devicetrees for v6.19
MAINTAINERS:
There's some re-jigging of things to reduce duplication, by moving me
into the StarFive entry and my tree into the Microchip one. The
other platforms that I look after (SiFive and Canaan) are marked as Odd
Fixes to better represent their status. Nothing functionally changes.
Microchip:
Add adc and mmc nodes for the Beagle-V Fire.
SiFive:
Add pwm fans to the unmatched board.
StarFive:
Add the Orange PI RV board, another VisionFive 2 derived SBC. This
required moving a mmc related nodes out of the common file, into
<board>.dts. Yet more things moved out of the common file when the
VisionFive 2 Lite boards were added, which use the JH7110S SoC instead of
the JH7110. The difference here between SoCs is just temperature and
frequency ranges, but the boards differ enough that the pool of common
nodes decreases a little further. There's an eMMC and an SD variant
here, that are different SKUs, bringing the total new StarFive boards to
three.
Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
----------------------------------------------------------------
Conor Dooley (5):
riscv: dts: microchip: enable qspi adc/mmc-spi-slot on BeagleV Fire
MAINTAINERS: add Conor to StarFive entry
MAINTAINERS: remove patchwork from RISC-V MISC SOC SUPPORT
MAINTAINERS: add tree to RISC-V Microchip entry
MAINTAINERS: degrade RISC-V MISC SOC SUPPORT to Odd Fixes
E Shattow (1):
dts: starfive: jh7110-common: split out mmc0 reset pins from common into boards
Hal Feng (5):
dt-bindings: riscv: Add StarFive JH7110S SoC and VisionFive 2 Lite board
riscv: dts: starfive: jh7110-common: Move out some nodes to the board dts
riscv: dts: starfive: Add common board dtsi for VisionFive 2 Lite variants
riscv: dts: starfive: Add VisionFive 2 Lite board device tree
riscv: dts: starfive: Add VisionFive 2 Lite eMMC board device tree
Icenowy Zheng (2):
dt-bindings: riscv: starfive: add xunlong,orangepi-rv
riscv: dts: starfive: add Orange Pi RV
René Rebe (1):
riscv: dts: sifive: unmatched: Add PWM controlled fans
.../devicetree/bindings/riscv/starfive.yaml | 7 +
MAINTAINERS | 9 +-
.../riscv/boot/dts/microchip/mpfs-beaglev-fire.dts | 96 ++++++++++++
.../riscv/boot/dts/sifive/hifive-unmatched-a00.dts | 10 ++
arch/riscv/boot/dts/starfive/Makefile | 3 +
arch/riscv/boot/dts/starfive/jh7110-common.dtsi | 19 ---
.../dts/starfive/jh7110-deepcomputing-fml13v01.dts | 27 ++++
arch/riscv/boot/dts/starfive/jh7110-milkv-mars.dts | 27 ++++
.../boot/dts/starfive/jh7110-milkv-marscm-emmc.dts | 9 ++
.../boot/dts/starfive/jh7110-milkv-marscm-lite.dts | 1 +
.../boot/dts/starfive/jh7110-milkv-marscm.dtsi | 13 ++
.../riscv/boot/dts/starfive/jh7110-orangepi-rv.dts | 76 ++++++++++
.../boot/dts/starfive/jh7110-pine64-star64.dts | 27 ++++
.../jh7110-starfive-visionfive-2-lite-emmc.dts | 22 +++
.../starfive/jh7110-starfive-visionfive-2-lite.dts | 20 +++
.../jh7110-starfive-visionfive-2-lite.dtsi | 161 +++++++++++++++++++++
.../dts/starfive/jh7110-starfive-visionfive-2.dtsi | 24 +++
17 files changed, 528 insertions(+), 23 deletions(-)
create mode 100644 arch/riscv/boot/dts/starfive/jh7110-orangepi-rv.dts
create mode 100644 arch/riscv/boot/dts/starfive/jh7110-starfive-visionfive-2-lite-emmc.dts
create mode 100644 arch/riscv/boot/dts/starfive/jh7110-starfive-visionfive-2-lite.dts
create mode 100644 arch/riscv/boot/dts/starfive/jh7110-starfive-visionfive-2-lite.dtsi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2025-11-27 17:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 17:21 Conor Dooley [this message]
2025-11-27 22:10 ` [GIT PULL] RISC-V Devicetrees for v6.19 patchwork-bot+linux-soc
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=20251127-unthread-probable-75bbd4e737f5@spud \
--to=conor@kernel.org \
--cc=kernel@esmil.dk \
--cc=linux-riscv@lists.infradead.org \
--cc=soc@kernel.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