[PATCH 0/2] riscv: dts: spacemit: Add K3 CoM260 IFX TQ support

[PATCH 0/2] riscv: dts: spacemit: Add K3 CoM260 IFX TQ support

[Troy Mitchell]

This series adds device tree support for the K3 CoM260 IFX TQ board,
which combines the K3 CoM260 module with the IFX TQ carrier.

The board reuses the CoM260 module description for the UART console,
Ethernet, module EEPROM and PMIC, and describes the carrier's Ethernet
PHY LEDs. Unlike the IFX carrier, the IFX TQ carrier has no additional
EEPROM.

Signed-off-by: Troy Mitchell <troy.mitchell@linux.spacemit.com>
---
Troy Mitchell (2):
      dt-bindings: riscv: spacemit: Add K3 CoM260 IFX TQ
      riscv: dts: spacemit: Add K3 CoM260 IFX TQ support

 .../devicetree/bindings/riscv/spacemit.yaml        |  1 +
 arch/riscv/boot/dts/spacemit/Makefile              |  1 +
 arch/riscv/boot/dts/spacemit/k3-com260-ifx-tq.dts  | 44 ++++++++++++++++++++++
 3 files changed, 46 insertions(+)
---
base-commit: 6628e7d4c6b25c8d18f1345e3a20d21829aae7e4
change-id: 20261015-k3-tq-dts-based-on-com260-37d5d99a2b9b

Best regards,
--  
Troy Mitchell <troy.mitchell@linux.spacemit.com>

[PATCH 1/2] dt-bindings: riscv: spacemit: Add K3 CoM260 IFX TQ

[Troy Mitchell]

The K3 CoM260 IFX TQ board combines a CoM260 module with an IFX TQ
carrier. Add its board compatible with the CoM260 module and K3 SoC
fallbacks.

Signed-off-by: Troy Mitchell <troy.mitchell@linux.spacemit.com>
---
 Documentation/devicetree/bindings/riscv/spacemit.yaml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Documentation/devicetree/bindings/riscv/spacemit.yaml b/Documentation/devicetree/bindings/riscv/spacemit.yaml
index 4ee9c88984b4..9b115b4e4b9b 100644
--- a/Documentation/devicetree/bindings/riscv/spacemit.yaml
+++ b/Documentation/devicetree/bindings/riscv/spacemit.yaml
@@ -40,6 +40,7 @@ properties:
       - items:
           - enum:
               - spacemit,k3-com260-ifx
+              - spacemit,k3-com260-ifx-tq
           - const: spacemit,k3-com260
           - const: spacemit,k3
 

-- 
2.56.0

[PATCH 2/2] riscv: dts: spacemit: Add K3 CoM260 IFX TQ support

[Troy Mitchell]

Add a device tree for the K3 CoM260 IFX TQ board. It reuses the CoM260
module description for the UART console, Ethernet, module EEPROM and
PMIC.

Describe the carrier's green and yellow Ethernet PHY LEDs while keeping
their existing hardware state. Enable ALDPS power saving on the
RTL8211F PHY and disable its unused CLKOUT output.

Signed-off-by: Troy Mitchell <troy.mitchell@linux.spacemit.com>
---
 arch/riscv/boot/dts/spacemit/Makefile             |  1 +
 arch/riscv/boot/dts/spacemit/k3-com260-ifx-tq.dts | 44 +++++++++++++++++++++++
 2 files changed, 45 insertions(+)

diff --git a/arch/riscv/boot/dts/spacemit/Makefile b/arch/riscv/boot/dts/spacemit/Makefile
index 851b701e5da4..fe664f84e1dd 100644
--- a/arch/riscv/boot/dts/spacemit/Makefile
+++ b/arch/riscv/boot/dts/spacemit/Makefile
@@ -6,5 +6,6 @@ dtb-$(CONFIG_ARCH_SPACEMIT) += k1-musepi-pro.dtb
 dtb-$(CONFIG_ARCH_SPACEMIT) += k1-orangepi-r2s.dtb
 dtb-$(CONFIG_ARCH_SPACEMIT) += k1-orangepi-rv2.dtb
 dtb-$(CONFIG_ARCH_SPACEMIT) += k3-com260-ifx.dtb
+dtb-$(CONFIG_ARCH_SPACEMIT) += k3-com260-ifx-tq.dtb
 dtb-$(CONFIG_ARCH_SPACEMIT) += k3-deepcomputing-fml13v05.dtb
 dtb-$(CONFIG_ARCH_SPACEMIT) += k3-pico-itx.dtb
diff --git a/arch/riscv/boot/dts/spacemit/k3-com260-ifx-tq.dts b/arch/riscv/boot/dts/spacemit/k3-com260-ifx-tq.dts
new file mode 100644
index 000000000000..6d9b2dbd825d
--- /dev/null
+++ b/arch/riscv/boot/dts/spacemit/k3-com260-ifx-tq.dts
@@ -0,0 +1,44 @@
+// SPDX-License-Identifier: (GPL-2.0 OR MIT)
+/* Copyright (c) 2026 SpacemiT (Hangzhou) Technology Co. Ltd */
+
+#include <dt-bindings/leds/common.h>
+
+#include "k3-com260.dtsi"
+
+/ {
+	model = "SpacemiT K3 CoM260 IFX TQ";
+	compatible = "spacemit,k3-com260-ifx-tq", "spacemit,k3-com260", "spacemit,k3";
+
+	aliases {
+		serial0 = &uart0;
+		ethernet0 = &eth1;
+	};
+
+	chosen {
+		stdout-path = "serial0:115200n8";
+	};
+};
+
+&phy1 {
+	realtek,aldps-enable;
+	realtek,clkout-disable;
+
+	leds {
+		#address-cells = <1>;
+		#size-cells = <0>;
+
+		led@1 {
+			reg = <1>;
+			function = LED_FUNCTION_LAN;
+			color = <LED_COLOR_ID_GREEN>;
+			default-state = "keep";
+		};
+
+		led@2 {
+			reg = <2>;
+			function = LED_FUNCTION_LAN;
+			color = <LED_COLOR_ID_YELLOW>;
+			default-state = "keep";
+		};
+	};
+};

-- 
2.56.0

Re: [PATCH 2/2] riscv: dts: spacemit: Add K3 CoM260 IFX TQ support

[Sarah Emery]

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

Re: [PATCH 2/2] riscv: dts: spacemit: Add K3 CoM260 IFX TQ support

[Troy Mitchell]

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

On Tue, Nov 10, 2026 at 01:46:28PM +0100, Sarah Emery wrote:
> 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?

They are the same carrier board. The only difference is the power scheme
of the CPU clusters. The bootloader programs those regulators at boot,
and upstream Linux currently keeps the voltages it leaves. Support for
the regulators is not upstream yet, so the two boards cannot be told
apart in the device tree for now.

> 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?

You are right, thanks for pointing this out. I only had an IFX TQ board
when I sent the series, so I did not notice that the TQ nodes identify
themselves as k3_com260_tq in the EEPROM.

I will restructure the series as k3-com260-tq.dtsi holding the shared
carrier description, with k3-com260-tq.dts and k3-com260-ifx-tq.dts on
top of it that only set model and compatible. I will add
k3-com260-tq-power.dtsi and k3-com260-ifx-tq-power.dtsi for the two
power schemes later.

Yixun, what do you think?

-- 
Troy Mitchell

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

Re: [PATCH 2/2] riscv: dts: spacemit: Add K3 CoM260 IFX TQ support

[Yixun Lan]

Hi Troy,

On 08:39 Fri 13 Nov     , Troy Mitchell wrote:
> On Tue, Nov 10, 2026 at 01:46:28PM +0100, Sarah Emery wrote:
> > 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?
> 
> 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?

> and upstream Linux currently keeps the voltages it leaves. Support for
> the regulators is not upstream yet, so the two boards cannot be told
> apart in the device tree for now.
> 
> > 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?
> 
> You are right, thanks for pointing this out. I only had an IFX TQ board
> when I sent the series, so I did not notice that the TQ nodes identify
> themselves as k3_com260_tq in the EEPROM.
> 
> I will restructure the series as k3-com260-tq.dtsi holding the shared
> carrier description, with k3-com260-tq.dts and k3-com260-ifx-tq.dts on
> top of it that only set model and compatible. I will add
> k3-com260-tq-power.dtsi and k3-com260-ifx-tq-power.dtsi for the two
> power schemes later.
> 
> Yixun, what do you think?
> 
Please send out a version for review, I'd be generally fine within introducing
two dts files, but be careful about new model and compatible string..

-- 
Yixun Lan (dlan)