From: Yixun Lan <dlan@gentoo.org>
To: soc@kernel.org
Cc: Meng Zhang <zhangmeng.kevin@linux.spacemit.com>,
Arnd Bergmann <arnd@arndb.de>,
Inochi Amaoto <inochiama@gmail.com>,
Jesse Taube <mr.bossman075@gmail.com>,
Yangyu Chen <cyy@cyyself.name>, Conor Dooley <conor@kernel.org>,
linux-riscv <linux-riscv@lists.infradead.org>
Subject: [GIT PULL] RISC-V SpacemiT Devicetrees for v6.14
Date: Wed, 8 Jan 2025 22:21:22 +0800 [thread overview]
Message-ID: <20250108142122-GYA3300457@gentoo> (raw)
Hi Arnd,
Here is SpacemiT's device tree changes for 6.14 cycle.
All patches have been merged in linux-next tree for testing.
Please pull, thanks
Yixun Lan (dlan)
The following changes since commit 78d4f34e2115b517bcbfe7ec0d018bbbb6f9b0b8:
Linux 6.13-rc3 (2024-12-15 15:58:23 -0800)
are available in the Git repository at:
https://github.com/spacemit-com/linux/ tags/spacemit-dt-for-6.14
for you to fetch changes up to e7cd95ad8013bc232316bba0a52ea11ecd5c81bd:
riscv: dts: spacemit: add pinctrl property to uart0 in BPI-F3 (2025-01-04 10:28:18 +0800)
----------------------------------------------------------------
RISC-V SpacemiT DT changes for 6.14
- basic device tree support
- pinctrl dt node info
- update MAINTAINERS info
----------------------------------------------------------------
Yangyu Chen (8):
dt-bindings: riscv: Add SpacemiT X60 compatibles
dt-bindings: riscv: add SpacemiT K1 bindings
dt-bindings: timer: Add SpacemiT K1 CLINT
dt-bindings: interrupt-controller: Add SpacemiT K1 PLIC
riscv: add SpacemiT SoC family Kconfig support
riscv: dts: add initial SpacemiT K1 SoC device tree
riscv: dts: spacemit: add Banana Pi BPI-F3 board device tree
riscv: defconfig: enable SpacemiT SoC
Yixun Lan (3):
MAINTAINERS: setup support for SpacemiT SoC tree
dt-bindings: serial: 8250: Add SpacemiT K1 uart compatible
riscv: dts: spacemit: add pinctrl property to uart0 in BPI-F3
.../interrupt-controller/sifive,plic-1.0.0.yaml | 1 +
Documentation/devicetree/bindings/riscv/cpus.yaml | 1 +
.../devicetree/bindings/riscv/spacemit.yaml | 28 ++
Documentation/devicetree/bindings/serial/8250.yaml | 4 +-
.../devicetree/bindings/timer/sifive,clint.yaml | 1 +
MAINTAINERS | 9 +
arch/riscv/Kconfig.socs | 5 +
arch/riscv/boot/dts/Makefile | 1 +
arch/riscv/boot/dts/spacemit/Makefile | 2 +
arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts | 22 +
arch/riscv/boot/dts/spacemit/k1-pinctrl.dtsi | 20 +
arch/riscv/boot/dts/spacemit/k1.dtsi | 464 +++++++++++++++++++++
arch/riscv/configs/defconfig | 1 +
13 files changed, 558 insertions(+), 1 deletion(-)
create mode 100644 Documentation/devicetree/bindings/riscv/spacemit.yaml
create mode 100644 arch/riscv/boot/dts/spacemit/Makefile
create mode 100644 arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts
create mode 100644 arch/riscv/boot/dts/spacemit/k1-pinctrl.dtsi
create mode 100644 arch/riscv/boot/dts/spacemit/k1.dtsi
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2025-01-08 14:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 14:21 Yixun Lan [this message]
2025-01-16 16:49 ` [GIT PULL] RISC-V SpacemiT Devicetrees for v6.14 Arnd Bergmann
2025-01-16 23:47 ` Yixun Lan
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=20250108142122-GYA3300457@gentoo \
--to=dlan@gentoo.org \
--cc=arnd@arndb.de \
--cc=conor@kernel.org \
--cc=cyy@cyyself.name \
--cc=inochiama@gmail.com \
--cc=linux-riscv@lists.infradead.org \
--cc=mr.bossman075@gmail.com \
--cc=soc@kernel.org \
--cc=zhangmeng.kevin@linux.spacemit.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