public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yixun Lan <dlan@gentoo.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Michael Opdenacker <michael.opdenacker@rootcommit.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>, Yangyu Chen <cyy@cyyself.name>,
	devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
	spacemit@lists.linux.dev, linux-kernel@vger.kernel.org,
	Troy Mitchell <troy.mitchell@linux.spacemit.com>
Subject: Re: [PATCH v3 1/2] dt-bindings: riscv: spacemit: Add OrangePi R2S board
Date: Tue, 11 Nov 2025 19:41:33 +0800	[thread overview]
Message-ID: <20251111114133-GYA1677599@gentoo.org> (raw)
In-Reply-To: <2eb5ea0b-d071-4e17-abc8-7db5c78919f2@kernel.org>

Hi All,

On 11:34 Tue 11 Nov     , Krzysztof Kozlowski wrote:
> On 11/11/2025 11:29, Michael Opdenacker wrote:
> > Greetings
> > 
> > Thanks one more time for the reviews!
> > 
> > On 11/11/25 11:13, Krzysztof Kozlowski wrote:
> >> On 11/11/2025 11:11, Yixun Lan wrote:
> >>> Hi Krzysztof,
> >>>
> >>> On 08:43 Tue 11 Nov     , Krzysztof Kozlowski wrote:
> >>>> On Mon, Nov 10, 2025 at 10:06:48PM +0000, michael.opdenacker@rootcommit.com wrote:
> >>>>> From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
> >>>>>
> >>>>> Document the compatible string for the OrangePi R2S board [1], which
> >>>>> is marketed as using the Ky X1 SoC but is in fact identical to
> >>> Maybe, just say it "same" to clarify the ambiguity?
> >> What is exactly "same"? Same die? Or same blocks/pieces? Whichever you
> >> choose please make it very explicit.
> > 
> > Maybe Troy Mitchell from Spacemit can shed light on this question.
> > 
> > Anyway, I could use the same wording as in this commit introducing 
> > "OrangePi RV2":
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch?id=bab8dea259100a99e047fd11a48940b229d30031
> > 
> > "The board is described as using the Ky X1 SoC, which, based on 
> > available downstream sources and testing, appears to be identical or 
> > very closely related to the SpacemiT K1 SoC".
sorry for bringing confusion in previous series, we had no further discussion on this..

> > 
> > What do you think?
> 
> This clearly suggests they are not identical thus you should have also
> dedicated compatible. Let me then precise, I thought it is obvious, that
> except writing it more detailed in commit msg, you also need proper
> binding expressing this. If this is not the same die and they look
> compatible, then usually it means you need a compatible.
> 

to be explicit, the Xy X1 has same die, same packaging as SpacemiT K1,
so we should not introduce new compatible in the SoC level, but a new
board compatible in patch [1/2] is ok to me

I hope this clarify this issue..

-- 
Yixun Lan (dlan)

  parent reply	other threads:[~2025-11-11 11:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251110220641.1751392-1-michael.opdenacker@rootcommit.com>
2025-11-10 22:06 ` [PATCH v3 1/2] dt-bindings: riscv: spacemit: Add OrangePi R2S board michael.opdenacker
2025-11-11  7:43   ` Krzysztof Kozlowski
2025-11-11 10:11     ` Yixun Lan
2025-11-11 10:13       ` Krzysztof Kozlowski
2025-11-11 10:29         ` Michael Opdenacker
2025-11-11 10:34           ` Krzysztof Kozlowski
2025-11-11 11:37             ` Michael Opdenacker
2025-11-11 11:41             ` Yixun Lan [this message]
2025-11-10 22:06 ` [PATCH v3 2/2] riscv: dts: spacemit: Add OrangePi R2S board device tree michael.opdenacker

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=20251111114133-GYA1677599@gentoo.org \
    --to=dlan@gentoo.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=conor+dt@kernel.org \
    --cc=cyy@cyyself.name \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=michael.opdenacker@rootcommit.com \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=robh@kernel.org \
    --cc=spacemit@lists.linux.dev \
    --cc=troy.mitchell@linux.spacemit.com \
    /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