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>
This commit is contained in:
parent
930f152cc9
commit
eb91b9118d
|
@ -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;
|
||||
|
|
Loading…
Reference in a new issue