From: Yixun Lan <dlan@kernel.org>
To: soc@kernel.org
Cc: Yixun Lan <dlan@gentoo.org>, Arnd Bergmann <arnd@arndb.de>,
spacemit@lists.linux.dev, linux-riscv@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] RISC-V SpacemiT Devicetrees for v7.1
Date: Fri, 3 Apr 2026 12:32:06 +0000 [thread overview]
Message-ID: <20260403123040-KYC0145825@kernel.org> (raw)
From: Yixun Lan <dlan@gentoo.org>
Hi Arnd,
Please pull SpacemiT's DeviceTree changes for v7.1
Yixun Lan
The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:
Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
are available in the Git repository at:
https://github.com/spacemit-com/linux tags/spacemit-dt-for-7.1-1
for you to fetch changes up to af62a095eb0c3359d477b55ef72d2afd94c83c8f:
dts: riscv: spacemit: k3: add P1 PMIC regulator tree (2026-03-30 04:42:10 +0000)
----------------------------------------------------------------
RISC-V SpacemiT DT changes for 7.1
For K3 SoC
- Add I2C support
- Add PMIC regulator tree
- Add ethernet support
- Add pinctrl/GPIO/Clock
- Enable full UART support
For K1 SoC
On Milk-V Jupiter
- Enable PCIe/USB on
- Enable QSPI/SPI NOR
- Enable EEPROM, LEDs
Others
- Fix PMIC supply properties
- Fix PCIe missing power regulator
----------------------------------------------------------------
Aurelien Jarno (7):
riscv: dts: spacemit: drop incorrect pinctrl for combo PHY
riscv: dts: spacemit: add LEDs for Milk-V Jupiter board
riscv: dts: spacemit: add 24c04 eeprom on Milk-V Jupiter
riscv: dts: spacemit: add i2c aliases on Milk-V Jupiter
riscv: dts: spacemit: enable QSPI and add SPI NOR on Milk-V Jupiter
riscv: dts: spacemit: enable USB 3 ports on Milk-V Jupiter
riscv: dts: spacemit: enable PCIe ports on Milk-V Jupiter
Chukun Pan (2):
riscv: dts: spacemit: Add 'linux,pci-domain' to PCIe nodes for K1
riscv: dts: spacemit: reorder phy nodes for K1
Guodong Xu (1):
riscv: dts: spacemit: Update PMIC supply properties for BPI-F3 and Jupiter
Inochi Amaoto (1):
riscv: dts: spacemit: Add ethernet device for K3
Yixun Lan (9):
riscv: dts: spacemit: pcie: fix missing power regulator
riscv: dts: spacemit: adapt regulator node name to preferred form
dt-bindings: serial: 8250: spacemit: fix clock property for K3 SoC
riscv: dts: spacemit: k3: add clock tree
riscv: dts: spacemit: k3: add pinctrl support
riscv: dts: spacemit: k3: add GPIO support
riscv: dts: spacemit: k3: add full resource to UART
dts: riscv: spacemit: k3: Add i2c nodes
dts: riscv: spacemit: k3: add P1 PMIC regulator tree
Documentation/devicetree/bindings/serial/8250.yaml | 5 +-
arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts | 26 +-
arch/riscv/boot/dts/spacemit/k1-milkv-jupiter.dts | 204 +++++++++++-
arch/riscv/boot/dts/spacemit/k1.dtsi | 112 ++++---
arch/riscv/boot/dts/spacemit/k3-pico-itx.dts | 170 ++++++++++
arch/riscv/boot/dts/spacemit/k3-pinctrl.dtsi | 69 ++++
arch/riscv/boot/dts/spacemit/k3.dtsi | 369 ++++++++++++++++++++-
7 files changed, 876 insertions(+), 79 deletions(-)
create mode 100644 arch/riscv/boot/dts/spacemit/k3-pinctrl.dtsi
reply other threads:[~2026-04-03 12:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260403123040-KYC0145825@kernel.org \
--to=dlan@kernel.org \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=dlan@gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=soc@kernel.org \
--cc=spacemit@lists.linux.dev \
/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