From: Aurelien Jarno <aurelien@aurel32.net>
To: linux-kernel@vger.kernel.org, Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>, Yixun Lan <dlan@kernel.org>
Cc: Aurelien Jarno <aurelien@aurel32.net>,
linux-riscv@lists.infradead.org (open list:RISC-V
ARCHITECTURE:Keyword:riscv),
spacemit@lists.linux.dev (open list:RISC-V SPACEMIT SoC
Support:Keyword:spacemit)
Subject: [PATCH v5 0/5] Enable Bluetooth and WiFi on K3 Pico ITX
Date: Mon, 28 Sep 2026 22:49:05 +0200 [thread overview]
Message-ID: <20260928205012.3689405-1-aurelien@aurel32.net> (raw)
This patchset enables Bluetooth through USB on the K3 Pico ITX board and
adds the rfkill nodes for Bluetooth and WLAN so that the devices can be
activated.
Note that WLAN support (patch 4) is only useful with the following
patchset, but they can be applied independently:
- https://lore.kernel.org/spacemit/20260923015016.64069-1-inochiama@gmail.com/T/#t
Changes v4 (unfortunately wrongly submitted as v3) -> v5
- rebase onto spacemit/dt-for-next
- explain in patch1 why the change does not impact the DT schema
validation (reported by Sashiko)
Changes v3 -> v4
- fully move the phy definition and the board level
- rebase onto 7.3-rc1
Changes v2 -> v3
- reorder patches in a more logical order
- rebase on current linus/master
- add patch 1 to move phy definition to the board level for the "usb3d"
controller
- remove link to USB3 phys, they can't be added if the combo phy is not
configured accordingly - also enable Bluetooth and WLAN drivers in
defconfig
Changes v1 -> v2
- Rebase on current spacemit/dt-for-next branch
- Collect Tested-by tag
- Add link to USB3 PHYs in DT now that K3 PHY support is merged
Aurelien Jarno (5):
riscv: dts: spacemit: k3: move USB3 phy to board level
riscv: dts: spacemit: k3: add USB3 B and C controllers for Pico-ITX
board
riscv: dts: spacemit: k3: add rfkill node for Bluetooth on Pico-ITX
board
riscv: dts: spacemit: k3: add rfkill node for WLAN on the K3 Pico-ITX
board
riscv64: defconfig: Enable BT and WLAN support for SpacemiT K3
Pico-ITX board
arch/riscv/boot/dts/spacemit/k3-pico-itx.dts | 38 ++++++++++++
arch/riscv/boot/dts/spacemit/k3.dtsi | 63 +++++++++++++++++++-
arch/riscv/configs/defconfig | 8 +++
3 files changed, 106 insertions(+), 3 deletions(-)
--
2.53.0
next reply other threads:[~2026-09-28 20:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 20:49 Aurelien Jarno [this message]
2026-09-28 20:49 ` [PATCH v5 1/5] riscv: dts: spacemit: k3: move USB3 phy to board level Aurelien Jarno
2026-09-28 20:49 ` [PATCH v5 2/5] riscv: dts: spacemit: k3: add USB3 B and C controllers for Pico-ITX board Aurelien Jarno
[not found] ` <20260928210216.7DCB41F000FF@smtp.kernel.org>
2026-09-28 21:10 ` Aurelien Jarno
2026-09-28 20:49 ` [PATCH v5 3/5] riscv: dts: spacemit: k3: add rfkill node for Bluetooth on " Aurelien Jarno
2026-09-28 20:49 ` [PATCH v5 4/5] riscv: dts: spacemit: k3: add rfkill node for WLAN on the K3 " Aurelien Jarno
2026-09-28 20:49 ` [PATCH v5 5/5] riscv64: defconfig: Enable BT and WLAN support for SpacemiT " Aurelien Jarno
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=20260928205012.3689405-1-aurelien@aurel32.net \
--to=aurelien@aurel32.net \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=dlan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@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
all inboxes | Powered by JetHome®