aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-sqlite.py
diff options
context:
space:
mode:
authorWolfram Sang <[email protected]>2021-06-24 17:16:14 +0200
committerUlf Hansson <[email protected]>2021-06-29 16:28:50 +0200
commit77347eda64ed5c9383961d1de9165f9d0b7d8df6 (patch)
tree703223ca265bec84ccc1d3a01cff4c68b1c2b113 /tools/perf/scripts/python/export-to-sqlite.py
parentc54b245d011855ea91c5beff07f1db74143ce614 (diff)
mmc: core: clear flags before allowing to retune
It might be that something goes wrong during tuning so the MMC core will immediately trigger a retune. In our case it was: - we sent a tuning block - there was an error so we need to send an abort cmd to the eMMC - the abort cmd had a CRC error - retune was set by the MMC core This lead to a vicious circle causing a performance regression of 75%. So, clear retuning flags before we enable retuning to start with a known cleared state. Reported-by Yoshihiro Shimoda <[email protected]> Suggested-by: Adrian Hunter <[email protected]> Signed-off-by: Wolfram Sang <[email protected]> Acked-by: Adrian Hunter <[email protected]> Reviewed-by: Yoshihiro Shimoda <[email protected]> Tested-by: Yoshihiro Shimoda <[email protected]> Fixes: bd11e8bd03ca ("mmc: core: Flag re-tuning is needed on CRC errors") Cc: [email protected] Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Ulf Hansson <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions