[GIT PULL] RISC-V SpacemiT Devicetrees for v7.1

[GIT PULL] RISC-V SpacemiT Devicetrees for v7.1

[Yixun Lan]

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

Re: [GIT PULL] RISC-V SpacemiT Devicetrees for v7.1

[Linus Walleij]

Hi Yixun,

I looked into this pull request.

I'm sorry if I do stupid mistakes in handling it, I'm new to maintaining
the SoC tree. Bear with me.

On Fri, Apr 3, 2026 at 2:32 PM Yixun Lan <dlan@kernel.org> wrote:

> Aurelien Jarno (7):
>       riscv: dts: spacemit: drop incorrect pinctrl for combo PHY
(...)
> Yixun Lan (9):
>       riscv: dts: spacemit: pcie: fix missing power regulator

[Fixes]
fatal: Not a valid object name linus/master
Commit: c68360c0d636 ("riscv: dts: spacemit: drop incorrect pinctrl
for combo PHY")
    Fixes tag: Fixes: 0be016a4b5d1b9 ("riscv: dts: spacemit: PCIe and
PHY-related updates")
    Has these problem(s):
        - Inspect: Target SHA is not ancestor of Linus' master branch,
which means it is fixing commit in your branch
fatal: Not a valid object name linus/master
Commit: 8a9071299dec ("riscv: dts: spacemit: pcie: fix missing power regulator")
    Fixes tag: Fixes: 0be016a4b5d1 ("riscv: dts: spacemit: PCIe and
PHY-related updates")
    Has these problem(s):
        - Inspect: Target SHA is not ancestor of Linus' master branch,
which means it is fixing commit in your branch

So this means you introduced bugs and fix them in the same pull request?

Why?

The practice is to squash such fixes into the offending patches when
presenting pull requests. But I went ahead anyway, trying to not be so
picky. (The commits are there, in your branch indeed.)

- Checked that it was in linux-next OK
- built DTBS OK

Pulled in, thanks.

Yours,
Linus Walleij

Re: [GIT PULL] RISC-V SpacemiT Devicetrees for v7.1

[Yixun Lan]

Hi Linus,

On 00:19 Sat 11 Apr     , Linus Walleij wrote:
> Hi Yixun,
> 
> I looked into this pull request.
> 
> I'm sorry if I do stupid mistakes in handling it, I'm new to maintaining
> the SoC tree. Bear with me.
> 
> On Fri, Apr 3, 2026 at 2:32 PM Yixun Lan <dlan@kernel.org> wrote:
> 
> > Aurelien Jarno (7):
> >       riscv: dts: spacemit: drop incorrect pinctrl for combo PHY
> (...)
> > Yixun Lan (9):
> >       riscv: dts: spacemit: pcie: fix missing power regulator
> 
> [Fixes]
> fatal: Not a valid object name linus/master
Could be the problem that your master branch isn't up-to-date?

> Commit: c68360c0d636 ("riscv: dts: spacemit: drop incorrect pinctrl
> for combo PHY")
..
>     Fixes tag: Fixes: 0be016a4b5d1b9 ("riscv: dts: spacemit: PCIe and
> PHY-related updates")
Above commit was merged for v7.0 cycle, while this PR is for v7.1
The fix isn't that critical and didn't cause any run-time issue, so
I do the fix in this v7.1 cycle..

>     Has these problem(s):
>         - Inspect: Target SHA is not ancestor of Linus' master branch,
> which means it is fixing commit in your branch
> fatal: Not a valid object name linus/master
> Commit: 8a9071299dec ("riscv: dts: spacemit: pcie: fix missing power regulator")
>     Fixes tag: Fixes: 0be016a4b5d1 ("riscv: dts: spacemit: PCIe and
> PHY-related updates")
>     Has these problem(s):
>         - Inspect: Target SHA is not ancestor of Linus' master branch,
> which means it is fixing commit in your branch
> 
> So this means you introduced bugs and fix them in the same pull request?
> 
> Why?
> 
> The practice is to squash such fixes into the offending patches when
> presenting pull requests. But I went ahead anyway, trying to not be so
> picky. (The commits are there, in your branch indeed.)
> 
Glad to learn this, I will keep it in mind..

> - Checked that it was in linux-next OK
Right, I think the commit is actually in v7.0-rc1

> - built DTBS OK
> 
> Pulled in, thanks.
Thank you

> 
> Yours,
> Linus Walleij

-- 
Yixun Lan (dlan)