From: Shawn Lin <shawn.lin@rock-chips.com>
Date: Fri, 30 Sep 2016 06:18:59 +0000 (+0800)
Subject: mmc: core: changes frequency to hs_max_dtr when selecting hs400es
X-Git-Tag: v4.14-rc1~2225^2~13
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=4f25580fb84d934d7ecffa3c0aa8f10f7e23af92;p=platform%2Fkernel%2Flinux-rpi.git

mmc: core: changes frequency to hs_max_dtr when selecting hs400es

Per JESD84-B51 P49, Host need to change frequency to <=52MHz
after setting HS_TIMING to 0x1, and host may changes frequency
to <= 200MHz after setting HS_TIMING to 0x3. That means the card
expects the clock rate to increase from the current used f_init
(which is less than 400KHz, but still being less than 52MHz) to
52MHz, otherwise we find some eMMC devices significantly report
failure when sending status.

Reported-by: Xiao Yao <xiaoyao@rock-chips.com>
Signed-off-by: Shawn Lin <shawn.lin@rock-chips.com>
Reviewed-by: Douglas Anderson <dianders@chromium.org>
Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
---

diff --git a/drivers/mmc/core/mmc.c b/drivers/mmc/core/mmc.c
index f4ed5ac..39fc5b2 100644
--- a/drivers/mmc/core/mmc.c
+++ b/drivers/mmc/core/mmc.c
@@ -1282,6 +1282,8 @@ static int mmc_select_hs400es(struct mmc_card *card)
 	if (err)
 		goto out_err;
 
+	mmc_set_clock(host, card->ext_csd.hs_max_dtr);
+
 	err = mmc_switch_status(card);
 	if (err)
 		goto out_err;