Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Javier Martinez Canillas <javierm@redhat.com>
To: Chukun Pan <amadeus@jmu.edu.cn>, michael.opdenacker@rootcommit.com
Cc: dan.carpenter@linaro.org, dlan@gentoo.org,
	linux-riscv@lists.infradead.org, spacemit@lists.linux.dev,
	Chukun Pan <amadeus@jmu.edu.cn>
Subject: Re: [PATCH 2/2] riscv: dts: spacemit: Add MMC support on BPI-F3 and OrangePi RV2
Date: Mon, 29 Dec 2025 11:14:21 +0100	[thread overview]
Message-ID: <87zf71fvcy.fsf@ocarina.mail-host-address-is-not-set> (raw)
In-Reply-To: <20251224150003.1232791-1-amadeus@jmu.edu.cn>

Chukun Pan <amadeus@jmu.edu.cn> writes:

> Hi,
>
>> +&sdhci0 {
>> +	pinctrl-names = "default";
>> +	pinctrl-0 = <&mmc1_cfg>;
>
> It would be better to arrange them in alphabetical order.
> (Place pinctrl below no-sdio)
>
>> +	bus-width = <4>;
>> +	cd-gpios = <&gpio K1_GPIO(80) GPIO_ACTIVE_HIGH>;
>
> It seems that "cap-sd-highspeed" is missing?
>
>> +	cd-inverted;
>> +	no-sdio;
>> +	status = "okay";
>> +};
>
>> +			sdhci0: mmc@d4280000 {
>
> An immature idea. Would naming nodes this way be better?
>
> sdmmc: mmc@d4280000
>  sdio: mmc@d4280800
>  emmc: mmc@d4281000
>
> This seems to fit the description here better:
> https://bianbu-linux.spacemit.com/en/device/peripheral_driver/SDHC/#dts-configuration
>

I initially thought something similar but it's not accurate. Because as
explained in the doc that you referred:

* slot1 supports SD/SDIO (1/4 bit)
* slot2 supports SDIO/eMMC (1/4 bit)
* slot3 supports only eMMC (1/4/8 bit)

Which means that only slot3 is limited to eMMC.

So even when a typical configuration is what you mentioned (and what I saw
in most of the existing designs), slots 1 and 2 won't always be SD and SDIO.

-- 
Best regards,

Javier Martinez Canillas
Core Platforms
Red Hat


_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2025-12-29 10:14 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-15 10:10 [PATCH 0/2] Attempt to enable MMC on SpacemiT K1 boards Michael Opdenacker
2025-12-15 10:10 ` [PATCH 2/2] riscv: dts: spacemit: Add MMC support on BPI-F3 and OrangePi RV2 Michael Opdenacker
2025-12-15 12:46   ` Yao Zi
2025-12-15 13:58     ` Michael Opdenacker
2025-12-24 15:00   ` Chukun Pan
2025-12-29 10:14     ` Javier Martinez Canillas [this message]
2025-12-15 10:10 ` [PATCH 1/2] riscv: dts: spacemit: Add i2c buses on " Michael Opdenacker
2025-12-15 12:58   ` Yao Zi
2025-12-15 15:00     ` Michael Opdenacker
2025-12-16  5:37       ` Yao Zi
2025-12-16 21:05         ` Michael Opdenacker
2025-12-17 15:26           ` Iker Pedrosa
2025-12-17 16:27             ` Michael Opdenacker
2025-12-17 22:10               ` Johannes Erdfelt
2025-12-18  5:19                 ` Michael Opdenacker
2025-12-18  5:25                   ` Michael Opdenacker
2025-12-18  9:49                     ` Iker Pedrosa
2025-12-19 11:29                       ` Yixun Lan
2025-12-20  2:22                         ` Yao Zi
2025-12-17 20:25             ` Javier Martinez Canillas
2025-12-16  8:58   ` Javier Martinez Canillas
2025-12-24 14:00   ` Chukun Pan

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=87zf71fvcy.fsf@ocarina.mail-host-address-is-not-set \
    --to=javierm@redhat.com \
    --cc=amadeus@jmu.edu.cn \
    --cc=dan.carpenter@linaro.org \
    --cc=dlan@gentoo.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=michael.opdenacker@rootcommit.com \
    --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