From: Conor Dooley <conor@kernel.org>
To: soc@kernel.org
Cc: conor@kernel.org, linux-riscv@lists.infradead.org
Subject: [GIT PULL] RISC-V Devicetrees for v6.13
Date: Fri, 8 Nov 2024 09:37:55 +0000 [thread overview]
Message-ID: <20241108-washboard-material-6b9ff196063d@spud> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2383 bytes --]
Hey,
Please pull a handful of changes, mostly for StarFive.
Branch is based on rc3 instead of rc1 as I'd usually do, because rc{1,2}
was not booting for me.
Cheers,
Conor.
The following changes since commit 8e929cb546ee42c9a61d24fae60605e9e3192354:
Linux 6.12-rc3 (2024-10-13 14:33:32 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/ tags/riscv-dt-for-v6.13
for you to fetch changes up to c8b72c301dbe71a7a55298d542dff7b2c3612765:
riscv: dts: starfive: add DeepComputing FML13V01 board device tree (2024-10-31 12:22:53 +0000)
----------------------------------------------------------------
RISC-V Devicetrees for v6.13
StarFive:
Support for the DeepComputing FML13V01, a Framework laptop compatible
with a JH7110. This board is fairly different to the more standard SBCs
offerings that the kernel already supports, so there's also some
refactoring of jh7110-common.dtsi to move out nodes unused on the new
board.
Spacemit:
A vendor prefix I grabbed from the basic support series, since its
dependencies are not yet ready but peripheral drivers have started being
merged.
Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
----------------------------------------------------------------
Guodong Xu (2):
riscv: dts: starfive: jh7110-common: revised device node
riscv: dts: starfive: jh7110-common: move usb0 config to board dts
Sandie Cao (3):
dt-bindings: vendor: add deepcomputing
dt-bindings: riscv: starfive: add deepcomputing,fml13v01
riscv: dts: starfive: add DeepComputing FML13V01 board device tree
Yangyu Chen (1):
dt-bindings: vendor-prefixes: add spacemit
.../devicetree/bindings/riscv/starfive.yaml | 1 +
.../devicetree/bindings/vendor-prefixes.yaml | 4 ++++
arch/riscv/boot/dts/starfive/Makefile | 1 +
arch/riscv/boot/dts/starfive/jh7110-common.dtsi | 10 ---------
.../dts/starfive/jh7110-deepcomputing-fml13v01.dts | 17 +++++++++++++++
arch/riscv/boot/dts/starfive/jh7110-milkv-mars.dts | 22 +++++++++++++++++++
.../boot/dts/starfive/jh7110-pine64-star64.dts | 22 +++++++++++++++++++
.../dts/starfive/jh7110-starfive-visionfive-2.dtsi | 25 ++++++++++++++++++++++
8 files changed, 92 insertions(+), 10 deletions(-)
create mode 100644 arch/riscv/boot/dts/starfive/jh7110-deepcomputing-fml13v01.dts
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
reply other threads:[~2024-11-08 9:38 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=20241108-washboard-material-6b9ff196063d@spud \
--to=conor@kernel.org \
--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