From: Yixun Lan <dlan@kernel.org>
To: u-boot@lists.u-boot-project.org
Cc: Yao Zi <me@ziyao.cc>, Tim Ouyang <tim609@andestech.com>,
Leo Liang <leo.liang@sifive.com>, Tom Rini <trini@konsulko.com>,
Michal Simek <michal.simek@amd.com>,
Raymond Mao <raymond.mao@riscstar.com>,
Hiago De Franco <hfranco@baylibre.com>,
Junhui Liu <junhui.liu@pigmoral.tech>,
Yixun Lan <dlan@kernel.org>
Subject: [PATCH v3 0/4] riscv: spacemit: Add support for K3 Pico-ITX board
Date: Sat, 03 Oct 2026 00:34:38 +0000 [thread overview]
Message-ID: <20261003-00-basic-spacemit-k3-v3-0-dea68cd1bd7d@kernel.org> (raw)
Add initial support for SpacemiT K3 Pico-ITX board, the config file
will enable all basic components which make it able to run into U-Boot
serial console.
The series actually depend on previous sent patches, I'm not adding
dependency to this series, but list it here for reference.
Pinctrl:
https://patch.msgid.link/20260923-01-k3-pinctrl-support-v2-0-e76a917ee252@kernel.org
GPIO:
https://patch.msgid.link/20260822-01-gpio-pinctrl-support-v1-1-6be2f4c71c5d@kernel.org
clock and reset:
https://patch.msgid.link/20260923-01-k3-clock-reset-support-v2-0-6ec0abb1c7b5@kernel.org
Signed-off-by: Yixun Lan <dlan@kernel.org>
---
Changes in v3:
- rename header and dtsi file with vendor prefix
- Link to v2: https://patch.msgid.link/20261002-00-basic-spacemit-k3-v2-0-fd6779a0317c@kernel.org
Changes in v2:
- drop board_get_usable_ram_top()
- drop empty source file
- Link to v1: https://patch.msgid.link/20260923-00-basic-spacemit-k3-v1-0-fa1015f2cd1b@kernel.org
---
Yixun Lan (4):
board: spacemit: add SpacemiT K3 Pico-ITX
riscv: dts: spacemit: k3: add binman node
configs: spacemit: Add K3 default configuration
doc: spacemit: k3: Add Pico-ITX board
arch/riscv/Kconfig | 5 +
arch/riscv/cpu/k3/Kconfig | 18 +++
arch/riscv/cpu/k3/Makefile | 5 +
arch/riscv/cpu/k3/dram.c | 21 ++++
arch/riscv/dts/spacemit-k3-u-boot.dtsi | 6 +
board/spacemit/k3/Kconfig | 30 +++++
board/spacemit/k3/MAINTAINERS | 8 ++
configs/spacemit_k3_defconfig | 51 ++++++++
doc/board/spacemit/index.rst | 1 +
doc/board/spacemit/spacemit-pico-itx.rst | 204 +++++++++++++++++++++++++++++++
include/configs/spacemit-k3.h | 13 ++
11 files changed, 362 insertions(+)
---
base-commit: cf615aafae36fc49f55e3e6a3648d29201b26d51
change-id: 20260921-00-basic-spacemit-k3-838119645d39
Best regards,
--
Yixun Lan <dlan@kernel.org>
next reply other threads:[~2026-10-03 0:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-03 0:34 Yixun Lan [this message]
2026-10-03 0:34 ` [PATCH v3 1/4] board: spacemit: add SpacemiT K3 Pico-ITX Yixun Lan
2026-10-03 10:02 ` E Shattow
2026-10-03 11:08 ` Yixun Lan
2026-10-03 11:18 ` E Shattow
2026-10-03 0:34 ` [PATCH v3 2/4] riscv: dts: spacemit: k3: add binman node Yixun Lan
2026-10-03 7:49 ` E Shattow
2026-10-03 10:14 ` Yixun Lan
2026-10-03 0:34 ` [PATCH v3 3/4] configs: spacemit: Add K3 default configuration Yixun Lan
2026-10-03 8:04 ` E Shattow
2026-10-03 0:34 ` [PATCH v3 4/4] doc: spacemit: k3: Add Pico-ITX board Yixun Lan
2026-10-03 12:43 ` E Shattow
2026-10-04 1:39 ` Yixun Lan
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=20261003-00-basic-spacemit-k3-v3-0-dea68cd1bd7d@kernel.org \
--to=dlan@kernel.org \
--cc=hfranco@baylibre.com \
--cc=junhui.liu@pigmoral.tech \
--cc=leo.liang@sifive.com \
--cc=me@ziyao.cc \
--cc=michal.simek@amd.com \
--cc=raymond.mao@riscstar.com \
--cc=tim609@andestech.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.u-boot-project.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.