From: Conor Dooley <conor@kernel.org>
To: E Shattow <e@freeshell.de>
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH v1 0/4] riscv: dts: starfive: Add Milk-V Mars CM (Lite) SoM
Date: Tue, 12 Aug 2025 19:05:43 +0100 [thread overview]
Message-ID: <20250812-endearing-spiral-4c0713898043@spud> (raw)
In-Reply-To: <20250724094912.253723-1-e@freeshell.de>
[-- Attachment #1.1: Type: text/plain, Size: 2360 bytes --]
Emil,
Could you take a look at this please?
Cheers,
Conor.
On Thu, Jul 24, 2025 at 02:48:43AM -0700, E Shattow wrote:
> Milk-V Mars CM and Mars CM Lite System-on-Module both are based on the
> StarFive JH7110 SoC and compatible with the Raspberry Pi CM4IO Classic IO
> Board carrier. Mars CM Lite is Mars CM without the eMMC storage component
> on mmc0 and the mmc0 interface configured instead for SD Card use. The
> optional WiFi+BT chipset is connected via SDIO on the mmc1 interface that
> would otherwise be connected to an SD Card slot on the StarFive
> VisionFive2 reference design.
>
> Add the related devicetree files for both Milk-V Mars CM and Milk-V Mars
> CM Lite describing the currently supported features, namely PMIC, UART,
> I2C, GPIO, eMMC or SD Card, WiFi+BT, QSPI Flash, and Ethernet.
>
> Caveat with vendor AP6256 firmware files present the firmware loading is
> successful but subsequently fails IRQ wake initialization. Common GPIO
> conflicts for "WiFi" optioned boards having this module:
>
> pwmdac_pins:
> - AP6256: WL_REG_ON>>WIFI_REG_ON_H_GPIO33
> - AP6256: WL_HOST_WAKE>>WIFI_WAKE_HOST_H_GPIO34
>
> i2c2_pins:
> - AP6256: UART_CTS_N<<UART1_RTSn_GPIO2
> - AP6256: UART_RTS_N>>UART1_CTSn_GPIO3
>
> i2c6_pins:
> - AP6256: UART_RXD<<UART_TX_GPIO16
> - AP6256: UART_TXD>>UART_RX_GPIO17
>
> Tested successfully for basic mmc0 storage, USB, and network functionality on:
> - Milk-V Mars CM 8GB
> - Milk-V Mars CM Lite 4GB
> - Milk-V Mars CM Lite WiFi 8GB
>
> E Shattow (4):
> dt-bindings: riscv: starfive: add milkv,marscm-emmc
> riscv: dts: starfive: add Milk-V Mars CM system-on-module
> dt-bindings: riscv: starfive: add milkv,marscm-lite
> riscv: dts: starfive: add Milk-V Mars CM Lite system-on-module
>
> .../devicetree/bindings/riscv/starfive.yaml | 2 +
> arch/riscv/boot/dts/starfive/Makefile | 2 +
> .../dts/starfive/jh7110-milkv-marscm-emmc.dts | 163 ++++++++++++++++
> .../dts/starfive/jh7110-milkv-marscm-lite.dts | 176 ++++++++++++++++++
> 4 files changed, 343 insertions(+)
> create mode 100644 arch/riscv/boot/dts/starfive/jh7110-milkv-marscm-emmc.dts
> create mode 100644 arch/riscv/boot/dts/starfive/jh7110-milkv-marscm-lite.dts
>
>
> base-commit: 28fa0dcb571ab8f3be4d919f0e20e01d4e44bcb1
> --
> 2.50.0
>
>
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2025-08-12 20:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 9:48 [PATCH v1 0/4] riscv: dts: starfive: Add Milk-V Mars CM (Lite) SoM E Shattow
2025-07-24 9:48 ` [PATCH v1 1/4] dt-bindings: riscv: starfive: add milkv,marscm-emmc E Shattow
2025-07-25 23:13 ` Rob Herring (Arm)
2025-07-24 9:48 ` [PATCH v1 2/4] riscv: dts: starfive: add Milk-V Mars CM system-on-module E Shattow
2025-07-24 9:59 ` E Shattow
2025-07-24 9:48 ` [PATCH v1 3/4] dt-bindings: riscv: starfive: add milkv,marscm-lite E Shattow
2025-07-25 23:13 ` Rob Herring (Arm)
2025-07-24 9:48 ` [PATCH v1 4/4] riscv: dts: starfive: add Milk-V Mars CM Lite system-on-module E Shattow
2025-08-21 2:40 ` Hal Feng
2025-08-31 22:46 ` E Shattow
2025-08-12 18:05 ` Conor Dooley [this message]
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=20250812-endearing-spiral-4c0713898043@spud \
--to=conor@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=devicetree@vger.kernel.org \
--cc=e@freeshell.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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