devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Jisheng Zhang <jszhang@kernel.org>
Cc: "Thomas Bonnefille" <thomas.bonnefille@bootlin.com>,
	"Yixun Lan" <dlan@gentoo.org>,
	"Inochi Amaoto" <inochiama@outlook.com>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Paul Walmsley" <paul.walmsley@sifive.com>,
	"Chen Wang" <unicorn_wang@outlook.com>,
	"Chao Wei" <chao.wei@sophgo.com>,
	"Albert Ou" <aou@eecs.berkeley.edu>,
	"Palmer Dabbelt" <palmer@dabbelt.com>,
	"Samuel Holland" <samuel.holland@sifive.com>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Daniel Lezcano" <daniel.lezcano@linaro.org>,
	"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
	"Miquèl Raynal" <miquel.raynal@bootlin.com>,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	linux-riscv@lists.infradead.org
Subject: Re: [PATCH v2 1/6] riscv: dts: sophgo: Put sdhci compatible in dt of specific SoC
Date: Mon, 17 Jun 2024 16:40:48 +0100	[thread overview]
Message-ID: <20240617-exuberant-protegee-f7d414f0976d@spud> (raw)
In-Reply-To: <ZnA3O14HOiV1SBPV@xhacker>

[-- Attachment #1: Type: text/plain, Size: 1865 bytes --]

On Mon, Jun 17, 2024 at 09:16:43PM +0800, Jisheng Zhang wrote:
> On Mon, Jun 17, 2024 at 11:16:32AM +0200, Thomas Bonnefille wrote:
> > On 6/17/24 1:58 AM, Yixun Lan wrote:
> > > On 18:47 Wed 12 Jun     , Inochi Amaoto wrote:

> > > > Is this change necessary? IIRC, the sdhci is the same across
> > > > the whole series.

> sorry for being late, I was busy in the past 2.5 month. Per my
> understanding, the sdhci in cv1800b is the same as the one in
> sg200x. Maybe I'm wrong, but this was my impression when I cooked
> the sdhci driver patch for these SoCs.
> 
> > > I tend to agree with Inochi here, if it's same across all SoC, then no bother to
> > > split, it will cause more trouble to maintain..
> > > 
> > 
> > To be honest, I agree with this to, but as a specific compatible for the
> > SG2002 was created in commit 849e81817b9b, I thought that the best practice
> > was to use it.
> 
> I'd like to take this chance to query DT maintainers: FWICT, in the past
> even if the PLIC is the same between SoCs, adding a new compatible for
> them seems a must. So when time goes on, the compatbile list would be
> longer and longer, is it really necessary? Can we just use the existing
> compatible string?
> DT maintainers may answered the query in the past, if so, sorry for
> querying again.

For new integrations of an IP, yes, new specific compatibles please. New
integrations may have different bugs etc, even if the IP itself is the
same. If there's different SoCs that are the same die, but with elements
fused off, then sure, use the same compatible.

I expect the list of compatibles in the binding to grow rather large, but
that is fine. No one SoC is going to do anything other than something like
compatible = "renesas,$soc-plic", "andestech,corecomplex-plic", "riscv,plic";
which I think is perfectly fine.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2024-06-17 15:40 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-12  8:02 [PATCH v2 0/6] Add board support for Sipeed LicheeRV Nano Thomas Bonnefille
2024-06-12  8:02 ` [PATCH v2 1/6] riscv: dts: sophgo: Put sdhci compatible in dt of specific SoC Thomas Bonnefille
2024-06-12 10:47   ` Inochi Amaoto
2024-06-16 23:58     ` Yixun Lan
2024-06-17  3:36       ` Inochi Amaoto
2024-06-17  9:16       ` Thomas Bonnefille
2024-06-17 13:16         ` Jisheng Zhang
2024-06-17 15:40           ` Conor Dooley [this message]
2024-06-17 15:57             ` Samuel Holland
2024-06-18  4:20               ` Jisheng Zhang
2024-06-18  6:36               ` Inochi Amaoto
2024-06-12  8:02 ` [PATCH v2 2/6] dt-bindings: interrupt-controller: Add SOPHGO SG2002 plic Thomas Bonnefille
2024-06-12 15:30   ` Rob Herring
2024-06-12 16:45     ` Conor Dooley
2024-06-12  8:02 ` [PATCH v2 3/6] dt-bindings: timer: Add SOPHGO SG2002 clint Thomas Bonnefille
2024-06-12 16:46   ` Conor Dooley
2024-06-12  8:02 ` [PATCH v2 4/6] dt-bindings: riscv: Add Sipeed LicheeRV Nano board compatibles Thomas Bonnefille
2024-06-12 16:46   ` Conor Dooley
2024-06-12  8:02 ` [PATCH v2 5/6] riscv: dts: sophgo: Add initial SG2002 SoC device tree Thomas Bonnefille
2024-06-17 16:01   ` Samuel Holland
2024-06-12  8:02 ` [PATCH v2 6/6] riscv: dts: sophgo: Add LicheeRV Nano board " Thomas Bonnefille
2024-06-20  1:00   ` Inochi Amaoto

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=20240617-exuberant-protegee-f7d414f0976d@spud \
    --to=conor@kernel.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=chao.wei@sophgo.com \
    --cc=conor+dt@kernel.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlan@gentoo.org \
    --cc=inochiama@outlook.com \
    --cc=jszhang@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robh@kernel.org \
    --cc=samuel.holland@sifive.com \
    --cc=tglx@linutronix.de \
    --cc=thomas.bonnefille@bootlin.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=unicorn_wang@outlook.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;
as well as URLs for NNTP newsgroup(s).