At HS400 mode the ITAPDLY value is that from High Speed mode
which is incorrect and may cause boot failures.

The ITAPDLY for HS400 speed mode should be the same as ITAPDLY
as HS200 timing after tuning is executed. Add the functionality
to save ITAPDLY from HS200 tuning and save as HS400 ITAPDLY.

Fixes: c964447ea3d6 ("mmc: am654_sdhci: Add support for input tap delay")
Signed-off-by: Judith Mendez <j...@ti.com>
---
 drivers/mmc/am654_sdhci.c | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/drivers/mmc/am654_sdhci.c b/drivers/mmc/am654_sdhci.c
index dee56dfdbaa..ce3813ea3d0 100644
--- a/drivers/mmc/am654_sdhci.c
+++ b/drivers/mmc/am654_sdhci.c
@@ -293,6 +293,11 @@ static int am654_sdhci_set_ios_post(struct sdhci_host 
*host)
                        return ret;
 
                plat->dll_enable = true;
+               if (mode == MMC_HS_400) {
+                       plat->itap_del_ena[mode] = 0x1;
+                       plat->itap_del_sel[mode] = plat->itap_del_sel[mode - 1];
+               }
+
                am654_sdhci_write_itapdly(plat, plat->itap_del_sel[mode],
                                          plat->itap_del_ena[mode]);
        } else {
@@ -484,6 +489,9 @@ static int am654_sdhci_execute_tuning(struct mmc *mmc, u8 
opcode)
        itap = am654_sdhci_calculate_itap(dev, fail_window, fail_index,
                                          plat->dll_enable);
 
+       /* Save ITAPDLY */
+       plat->itap_del_sel[mode] = itap;
+
        am654_sdhci_write_itapdly(plat, itap, plat->itap_del_ena[mode]);
 
        return 0;
-- 
2.43.2

Reply via email to