From: Quentin Schulz <quentin.schulz@cherry.de>
To: Quentin Schulz <foss+kernel@0leil.net>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>
Cc: Jakob Unterwurzacher <jakob.unterwurzacher@cherry.de>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: rockchip: disable HS400 on RK3588 Tiger
Date: Thu, 13 Nov 2025 10:57:16 +0100 [thread overview]
Message-ID: <575fd825-5ee8-4a46-b9ef-2a16d9ce61b1@cherry.de> (raw)
In-Reply-To: <20251112-tiger-hs200-v1-1-b50adac107c0@cherry.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
next prev parent reply other threads:[~2025-11-13 9:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 15:01 Quentin Schulz
2025-11-13 9:57 ` Quentin Schulz [this message]
2025-11-13 23:18 ` Heiko Stuebner
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=575fd825-5ee8-4a46-b9ef-2a16d9ce61b1@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=foss+kernel@0leil.net \
--cc=heiko@sntech.de \
--cc=jakob.unterwurzacher@cherry.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
/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
all inboxes | Powered by JetHome®