From: Yixun Lan <dlan@gentoo.org>
To: Vivian Wang <wangruikang@iscas.ac.cn>
Cc: Hendrik Hamerlinck <hendrik.hamerlinck@hammernet.be>,
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 v2 2/2] riscv: dts: spacemit: Add OrangePi RV2 board device tree
Date: Fri, 18 Jul 2025 18:07:32 +0800 [thread overview]
Message-ID: <20250718100732-GYA700698@gentoo> (raw)
In-Reply-To: <8ade99a6-84a0-4e69-8ebf-d9dfdc9141b5@iscas.ac.cn>
Hi Vivian,
On 17:10 Fri 18 Jul , Vivian Wang wrote:
> Hi Hendrik,
>
> On 7/18/25 16:43, 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 isn't particularly crucial, but I wonder if we can do something
> similar to a jh7110-common.dtsi arrangement, where most of the boards
> sharing similar designs can also share devicetree source files.
>
> Easier said than done, probably, but I think it should be possible by
> just comparing the vendor dts files.
>
> Again this doesn't need to block this patch.
>
Sure
> Yixun: I'm assuming you'll be handling this. What do you think about a
> k1-common.dtsi?
>
Sharing dtsi file for similar boards is generally fine, I saw a few
other SoC maintainers have done the same..
In the practical cases, we have to evaluate and plan carefully, it
should be manageable to support fixed number of boards for one file,
but would be nasty if expect one common dts file to cover all boards..
Anyhow, I think we can revisit this idea and having incremental patch
later, it's not the problem for now
Thanks for the suggestion
--
Yixun Lan (dlan)
next prev parent reply other threads:[~2025-07-18 10:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 8:43 [PATCH v2 0/2] riscv: dts: spacemit: Add initial support for OrangePi RV2 Hendrik Hamerlinck
2025-07-18 8:43 ` [PATCH v2 1/2] dt-bindings: riscv: spacemit: Add OrangePi RV2 board Hendrik Hamerlinck
2025-07-18 8:43 ` [PATCH v2 2/2] riscv: dts: spacemit: Add OrangePi RV2 board device tree Hendrik Hamerlinck
2025-07-18 9:10 ` Vivian Wang
2025-07-18 10:07 ` Yixun Lan [this message]
2025-07-18 8:57 ` [PATCH v2 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=20250718100732-GYA700698@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 \
--cc=wangruikang@iscas.ac.cn \
/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