Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Troy Mitchell" <troy.mitchell@linux.spacemit.com>
To: "Yixun Lan" <dlan@kernel.org>
Cc: "Troy Mitchell" <troy.mitchell@linux.spacemit.com>,
	"Sarah Emery" <sarah.emery@canonical.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>,
	"Guodong Xu" <docular.xu@gmail.com>,
	"Yangyu Chen" <cyy@cyyself.name>, <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 K3 CoM260 IFX TQ support
Date: Tue, 17 Nov 2026 06:46:04 +0000	[thread overview]
Message-ID: <DMXA85POOYLH.3L9L2Q53OUJ1T@linux.spacemit.com> (raw)
In-Reply-To: <20261114082802-GKC100523@kernel.org>


[-- Attachment #1.1: Type: text/plain, Size: 835 bytes --]

On Sat, Nov 14, 2026 at 08:28:02AM +0000, Yixun Lan wrote:
> On 08:39 Fri 13 Nov     , Troy Mitchell wrote:
> > They are the same carrier board. The only difference is the power scheme
> > of the CPU clusters. The bootloader programs those regulators at boot,
>
> If they are physically same carrier board with same CoM260 module, but only
> the power setup configuration is different? then no reason to introduce two
> different compatible strings, if still need to differentiant, please find
> other way out?

Agreed. v2 will only add spacemit,k3-com260-tq and k3-com260-tq.dts.

Once the regulators are supported, I plan to describe each power scheme
as an overlay and build the other variant as a composite DTB, i.e.
k3-com260-tq.dtb plus its power overlay, so it keeps the same
compatible.


-- 
Troy Mitchell

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

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

      reply	other threads:[~2026-11-17  6:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-05  8:29 [PATCH 0/2] riscv: dts: spacemit: Add K3 CoM260 IFX TQ support Troy Mitchell
2026-11-05  8:29 ` [PATCH 1/2] dt-bindings: riscv: spacemit: Add K3 CoM260 IFX TQ Troy Mitchell
2026-11-05  8:29 ` [PATCH 2/2] riscv: dts: spacemit: Add K3 CoM260 IFX TQ support Troy Mitchell
2026-11-10 12:46   ` Sarah Emery
2026-11-13  8:39     ` Troy Mitchell
2026-11-14  8:28       ` Yixun Lan
2026-11-17  6:46         ` Troy Mitchell [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=DMXA85POOYLH.3L9L2Q53OUJ1T@linux.spacemit.com \
    --to=troy.mitchell@linux.spacemit.com \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=conor+dt@kernel.org \
    --cc=cyy@cyyself.name \
    --cc=devicetree@vger.kernel.org \
    --cc=dlan@kernel.org \
    --cc=docular.xu@gmail.com \
    --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=sarah.emery@canonical.com \
    --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