On 7/23/20 1:30 PM, Yangbo Lu wrote:
Some controllers may have difference between HS200 tuning and HS400 tuning, such as different registers setting, different procedure, or different errata.
This patch is to add a hs400_tuning flag to identify the tuning for HS400 mode.
Signed-off-by: Yangbo Lu yangbo.lu@nxp.com
Changes for v2:
- None.
Changes for v3:
- Explained more in commit messages.
drivers/mmc/mmc.c | 2 ++ include/mmc.h | 1 + 2 files changed, 3 insertions(+)
diff --git a/drivers/mmc/mmc.c b/drivers/mmc/mmc.c index a4c6153..f020a8e 100644 --- a/drivers/mmc/mmc.c +++ b/drivers/mmc/mmc.c @@ -1981,7 +1981,9 @@ static int mmc_select_hs400(struct mmc *mmc) mmc_set_clock(mmc, mmc->tran_speed, false);
/* execute tuning if needed */
- mmc->hs400_tuning = 1; err = mmc_execute_tuning(mmc, MMC_CMD_SEND_TUNING_BLOCK_HS200);
- mmc->hs400_tuning = 0;
It seems that it's fsl_esdhc specific flag. Is it need to set to 0?
Best Regards, Jaehoon Chung
if (err) { debug("tuning failed\n"); return err; diff --git a/include/mmc.h b/include/mmc.h index 161b8bc..2399cc2 100644 --- a/include/mmc.h +++ b/include/mmc.h @@ -707,6 +707,7 @@ struct mmc { * accessing the boot partitions */ u32 quirks;
- u8 hs400_tuning;
};
struct mmc_hwpart_conf {