summaryrefslogtreecommitdiff
path: root/drivers/spi/tegra210_qspi.c
diff options
context:
space:
mode:
authorTom Warren <twarren@nvidia.com>2019-06-04 02:06:34 +0300
committerTom Warren <twarren@nvidia.com>2020-04-03 00:30:01 +0300
commita482f32992230d8bdae2caa72056ab7d9208d5f0 (patch)
tree02b8009a11d357044536905c5eeb79e8d1ceba3e /drivers/spi/tegra210_qspi.c
parent5e965e814067e7539943bbaeb47d7bf9738a701b (diff)
downloadu-boot-a482f32992230d8bdae2caa72056ab7d9208d5f0.tar.xz
mmc: t210: Fix 'bad' SD-card clock when doing 400KHz card detect
According to the HW team, for some reason the normal clock select code picks what appears to be a perfectly valid 375KHz SD card clock, based on the CAR clock source and SDMMC1 controller register settings (CAR = 408MHz PLLP0 divided by 68 for 6MHz, then a SD Clock Control register divisor of 16 = 375KHz). But the resulting SD card clock, as measured by the HW team, is 700KHz, which is out-of-spec. So the WAR is to use the values given in the TRM PLLP table to generate a 400KHz SD-clock (CAR clock of 24.7MHz, SD Clock Control divisor of 62) only for SDMMC1 on T210 when the requested clock is <= 400KHz. Note that as far as I can tell, the other requests for clocks in the Tegra MMC driver result in valid SD clocks. Signed-off-by: Tom Warren <twarren@nvidia.com> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
Diffstat (limited to 'drivers/spi/tegra210_qspi.c')
0 files changed, 0 insertions, 0 deletions