diff options
author | 2019-06-11 22:03:43 +0200 | |
---|---|---|
committer | 2019-06-17 13:18:11 +0200 | |
commit | b0e370b95a3b231d0fb5d1958cce85ef57196fe6 (patch) | |
tree | e2226e70bfbbd45948598e95267afbaf575ee6ef /tools/perf/scripts/python/export-to-sqlite.py | |
parent | mmc: sdhi: disallow HS400 for M3-W ES1.2, RZ/G2M, and V3H (diff) | |
download | wireguard-linux-b0e370b95a3b231d0fb5d1958cce85ef57196fe6.tar.xz wireguard-linux-b0e370b95a3b231d0fb5d1958cce85ef57196fe6.zip |
mmc: core: complete HS400 before checking status
We don't have a reproducible error case, yet our BSP team suggested that
the mmc_switch_status() command in mmc_select_hs400() should come after
the callback into the driver completing HS400 setup. It makes sense to
me because we want the status of a fully setup HS400, so it will
increase the reliability of the mmc_switch_status() command.
Reported-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Fixes: ba6c7ac3a2f4 ("mmc: core: more fine-grained hooks for HS400 tuning")
Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions