Skip to contentSkip to conversation

ARM: dts: rockchip: remove cap-mmc-highspeed property from mk808 &mmc0 node

PATCH In review Johan Jonker 2 participants 4 messages Aug 20, 2021

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 ARM: dts: rockchip: remove cap-mmc-highspeed property from mk808 &mmc0 node

On the MK808 only a microSD slot is connected with the SDMMC Host Controller, so remove the cap-mmc-highspeed property from the &mmc0 node.

---
 arch/arm/boot/dts/rk3066a-mk808.dts | 1 -
 1 file changed, 1 deletion(-)
arch/arm/boot/dts/rk3066a-mk808.dts +0 -1
index 9790bc63b..b67f5cb51 100644
@@ -123,7 +123,6 @@
 
 &mmc0 {
 	bus-width = <4>;
-	cap-mmc-highspeed;
 	cap-sd-highspeed;
 	vmmc-supply = <&vcc_sd>;
 	status = "okay";
Signature · 1 line
2.20.1
#1 lore raw
Quoted 2 lines · Johan Jonker

On the MK808 only a microSD slot is connected with the SDMMC Host Controller, so remove the cap-mmc-highspeed property from the &mmc0 node.

Why, does it do any harm? It's perfectly possible to connect a full-sized card to a microSD slot with an adapter. I came across my old SDIO WiFi card a while back and tried it that way for a giggle, but unfortunately it turned out not to be a chipset supported by any upstream driver.

Robin.

Quoted 18 lines
---
  arch/arm/boot/dts/rk3066a-mk808.dts | 1 -
  1 file changed, 1 deletion(-)
arch/arm/boot/dts/rk3066a-mk808.dts +0 -1
index 9790bc63b..b67f5cb51 100644
@@ -123,7 +123,6 @@
 
  &mmc0 {
  	bus-width = <4>;
-	cap-mmc-highspeed;
  	cap-sd-highspeed;
  	vmmc-supply = <&vcc_sd>;
  	status = "okay";
#2 lore raw
Quoted 6 lines · Robin Murphy
Quoted 3 lines · Johan Jonker

On the MK808 only a microSD slot is connected with the SDMMC Host Controller,
so remove the cap-mmc-highspeed property from the &mmc0 node.

Why, does it do any harm?

Harm not. Example rk3066 u-boot:

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

sd_select_mode_and_width

sd card: widths [4, 1, ] modes [MMC legacy, SD High Speed (50MHz), UHS SDR12 (25MHz), UHS SDR25 (50MHz), ]
host: widths [4, 1, ] modes [MMC legacy, MMC High Speed (26MHz), SD High Speed (50MHz), MMC High Speed (52MHz), ]
trying mode SD High Speed (50MHz) width 4 (at 50 MHz)

I would say only advertise host capabilities that are under normal circumstances occur. How realistic is it to use a TF/Micro SD TO SD Card Extension Cable Adapter (giggle) for a deprecated mmc card?

Johan

It's perfectly possible to connect a

Quoted 25 lines

full-sized card to a microSD slot with an adapter. I came across my old SDIO WiFi card a while back and tried it that way for a giggle, but unfortunately it turned out not to be a chipset supported by any upstream driver.

Robin.

Quoted 18 lines

---
  arch/arm/boot/dts/rk3066a-mk808.dts | 1 -

  1 file changed, 1 deletion(-)
arch/arm/boot/dts/rk3066a-mk808.dts +0 -1
index 9790bc63b..b67f5cb51 100644
@@ -123,7 +123,6 @@
     &mmc0 {
       bus-width = <4>;
-    cap-mmc-highspeed;
       cap-sd-highspeed;
       vmmc-supply = <&vcc_sd>;
       status = "okay";
 
#3 lore raw
Quoted 19 lines · Johan Jonker
Quoted 6 lines · Robin Murphy
Quoted 3 lines · Johan Jonker

On the MK808 only a microSD slot is connected with the SDMMC Host Controller,
so remove the cap-mmc-highspeed property from the &mmc0 node.

Why, does it do any harm?

Harm not. Example rk3066 u-boot:

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

sd_select_mode_and_width

sd card: widths [4, 1, ] modes [MMC legacy, SD High Speed (50MHz), UHS SDR12 (25MHz), UHS SDR25 (50MHz), ]
host: widths [4, 1, ] modes [MMC legacy, MMC High Speed (26MHz), SD High Speed (50MHz), MMC High Speed (52MHz), ]
trying mode SD High Speed (50MHz) width 4 (at 50 MHz)

Quoted 3 lines

I would say only advertise host capabilities that are under normal circumstances occur. How realistic is it to use a TF/Micro SD TO SD Card Extension Cable Adapter (giggle) for a deprecated mmc card?

Well, if you want a far more realistic example:

https://www.hardkernel.com/shop/emmc-module-reader-board-for-os-upgrade/

Who are we to dictate what "normal circumstances" are, and what do we gain by removing support for modes that could work fine and at least be useful to someone on occasion?

Robin.