Re: [PATCH 2/2] riscv: dts: spacemit: Add K3 CoM260 IFX TQ support
From: Sarah Emery
Date: Tue Nov 10 2026 - 07:47:02 EST
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