From: Sarah Emery <sarah.emery@canonical.com>
To: Troy Mitchell <troy.mitchell@linux.spacemit.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>, Yixun Lan <dlan@kernel.org>,
Guodong Xu <docular.xu@gmail.com>, Yangyu Chen <cyy@cyyself.name>
Cc: 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, 10 Nov 2026 13:46:28 +0100 [thread overview]
Message-ID: <fcd2fc41-5af8-4256-8296-a5435fdf41db@canonical.com> (raw)
In-Reply-To: <20261105-k3-tq-dts-based-on-com260-v1-2-aa0b7714aed0@linux.spacemit.com>
Hi Troy,
On 05/11/2026 09:29, Troy Mitchell wrote:
> + model = "SpacemiT K3 CoM260 IFX TQ";
> + compatible = "spacemit,k3-com260-ifx-tq", "spacemit,k3-com260", "spacemit,k3";
> +
On the CSB1-N10SPK3 server from Firefly, using 10 K3 nodes, reading the
TLV EEPROM of a node gives: "TLV 0x21 (Product Name): k3_com260_tq".
The latest EDK2 from SpacemiT derives the compatible from the TLV EEPROM
name, so EDK2 will report "spacemit, k3-com260-tq" as compatible. This
is by reading the EEPROM that was factory-flashed, so it is not
something easily fixed by a firmware update.
My understanding is that the nodes from CSB1-N10SPK3, the "K3 CoM260 TQ"
and the "K3 CoM260 IFX TQ" are all the same: a "K3 CoM260" module on a
"TQ" or "IFX TQ" carrier board.
Is there two different carrier boards name "TQ" and "IFX TQ"? Or is it
just the same thing, called differently in this patch and in the EEPROM?
I've seen EDK2 referencing both configurations ("TQ" and "IFX TQ").
I'm not sure how devices out there are referencing themselves. But if it
is in fact one device and the EEPROM calls it "k3-com260-tq", this patch
will not work for device-tree matching.
What do you think? Can you clarify the situation?
Many thanks,
Sarah
prev parent reply other threads:[~2026-11-10 12:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 8:29 [PATCH 0/2] " 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 [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=fcd2fc41-5af8-4256-8296-a5435fdf41db@canonical.com \
--to=sarah.emery@canonical.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=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
all inboxes | Powered by JetHome®