From: Guodong Xu <guodong@riscstar.com>
To: Conor Dooley <conor@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Emil Renner Berthing <kernel@esmil.dk>,
rafal@milecki.pl
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Neil Armstrong <neil.armstrong@linaro.org>,
Heiko Stuebner <heiko.stuebner@cherry.de>,
Michael Zhu <michael.zhu@starfivetech.com>,
Drew Fustini <drew@beagleboard.org>,
Alexandru Stan <ams@frame.work>, Daniel Schaefer <dhs@frame.work>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sandie Cao <sandie.cao@deepcomputing.io>,
Yuning Liang <yuning.liang@deepcomputing.io>,
Huiming Qiu <huiming.qiu@deepcomputing.io>,
Alex Elder <elder@riscstar.com>,
linux@frame.work, devicetree@vger.kernel.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
Guodong Xu <guodong@riscstar.com>
Subject: [PATCH v4 3/3] riscv: dts: starfive: add DeepComputing FML13V01 board device tree
Date: Sun, 20 Oct 2024 00:26:05 +0800 [thread overview]
Message-ID: <20241019162605.308475-4-guodong@riscstar.com> (raw)
In-Reply-To: <20241019162605.308475-1-guodong@riscstar.com>
From: Sandie Cao <sandie.cao@deepcomputing.io>
The FML13V01 board from DeepComputing incorporates a StarFive JH7110 SoC.
It is a mainboard designed for the Framework Laptop 13 Chassis, which has
(Framework) SKU FRANHQ0001.
The FML13V01 board features:
- StarFive JH7110 SoC
- LPDDR4 8GB
- eMMC 32GB or 128GB
- QSPI Flash
- MicroSD Slot
- PCIe-based Wi-Fi
- 4 USB-C Ports
- Port 1: PD 3.0 (60W Max), USB 3.2 Gen 1, DP 1.4 (4K@30Hz/2.5K@60Hz)
- Port 2: PD 3.0 (60W Max), USB 3.2 Gen 1
- Port 3 & 4: USB 3.2 Gen 1
Create the DTS file for the DeepComputing FML13V01 board. Seven device
nodes have been verified functional and remain enabled: i2c2, i2c5, i2c6
qspi, mmc0, mmc1 and usb0. All others remain disabled, or are disabled
by nodes in "jh7110-deepcomputing-fml13v01.dts".
Signed-off-by: Sandie Cao <sandie.cao@deepcomputing.io>
[elder@riscstar.com: revised the description, updated some nodes]
Signed-off-by: Alex Elder <elder@riscstar.com>
Signed-off-by: Guodong Xu <guodong@riscstar.com>
---
v4: Changed model string to "DeepComputing FML13V01"
Changed dts filename and Makefile accordingly to reflect the change
Updated device nodes status, and verified functional
Revised the commit message
v3: Updated the commit message
v2: Changed the model and copmatible strings
Updated the commit message with board features
arch/riscv/boot/dts/starfive/Makefile | 1 +
.../jh7110-deepcomputing-fml13v01.dts | 44 +++++++++++++++++++
2 files changed, 45 insertions(+)
create mode 100644 arch/riscv/boot/dts/starfive/jh7110-deepcomputing-fml13v01.dts
diff --git a/arch/riscv/boot/dts/starfive/Makefile b/arch/riscv/boot/dts/starfive/Makefile
index 7a163a7d6ba3..b3bb12f78e7d 100644
--- a/arch/riscv/boot/dts/starfive/Makefile
+++ b/arch/riscv/boot/dts/starfive/Makefile
@@ -8,6 +8,7 @@ DTC_FLAGS_jh7110-starfive-visionfive-2-v1.3b := -@
dtb-$(CONFIG_ARCH_STARFIVE) += jh7100-beaglev-starlight.dtb
dtb-$(CONFIG_ARCH_STARFIVE) += jh7100-starfive-visionfive-v1.dtb
+dtb-$(CONFIG_ARCH_STARFIVE) += jh7110-deepcomputing-fml13v01.dtb
dtb-$(CONFIG_ARCH_STARFIVE) += jh7110-milkv-mars.dtb
dtb-$(CONFIG_ARCH_STARFIVE) += jh7110-pine64-star64.dtb
dtb-$(CONFIG_ARCH_STARFIVE) += jh7110-starfive-visionfive-2-v1.2a.dtb
diff --git a/arch/riscv/boot/dts/starfive/jh7110-deepcomputing-fml13v01.dts b/arch/riscv/boot/dts/starfive/jh7110-deepcomputing-fml13v01.dts
new file mode 100644
index 000000000000..b515b7d04c37
--- /dev/null
+++ b/arch/riscv/boot/dts/starfive/jh7110-deepcomputing-fml13v01.dts
@@ -0,0 +1,44 @@
+// SPDX-License-Identifier: GPL-2.0 OR MIT
+/*
+ * Copyright (C) 2024 DeepComputing (HK) Limited
+ */
+
+/dts-v1/;
+#include "jh7110-common.dtsi"
+
+/ {
+ model = "DeepComputing FML13V01";
+ compatible = "deepcomputing,fml13v01", "starfive,jh7110";
+};
+
+&camss {
+ status = "disabled";
+};
+
+&csi2rx {
+ status = "disabled";
+};
+
+&gmac0 {
+ status = "disabled";
+};
+
+&i2c0 {
+ status = "disabled";
+};
+
+&pwm {
+ status = "disabled";
+};
+
+&pwmdac {
+ status = "disabled";
+};
+
+&spi0 {
+ status = "disabled";
+};
+
+&usb0 {
+ dr_mode = "host";
+};
--
2.34.1
prev parent reply other threads:[~2024-10-19 16:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-19 16:26 [PATCH v4 0/3] Add DeepComputing FML13V01 board dts Guodong Xu
2024-10-19 16:26 ` [PATCH v4 1/3] dt-bindings: vendor: add deepcomputing Guodong Xu
2024-10-20 6:21 ` Greg Kroah-Hartman
2024-10-20 13:26 ` Guodong Xu
2024-10-19 16:26 ` [PATCH v4 2/3] dt-bindings: riscv: starfive: add deepcomputing,fml13v01 Guodong Xu
2024-10-19 16:26 ` Guodong Xu [this message]
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=20241019162605.308475-4-guodong@riscstar.com \
--to=guodong@riscstar.com \
--cc=ams@frame.work \
--cc=aou@eecs.berkeley.edu \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dhs@frame.work \
--cc=drew@beagleboard.org \
--cc=elder@riscstar.com \
--cc=gregkh@linuxfoundation.org \
--cc=heiko.stuebner@cherry.de \
--cc=huiming.qiu@deepcomputing.io \
--cc=kernel@esmil.dk \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@frame.work \
--cc=michael.zhu@starfivetech.com \
--cc=neil.armstrong@linaro.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rafal@milecki.pl \
--cc=robh@kernel.org \
--cc=sandie.cao@deepcomputing.io \
--cc=yuning.liang@deepcomputing.io \
/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