The timeout clock for uSDHC is SDCLK, so it's reasonable to use the actual_clock to calculate the max timeout.
Signed-off-by: Dong Aisheng <[email protected]> --- drivers/mmc/host/sdhci-esdhc-imx.c | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/drivers/mmc/host/sdhci-esdhc-imx.c b/drivers/mmc/host/sdhci-esdhc-imx.c index c24cb23..83236d3 100644 --- a/drivers/mmc/host/sdhci-esdhc-imx.c +++ b/drivers/mmc/host/sdhci-esdhc-imx.c @@ -865,7 +865,8 @@ unsigned int esdhc_get_max_timeout(struct sdhci_host *host) struct pltfm_imx_data *imx_data = pltfm_host->priv; u32 max_to = esdhc_is_usdhc(imx_data) ? 1 << 28 : 1 << 27; - return max_to / (esdhc_pltfm_get_max_clock(host) / 1000); + return host->mmc->actual_clock ? + max_to / (host->mmc->actual_clock / 1000) : 0; } void esdhc_set_timeout(struct sdhci_host *host, struct mmc_command *cmd) -- 1.7.2.rc3 -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
