aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/mmc/host/sdhci-msm.c
diff options
context:
space:
mode:
authorTakeshi Saito <takeshi.saito.xv@renesas.com>2020-04-23 15:04:32 +0200
committerUlf Hansson <ulf.hansson@linaro.org>2020-05-28 11:21:02 +0200
commita38c078fea0b1393fd2acb50e91057d7e429d9aa (patch)
tree4f0753d9d645564b51be7776c12cfde1b1bcc605 /drivers/mmc/host/sdhci-msm.c
parentmmc: renesas_sdhi: handle M3-W ES1.2 and 1.3 revisions (diff)
downloadlinux-dev-a38c078fea0b1393fd2acb50e91057d7e429d9aa.tar.xz
linux-dev-a38c078fea0b1393fd2acb50e91057d7e429d9aa.zip
mmc: renesas_sdhi: Avoid bad TAP in HS400
With R-Car Gen3, CRC error occue at the following TAPs. H3, M3W 1.3, M3N... TAP=2,3,6,7 M3W 3.0 ... TAP=1,3,5,7 (Note: for 4tap SoCs, the numbers get divided by 2) Do not use these TAPs in HS400, and also don't use auto correction but manual correction. We check for bad taps in two places: 1) After tuning HS400: Then, we select a neighbouring TAP. One of them must be good, because there are never three bad taps in a row. Retuning won't help because we just finished tuning. 2) After a manual correction request: Here, we can't switch to the requested TAP. But we can retune (if the HS200 tuning was good) because the environment might have changed since the last tuning. If not, we stay on the same TAP. Signed-off-by: Takeshi Saito <takeshi.saito.xv@renesas.com> [wsa: refactored to match upstream driver, reworded commit msg] Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com> Reviewed-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com> Link: https://lore.kernel.org/r/20200423130432.9990-3-wsa+renesas@sang-engineering.com Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
Diffstat (limited to 'drivers/mmc/host/sdhci-msm.c')
0 files changed, 0 insertions, 0 deletions