summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSimon Horman <horms@verge.net.au>2012-03-28 18:01:11 +0900
committerChris Ball <cjb@laptop.org>2012-04-05 20:32:24 -0400
commiteb91b9118db8c05a5a1257b594b021d32b491254 (patch)
tree59d946917c73b372dee2162b25eaa4f8c3d94816
parent930f152cc9998388031af577843baae572ac8ab6 (diff)
downloadlinux-eb91b9118db8c05a5a1257b594b021d32b491254.tar.gz
linux-eb91b9118db8c05a5a1257b594b021d32b491254.tar.bz2
linux-eb91b9118db8c05a5a1257b594b021d32b491254.zip
mmc: sh_mmcif: Simplify calculation of mmc->f_min
There is no need to tune mmc->f_min to a value near 400kHz as the MMC core begins testing frequencies at 400kHz regardless of the value of mmc->f_min. As suggested by Guennadi Liakhovetski. Cc: Magnus Damm <magnus.damm@gmail.com> Acked-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de> Tested-by: Cao Minh Hiep <hiepcm@gmail.com> Signed-off-by: Simon Horman <horms@verge.net.au> Signed-off-by: Chris Ball <cjb@laptop.org>
-rw-r--r--drivers/mmc/host/sh_mmcif.c8
1 files changed, 1 insertions, 7 deletions
diff --git a/drivers/mmc/host/sh_mmcif.c b/drivers/mmc/host/sh_mmcif.c
index 4bb999ed335d..724b35e85a26 100644
--- a/drivers/mmc/host/sh_mmcif.c
+++ b/drivers/mmc/host/sh_mmcif.c
@@ -1299,13 +1299,7 @@ static int __devinit sh_mmcif_probe(struct platform_device *pdev)
mmc->ops = &sh_mmcif_ops;
mmc->f_max = host->clk / 2;
- /* close to 400KHz */
- if (host->clk < 51200000)
- mmc->f_min = host->clk / 128;
- else if (host->clk < 102400000)
- mmc->f_min = host->clk / 256;
- else
- mmc->f_min = host->clk / 512;
+ mmc->f_min = host->clk / 512;
if (pd->ocr)
mmc->ocr_avail = pd->ocr;
mmc->caps = MMC_CAP_MMC_HIGHSPEED;