From: Yixun Lan <dlan@gentoo.org>
To: Hendrik Hamerlinck <hendrik.hamerlinck@hammernet.be>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
paul.walmsley@sifive.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
palmer@dabbelt.com, skhan@linuxfoundation.org,
linux-kernel-mentees@lists.linux.dev, devicetree@vger.kernel.org,
linux-riscv@lists.infradead.org, spacemit@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] riscv: dts: spacemit: Add OrangePi RV2 board device tree
Date: Tue, 15 Jul 2025 18:25:34 +0800 [thread overview]
Message-ID: <20250715102534-GYA542593@gentoo> (raw)
In-Reply-To: <20250711183245.256683-3-hendrik.hamerlinck@hammernet.be>
On 20:32 Fri 11 Jul , Hendrik Hamerlinck wrote:
> Add initial device tree support for the OrangePi RV2 board [1], which is
> marketed as using the Ky X1 SoC but has been confirmed to be
> identical to the SpacemiT K1 [2].
>
> The device tree is adapted from the OrangePi vendor tree [3], and similar
> integration can be found in the Banana Pi kernel tree [4], confirming SoC
> compatibility.
>
> This minimal device tree enables booting into a serial console with UART
> output and a blinking LED.
>
> Link: http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/Orange-Pi-RV2.html [1]
> Link: https://www.spacemit.com/en/key-stone-k1 [2]
> Link: https://github.com/BPI-SINOVOIP/pi-linux/blob/linux-6.6.63-k1/arch/riscv/boot/dts/spacemit/k1-x_orangepi-rv2.dts [3]
> Link: https://github.com/orangepi-xunlong/linux-orangepi/tree/orange-pi-6.6-ky [4]
> Signed-off-by: Hendrik Hamerlinck <hendrik.hamerlinck@hammernet.be>
> ---
> arch/riscv/boot/dts/spacemit/Makefile | 1 +
> .../boot/dts/spacemit/k1-orangepi-rv2.dts | 43 +++++++++++++++++++
> 2 files changed, 44 insertions(+)
> create mode 100644 arch/riscv/boot/dts/spacemit/k1-orangepi-rv2.dts
>
> diff --git a/arch/riscv/boot/dts/spacemit/Makefile b/arch/riscv/boot/dts/spacemit/Makefile
> index 92e13ce1c16d..152832644870 100644
> --- a/arch/riscv/boot/dts/spacemit/Makefile
> +++ b/arch/riscv/boot/dts/spacemit/Makefile
> @@ -1,3 +1,4 @@
> # SPDX-License-Identifier: GPL-2.0
> dtb-$(CONFIG_ARCH_SPACEMIT) += k1-bananapi-f3.dtb
> dtb-$(CONFIG_ARCH_SPACEMIT) += k1-milkv-jupiter.dtb
> +dtb-$(CONFIG_ARCH_SPACEMIT) += k1-orangepi-rv2.dtb
> diff --git a/arch/riscv/boot/dts/spacemit/k1-orangepi-rv2.dts b/arch/riscv/boot/dts/spacemit/k1-orangepi-rv2.dts
> new file mode 100644
> index 000000000000..8313f9589cd2
> --- /dev/null
> +++ b/arch/riscv/boot/dts/spacemit/k1-orangepi-rv2.dts
> @@ -0,0 +1,43 @@
> +// SPDX-License-Identifier: (GPL-2.0 OR MIT)
..
> +/* Copyright (c) 2023 Ky, Inc */
Copyright should cover current year, which is 2025..
what's "Ky" stand for? Can you give a full description here
> +
> +/dts-v1/;
> +
> +#include "k1.dtsi"
> +#include "k1-pinctrl.dtsi"
> +
> +/ {
> + model = "OrangePi RV2";
> + compatible = "xunlong,orangepi-rv2", "spacemit,k1";
> +
..
> + memory@0 {
> + device_type = "memory";
> + reg = <0x0 0x00000000 0x0 0x80000000>;
> + };
> +
> + memory@100000000 {
> + device_type = "memory";
> + reg = <0x1 0x00000000 0x0 0x80000000>;
> + };
> +
for the memory nodes, there are 2/4/8GB variants from the Link [1], and
you couldn't cover all of them in one dt
besides, I thought bootloader (u-boot) will populate these info, right?
so the above nodes isn't really necessary
> + chosen {
> + stdout-path = "serial0";
> + };
> +
> + leds {
> + compatible = "gpio-leds";
> +
> + led1 {
> + label = "sys-led";
> + gpios = <&gpio K1_GPIO(96) GPIO_ACTIVE_LOW>;
> + linux,default-trigger = "heartbeat";
> + default-state = "on";
> + };
> + };
> +};
> +
> +&uart0 {
> + pinctrl-names = "default";
> + pinctrl-0 = <&uart0_2_cfg>;
> + status = "okay";
> +};
> --
> 2.43.0
>
--
Yixun Lan (dlan)
next prev parent reply other threads:[~2025-07-15 10:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 18:32 [PATCH 0/2] riscv: dts: spacemit: Add initial support for OrangePi RV2 Hendrik Hamerlinck
2025-07-11 18:32 ` [PATCH 1/2] dt-bindings: riscv: spacemit: Add OrangePi RV2 board Hendrik Hamerlinck
2025-07-15 3:25 ` Rob Herring (Arm)
2025-07-11 18:32 ` [PATCH 2/2] riscv: dts: spacemit: Add OrangePi RV2 board device tree Hendrik Hamerlinck
2025-07-15 10:25 ` Yixun Lan [this message]
2025-07-16 9:37 ` Hendrik Hammernet
2025-07-16 11:33 ` Yixun Lan
2025-07-15 10:30 ` [PATCH 0/2] riscv: dts: spacemit: Add initial support for OrangePi RV2 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=20250715102534-GYA542593@gentoo \
--to=dlan@gentoo.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hendrik.hamerlinck@hammernet.be \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=skhan@linuxfoundation.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