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

From: Troy Mitchell

Date: Tue Nov 17 2026 - 03:49:23 EST


This series adds device tree support for the K3 CoM260 TQ board, a
K3 CoM260 module on the TQ carrier board.

The board uses the CoM260 module description for the UART console,
Ethernet, module EEPROM and PMIC, and describes the carrier's Ethernet
PHY LEDs.

The TQ carrier board comes with one of two power schemes for the CPU
clusters. Both are the same hardware otherwise, and the system currently
relies on the bootloader to set up the power scheme, so a single
compatible and device tree cover both variants. Once the regulators are
supported, the power schemes can be described as overlays applied to
this device tree at build time.

---
Changes in v2:
- Rename the board to K3 CoM260 TQ, which covers both the TQ and the
IFX TQ power schemes.
- Use a single compatible for both power schemes of the TQ carrier.
- Link to v1: https://patch.msgid.link/20261105-k3-tq-dts-based-on-com260-v1-0-aa0b7714aed0@xxxxxxxxxxxxxxxxxx

To: Rob Herring <robh@xxxxxxxxxx>
To: Krzysztof Kozlowski <krzk+dt@xxxxxxxxxx>
To: Conor Dooley <conor+dt@xxxxxxxxxx>
To: Paul Walmsley <pjw@xxxxxxxxxx>
To: Palmer Dabbelt <palmer@xxxxxxxxxxx>
To: Albert Ou <aou@xxxxxxxxxxxxxxxxx>
To: Alexandre Ghiti <alex@xxxxxxxx>
To: Yixun Lan <dlan@xxxxxxxxxx>
To: Troy Mitchell <troy.mitchell@xxxxxxxxxxxxxxxxxx>
To: Guodong Xu <docular.xu@xxxxxxxxx>
To: Yangyu Chen <cyy@xxxxxxxxxxxx>
Cc: devicetree@xxxxxxxxxxxxxxx
Cc: linux-riscv@xxxxxxxxxxxxxxxxxxx
Cc: spacemit@xxxxxxxxxxxxxxx
Cc: linux-kernel@xxxxxxxxxxxxxxx

---
Troy Mitchell (2):
dt-bindings: riscv: spacemit: Add K3 CoM260 TQ
riscv: dts: spacemit: Add K3 CoM260 TQ support

.../devicetree/bindings/riscv/spacemit.yaml | 1 +
arch/riscv/boot/dts/spacemit/Makefile | 1 +
arch/riscv/boot/dts/spacemit/k3-com260-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@xxxxxxxxxxxxxxxxxx>