public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: "Sandie Cao" <sandie.cao@deepcomputing.io>
To: "Conor Dooley" <conor+dt@kernel.org>
Cc: "Emil Renner Berthing" <kernel@esmil.dk>,
	 "Rob Herring" <robh@kernel.org>,
	 "Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	 "Yixun Lan" <dlan@kernel.org>,
	 "Paul Walmsley" <paul.walmsley@sifive.com>,
	 "Palmer Dabbelt" <palmer@dabbelt.com>,
	 "Albert Ou" <aou@eecs.berkeley.edu>,
	 "Heinrich Schuchardt" <heinrich.schuchardt@canonical.com>,
	 "Troy Mitchell" <troy.mitchell@linux.spacemit.com>,
	 "Michael Opdenacker" <michael.opdenacker@rootcommit.com>,
	 "Guodong Xu" <guodong@riscstar.com>,
	 "Hendrik Hamerlinck" <hendrik.hamerlinck@hammernet.be>,
	 "Yangyu Chen" <cyy@cyyself.name>, <spacemit@lists.linux.dev>,
	 <linux-riscv@lists.infradead.org>, <devicetree@vger.kernel.org>,
	 <linux-kernel@vger.kernel.org>,
	 "Sandie Cao" <sandie.cao@deepcomputing.io>
Subject: [PATCH v2 0/2] Add DeepComputing FML13V05 board dts
Date: Tue, 31 Mar 2026 15:11:10 +0800	[thread overview]
Message-ID: <20260331071110.68321-1-sandie.cao@deepcomputing.io> (raw)

This series updates Device Tree related files to introduce the
FML13V05 board from DeepComputing, which incorporates a Spacemit
K3 SoC.  This board is designed for use on the Framework Laptop 13
Chassis, which has (Framework) SKU FRANHQ0001.

The series is based on riscv-dt-for-next.

v2:
- Patch 1:
   Use formal format user name.
- Patch 2:
   Use formal format user name.
   Add Reviewed-by from Troy Mitchell.

Link to v1: https://lore.kernel.org/all/20260331034423.67142-1-sandie.cao@deepcomputing.io/

Sandie Cao (2):
  dt-bindings: riscv: spacemit: add deepcomputing,fml13v05
  riscv: dts: spacemit: add DeepComputing FML13V05 board device tree

 .../devicetree/bindings/riscv/spacemit.yaml   |  1 +
 arch/riscv/boot/dts/spacemit/Makefile         |  1 +
 .../spacemit/k3-deepcomputing-fml13v05.dts    | 28 +++++++++++++++++++
 3 files changed, 30 insertions(+)
 create mode 100644 arch/riscv/boot/dts/spacemit/k3-deepcomputing-fml13v05.dts


base-commit: 4a1739c30fc66a59450c1f78923f94607e786882
-- 
2.43.0

             reply	other threads:[~2026-03-31  7:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-31  7:11 Sandie Cao [this message]
2026-03-31  7:12 ` [PATCH v2 1/2] dt-bindings: riscv: spacemit: add deepcomputing,fml13v05 Sandie Cao
2026-03-31  7:13 ` [PATCH v2 2/2] riscv: dts: spacemit: add DeepComputing FML13V05 board device tree Sandie Cao
2026-03-31  7:15 ` [PATCH v2 0/2] Add DeepComputing FML13V05 board dts Troy Mitchell
2026-03-31  7:21   ` 曹珊珊
  -- strict thread matches above, loose matches on Subject: below --
2026-03-31  3:44 [PATCH v1 " Sandie Cao
2026-03-31  7:10 ` [PATCH v2 " Sandie Cao

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=20260331071110.68321-1-sandie.cao@deepcomputing.io \
    --to=sandie.cao@deepcomputing.io \
    --cc=aou@eecs.berkeley.edu \
    --cc=conor+dt@kernel.org \
    --cc=cyy@cyyself.name \
    --cc=devicetree@vger.kernel.org \
    --cc=dlan@kernel.org \
    --cc=guodong@riscstar.com \
    --cc=heinrich.schuchardt@canonical.com \
    --cc=hendrik.hamerlinck@hammernet.be \
    --cc=kernel@esmil.dk \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=michael.opdenacker@rootcommit.com \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --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