From: Yixun Lan <dlan@gentoo.org>
To: Chukun Pan <amadeus@jmu.edu.cn>
Cc: alex@ghiti.fr, aou@eecs.berkeley.edu, conor+dt@kernel.org,
krzk+dt@kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, palmer@dabbelt.com,
pjw@kernel.org, robh@kernel.org, spacemit@lists.linux.dev
Subject: Re: [PATCH 1/2] riscv: dts: spacemit: add common board dtsi for OrangePi
Date: Sat, 24 Jan 2026 08:04:27 +0800 [thread overview]
Message-ID: <20260124000427-GYC71302@gentoo.org> (raw)
In-Reply-To: <20260123140625.1918171-1-amadeus@jmu.edu.cn>
Hi Chukun,
On 22:06 Fri 23 Jan , Chukun Pan wrote:
> Hi,
>
> > no, as I checked these two boards having too many differences that
> > I don't think it's worth trying to create a shared dtsi file
>
> I think some of them can be shared? If you think this is inappropriate,
that's true, but I'd rather we think of this in whole K1 board perspective,
not just two boards of orangepi.
> I will abandon this. By the way, it seems that the OrangePi R2S lacks
> publicly available schematics.
>
> Some parts are the same:
> - emmc
> - eeprom
> - ethernet
> - p1 pmic
> - combo phy
> - pdma / uart0
> - always-on regulator
> - pcie (excluding supply)
> - usb2/3 (excluding supply)
I'm not surprised of this, as most ODM copy the design from vendor.
>
> Some parts are different:
> - hdmi
> - qspi
> - sdcard
> - gpio led
> - sdio wifi
> - audio codec
> - pcie supply
> - usb2/3 supply
> - gpio regulator
>
> Thanks,
> Chukun
--
Yixun Lan (dlan)
prev parent reply other threads:[~2026-01-24 0:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 10:00 [PATCH 1/2] riscv: dts: spacemit: add common board dtsi for OrangePi Chukun Pan
2026-01-16 10:00 ` [PATCH 2/2] riscv: dts: spacemit: add fixed regulators " Chukun Pan
2026-01-19 3:02 ` Yixun Lan
2026-01-23 14:50 ` Chukun Pan
2026-01-23 23:58 ` Yixun Lan
2026-01-19 2:42 ` [PATCH 1/2] riscv: dts: spacemit: add common board dtsi " Yixun Lan
2026-01-23 14:06 ` Chukun Pan
2026-01-24 0:04 ` Yixun Lan [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=20260124000427-GYC71302@gentoo.org \
--to=dlan@gentoo.org \
--cc=alex@ghiti.fr \
--cc=amadeus@jmu.edu.cn \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=robh@kernel.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