From: Yixun Lan <dlan@kernel.org>
To: 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>
Cc: devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
spacemit@lists.linux.dev, linux-kernel@vger.kernel.org,
Yixun Lan <dlan@kernel.org>
Subject: [PATCH 0/2] spacemit: k3: Add support for CoM260-IFX board
Date: Wed, 20 May 2026 05:40:08 +0000 [thread overview]
Message-ID: <20260520-02-k3-com260-ifx-v1-0-3e17055dd488@kernel.org> (raw)
This patch series try to add initial support for SpacemiT K3 CoM260-IFX
board which combines a 69.6 × 45 mm compute module with a reference carrier
board.
The first patch introduce new dt bindings for the module and board, the
second patch enable support for serial console and ethernet.
Link: https://spacemit.com/community/document/info?lang=zh&nodepath=hardware/eco/k3_com260/root_overview.md
Signed-off-by: Yixun Lan <dlan@kernel.org>
---
Yixun Lan (2):
dt-bindings: riscv: spacemit: Add K3 CoM260-IFX board
riscv: dts: spacemit: k3: Initial support for CoM260-IFX board
.../devicetree/bindings/riscv/spacemit.yaml | 5 +
arch/riscv/boot/dts/spacemit/Makefile | 1 +
arch/riscv/boot/dts/spacemit/k3-com260-ifx.dts | 21 +++
arch/riscv/boot/dts/spacemit/k3-com260.dtsi | 190 +++++++++++++++++++++
arch/riscv/boot/dts/spacemit/k3-pinctrl.dtsi | 33 ++++
5 files changed, 250 insertions(+)
---
base-commit: e2518e8cb1dde64af2d1bb246639bb7ef7523f7a
change-id: 20260519-02-k3-com260-ifx-aa320b90e657
Best regards,
--
Yixun Lan <dlan@kernel.org>
next reply other threads:[~2026-05-20 5:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 5:40 Yixun Lan [this message]
2026-05-20 5:40 ` [PATCH 1/2] dt-bindings: riscv: spacemit: Add K3 CoM260-IFX board Yixun Lan
2026-05-20 16:18 ` Conor Dooley
2026-05-20 5:40 ` [PATCH 2/2] riscv: dts: spacemit: k3: Initial support for " Yixun Lan
2026-05-20 5:56 ` sashiko-bot
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=20260520-02-k3-com260-ifx-v1-0-3e17055dd488@kernel.org \
--to=dlan@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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 \
/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