This patch is bug fixed..
I think that host->ios.clock(initial clock) will be set lower than 400KHz.
But in this code, if host->f_min is higher than 400KHz, print warning message 
and set higher than 400KHz.
And We use SDHCI_QUIRK_NONSTANDARD_CLOCK..so using get_min_clock function. 
but didn't effect nothing through used get_min_clock function.


 Signed-off-by: Jaehoon Chung <[email protected]>
---
 drivers/mmc/core/core.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/mmc/core/core.c b/drivers/mmc/core/core.c
index 569e94d..9cd5767 100644
--- a/drivers/mmc/core/core.c
+++ b/drivers/mmc/core/core.c
@@ -910,9 +910,9 @@ static void mmc_power_up(struct mmc_host *host)
        if (host->f_min > 400000) {
                pr_warning("%s: Minimum clock frequency too high for "
                                "identification mode\n", mmc_hostname(host));
-               host->ios.clock = host->f_min;
-       } else
                host->ios.clock = 400000;
+       } else
+               host->ios.clock = host->f_min;
 
        host->ios.power_mode = MMC_POWER_ON;
        mmc_set_ios(host);
-- 1.6.0.4 
--
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

Reply via email to