Message ID | 20250214151700.666544-1-javierm@redhat.com (mailing list archive) |
---|---|
Headers | show |
Series | riscv: dts: spacemit: Add initial support for Milk-V Jupiter | expand |
Hi Javier: On 16:16 Fri 14 Feb , Javier Martinez Canillas wrote: > Hello, > > This patch-set adds a minimal support for the Milk-V Jupiter board. > which is a Mini ITX computer based on the SpacemiT K1/M1 RISC-V SoC. > > The DTS is very basic but at least allows to boot into a serial console > and get UART output, similar to what exists for other K1 based boards > such as the BananaPi BPI-F3. > > Patch #1 just adds the compatible string for the Milk-V Jupiter to the > SpacemiT bindings and patch #2 adds the minimal DTS for this computer. > > Best regards, > Javier > > > Javier Martinez Canillas (2): > dt-bindings: riscv: spacemit: Add Milk-V Jupiter board compatible > riscv: dts: spacemit: Add Milk-V Jupiter board device tree > Reviewed-by: Yixun Lan <dlan@gentoo.org> > .../devicetree/bindings/riscv/spacemit.yaml | 1 + > arch/riscv/boot/dts/spacemit/Makefile | 1 + > .../boot/dts/spacemit/k1-milkv-jupiter.dts | 27 +++++++++++++++++++ > 3 files changed, 29 insertions(+) > create mode 100644 arch/riscv/boot/dts/spacemit/k1-milkv-jupiter.dts > > -- > 2.48.1 >
On Fri, 14 Feb 2025 16:16:36 +0100, Javier Martinez Canillas wrote: > This patch-set adds a minimal support for the Milk-V Jupiter board. > which is a Mini ITX computer based on the SpacemiT K1/M1 RISC-V SoC. > > The DTS is very basic but at least allows to boot into a serial console > and get UART output, similar to what exists for other K1 based boards > such as the BananaPi BPI-F3. > > [...] Thanks, Applied to SpacemiT's SoC tree: https://github.com/spacemit-com/linux/ (for-next) [1/2] dt-bindings: riscv: spacemit: Add Milk-V Jupiter board compatible https://github.com/spacemit-com/linux/commit/8c8d2a19a3ad87d9344a5e58172f8e0c05c4622a [2/2] riscv: dts: spacemit: Add Milk-V Jupiter board device tree https://github.com/spacemit-com/linux/commit/5b90a3d6092d9292d3c4fe4eef8969282e070ae3 The for-next branch will be sent via a formal Pull Request to the Linux SoC maintainers for inclusion in next merge window. Best regards,