diff options
| author | Christian Hewitt <christianshewitt@gmail.com> | 2020-07-21 01:59:50 +0000 |
|---|---|---|
| committer | Kevin Hilman <khilman@baylibre.com> | 2020-07-27 11:53:47 -0700 |
| commit | f1bb924e8f5b50752a80fa5b48c43003680a7b64 (patch) | |
| tree | 0af46cc342518e5879739890aef7c31a3b996bc5 /arch/arm64/boot/dts/amlogic/meson-sm1-khadas-vim3l.dts | |
| parent | 2fa17dd09533d5d83201be3229a28c1010a8ea3e (diff) | |
arm64: dts: meson: fix mmc0 tuning error on Khadas VIM3
Similar to other G12B devices using the W400 dtsi, I see reports of mmc0
tuning errors on VIM3 after a few hours uptime:
[12483.917391] mmc0: tuning execution failed: -5
[30535.551221] mmc0: tuning execution failed: -5
[35359.953671] mmc0: tuning execution failed: -5
[35561.875332] mmc0: tuning execution failed: -5
[61733.348709] mmc0: tuning execution failed: -5
I do not see the same on VIM3L, so remove sd-uhs-sdr50 from the common dtsi
to silence the error, then (re)add it to the VIM3L dts.
Fixes: 4f26cc1c96c9 ("arm64: dts: khadas-vim3: move common nodes into meson-khadas-vim3.dtsi")
Fixes: 700ab8d83927 ("arm64: dts: khadas-vim3: add support for the SM1 based VIM3L")
Signed-off-by: Christian Hewitt <christianshewitt@gmail.com>
Signed-off-by: Kevin Hilman <khilman@baylibre.com>
Link: https://lore.kernel.org/r/20200721015950.11816-1-christianshewitt@gmail.com
Diffstat (limited to 'arch/arm64/boot/dts/amlogic/meson-sm1-khadas-vim3l.dts')
| -rw-r--r-- | arch/arm64/boot/dts/amlogic/meson-sm1-khadas-vim3l.dts | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/arch/arm64/boot/dts/amlogic/meson-sm1-khadas-vim3l.dts b/arch/arm64/boot/dts/amlogic/meson-sm1-khadas-vim3l.dts index b104967dbef1..0da56c051a0e 100644 --- a/arch/arm64/boot/dts/amlogic/meson-sm1-khadas-vim3l.dts +++ b/arch/arm64/boot/dts/amlogic/meson-sm1-khadas-vim3l.dts @@ -164,6 +164,10 @@ status = "okay"; }; +&sd_emmc_a { + sd-uhs-sdr50; +}; + &usb { phys = <&usb2_phy0>, <&usb2_phy1>; phy-names = "usb2-phy0", "usb2-phy1"; |