aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/drivers/clk/clk-asm9260.c
diff options
context:
space:
mode:
authorPeter Griffin <peter.griffin@linaro.org>2015-01-20 15:32:41 +0000
committerMichael Turquette <mturquette@linaro.org>2015-01-20 10:09:13 -0800
commitedc30077c926d55f500c3845f5f784c148f147db (patch)
treefe007517efb52fd68d66c57a548abed891ff02cd /drivers/clk/clk-asm9260.c
parentclk: ppc-corenet: rename driver to clk-qoriq (diff)
downloadwireguard-linux-edc30077c926d55f500c3845f5f784c148f147db.tar.xz
wireguard-linux-edc30077c926d55f500c3845f5f784c148f147db.zip
clk: st: STiH410: Fix pdiv and fdiv divisor when setting rate
Debugging eMMC on upstream kernels it has been noticed that when the targetpack configures MMC0 clock to 200Mhz (required to switch to HS200) then everything works OK. However if the kernel sets the clock rate using clk_set_rate, then the eMMC card initialisation fails with timeouts. Lower clock speeds (the default being 50Mhz) work ok, but they we fail to get good eMMC transfer rates. Looking through the vendor kernel clock driver reveals Giuseppe had already fixed this issue, but the patch hasn't made its way upstream. The issue is fixed by changing the logic to manage the pdiv and fdiv divisors used for setting the rate inside the flexgen driver code. Pdiv is mainly targeted for low freq results, while fdiv should be used for divs =< 64. The other way can lead to 'duty cycle' issues. I have changed the original patch to keep the original behaviour in cases where the div is >64 which matches the original comment and patch description more closely. Although no clocks appear to hit this case currently when booting an upstream kernel. Signed-off-by: Peter Griffin <peter.griffin@linaro.org> Signed-off-by: Giuseppe Cavallaro <peppe.cavallaro@st.com> Signed-off-by: Michael Turquette <mturquette@linaro.org>
Diffstat (limited to 'drivers/clk/clk-asm9260.c')
0 files changed, 0 insertions, 0 deletions