From: "Sandie Cao" <sandie.cao@deepcomputing.io>
To: "Yixun Lan" <dlan@kernel.org>,
"Troy Mitchell" <troy.mitchell@linux.spacemit.com>,
"Conor Dooley" <conor+dt@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Paul Walmsley" <pjw@kernel.org>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>
Cc: "Alexandre Ghiti" <alex@ghiti.fr>, <devicetree@vger.kernel.org>,
<linux-riscv@lists.infradead.org>, <spacemit@lists.linux.dev>,
<linux-kernel@vger.kernel.org>,
"Sandie Cao" <sandie.cao@deepcomputing.io>
Subject: [PATCH 0/5] riscv: dts: spacemit: enable WLAN and Bluetooth on DeepComputing FML13V05
Date: Mon, 16 Nov 2026 16:57:25 +0800 [thread overview]
Message-ID: <20261116085725.951253-1-sandie.cao@deepcomputing.io> (raw)
This series updates the DeepComputing FML13V05 device tree to describes
the console UART as 115200n8, add rfkill nodes for WLAN and Bluetooth,
model the 3.3V supply of the WLAN module, and enable PCIe node.
The series is based on next-20261113. The DeepComputing FML13V05
device tree depends on [1]. The PCIe driver depends on[2], which
in turn depends on [3] and [4]. The PCIe node depends on [5].
[1] https://lore.kernel.org/all/20261109033154.361399-1-sandie.cao
@deepcomputing.io/
[2] https://lore.kernel.org/all/20260929083755.458238-1-inochiama
@gmail.com/
[3] https://github.com/spacemit-com/linux-6.18/commits/k3-br-v1.0.y/
drivers/pci/controller/dwc/pcie-spacemit-k1.c
[4] https://lore.kernel.org/linux-phy/20260904083709.425893-1-inochiama
@gmail.com/
[5] https://lore.kernel.org/spacemit/20260727094726.890179-3-inochiama
@gmail.com/
---
Sandie Cao (5):
riscv: dts: spacemit: k3-deepcomputing-fml13v05: add 115200n8 to
stdout-path
riscv: dts: spacemit: k3-deepcomputing-fml13v05: add rfkill node for
WLAN
riscv: dts: spacemit: k3-deepcomputing-fml13v05: add rfkill node for
Bluetooth
riscv: dts: spacemit: k3-deepcomputing-fml13v05: add WLAN power
regulator
riscv: dts: spacemit: k3-deepcomputing-fml13v05: enable PCIe
.../spacemit/k3-deepcomputing-fml13v05.dts | 60 ++++++++++++++++++-
1 file changed, 59 insertions(+), 1 deletion(-)
base-commit: 4bc415760dd40fcff23deb073333984dd15d418d
--
2.43.0
next reply other threads:[~2026-11-16 8:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 8:57 Sandie Cao [this message]
2026-11-16 8:58 ` [PATCH 1/5] riscv: dts: spacemit: k3-deepcomputing-fml13v05: add 115200n8 to stdout-path Sandie Cao
2026-11-16 8:59 ` [PATCH 2/5] riscv: dts: spacemit: k3-deepcomputing-fml13v05: add rfkill node for WLAN Sandie Cao
2026-11-16 8:59 ` [PATCH 3/5] riscv: dts: spacemit: k3-deepcomputing-fml13v05: add rfkill node for Bluetooth Sandie Cao
2026-11-16 8:59 ` [PATCH 4/5] riscv: dts: spacemit: k3-deepcomputing-fml13v05: add WLAN power regulator Sandie Cao
2026-11-16 9:00 ` [PATCH 5/5] riscv: dts: spacemit: k3-deepcomputing-fml13v05: enable PCIe 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=20261116085725.951253-1-sandie.cao@deepcomputing.io \
--to=sandie.cao@deepcomputing.io \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@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 \
--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
all inboxes | Powered by JetHome®