From: Quentin Schulz <quentin.schulz@cherry.de>

We've had reports from the field that some RK3588 Tiger have random
issues with eMMC errors.

Applying commit a28352cf2d2f ("mmc: sdhci-of-dwcmshc: Change
DLL_STRBIN_TAPNUM_DEFAULT to 0x4") didn't help and seemed to have made
things worse for our board.

Our HW department checked the eMMC lines and reported that they are too
long and don't look great so signal integrity is probably not the best.

Note that not all Tigers with the same eMMC chip have errors, so the
suspicion is that we're really on the edge in terms of signal integrity
and only a handful devices are failing. Additionally, we have RK3588
Jaguars with the same eMMC chip but the layout is different and we also
haven't received reports about those so far.

Lowering the max-frequency to 150MHz from 200MHz instead of simply
disabling HS400 was briefly tested and seem to work as well. We've
disabled HS400 downstream and haven't received reports since so we'll go
with that instead of lowering the max-frequency.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 arch/arm64/boot/dts/rockchip/rk3588-tiger.dtsi | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/arch/arm64/boot/dts/rockchip/rk3588-tiger.dtsi b/arch/arm64/boot/dts/rockchip/rk3588-tiger.dtsi
index b44e89e1bb159..365c1d958f2d5 100644
--- a/arch/arm64/boot/dts/rockchip/rk3588-tiger.dtsi
+++ b/arch/arm64/boot/dts/rockchip/rk3588-tiger.dtsi
@@ -382,14 +382,12 @@ &sdhci {
 	cap-mmc-highspeed;
 	mmc-ddr-1_8v;
 	mmc-hs200-1_8v;
-	mmc-hs400-1_8v;
-	mmc-hs400-enhanced-strobe;
 	mmc-pwrseq = <&emmc_pwrseq>;
 	no-sdio;
 	no-sd;
 	non-removable;
 	pinctrl-names = "default";
-	pinctrl-0 = <&emmc_bus8 &emmc_cmd &emmc_clk &emmc_data_strobe>;
+	pinctrl-0 = <&emmc_bus8 &emmc_cmd &emmc_clk>;
 	vmmc-supply = <&vcc_3v3_s3>;
 	vqmmc-supply = <&vcc_1v8_s3>;
 	status = "okay";

---
base-commit: 6bff916a7e9b6b7f6bd06eb5722e6dfbb777f13e
change-id: 20251112-tiger-hs200-e5b87e1e5835

Best regards,
-- 
Quentin Schulz <quentin.schulz@cherry.de>

On Wed, 12 Nov 2025 16:01:53 +0100, Quentin Schulz wrote:
> We've had reports from the field that some RK3588 Tiger have random
> issues with eMMC errors.
> 
> Applying commit a28352cf2d2f ("mmc: sdhci-of-dwcmshc: Change
> DLL_STRBIN_TAPNUM_DEFAULT to 0x4") didn't help and seemed to have made
> things worse for our board.
> 
> [...]

Applied, thanks!

[1/1] arm64: dts: rockchip: disable HS400 on RK3588 Tiger
      commit: baa18d577cd445145039e731d3de0fa49ca57204

Best regards,
-- 
Heiko Stuebner <heiko@sntech.de>

Hi all,

On 11/12/25 4:01 PM, Quentin Schulz wrote:
> From: Quentin Schulz <quentin.schulz@cherry.de>
> 
> We've had reports from the field that some RK3588 Tiger have random
> issues with eMMC errors.
> 
> Applying commit a28352cf2d2f ("mmc: sdhci-of-dwcmshc: Change
> DLL_STRBIN_TAPNUM_DEFAULT to 0x4") didn't help and seemed to have made
> things worse for our board.
> 
> Our HW department checked the eMMC lines and reported that they are too
> long and don't look great so signal integrity is probably not the best.
> 
> Note that not all Tigers with the same eMMC chip have errors, so the
> suspicion is that we're really on the edge in terms of signal integrity
> and only a handful devices are failing. Additionally, we have RK3588
> Jaguars with the same eMMC chip but the layout is different and we also
> haven't received reports about those so far.
> 
> Lowering the max-frequency to 150MHz from 200MHz instead of simply
> disabling HS400 was briefly tested and seem to work as well. We've
> disabled HS400 downstream and haven't received reports since so we'll go
> with that instead of lowering the max-frequency.
> 
> Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>

Went too fast and forgot:

Fixes: 6173ef24b35b ("arm64: dts: rockchip: add RK3588-Q7 (Tiger) SoM")
Cc: stable@vger.kernel.org

Will give a few days for reviews and then send a v2 next week.

Cheers,
Quentin