summaryrefslogtreecommitdiffstats
path: root/drivers/xen/gntdev-dmabuf.h
diff options
context:
space:
mode:
authorFaiz Abbas <faiz_abbas@ti.com>2018-12-11 19:52:53 +0530
committerUlf Hansson <ulf.hansson@linaro.org>2018-12-17 08:26:24 +0100
commit961de0a856e3a30c0238d1269c0b17f9b179b6c3 (patch)
treee6fbe9554d977af91ce2044a0401dc14b6d97541 /drivers/xen/gntdev-dmabuf.h
parent58fe8bbacd285af44831f68da1d2d50f0e2fc9a9 (diff)
downloadlinux-961de0a856e3a30c0238d1269c0b17f9b179b6c3.tar.bz2
mmc: sdhci-omap: Workaround errata regarding SDR104/HS200 tuning failures (i929)
Errata i929 in certain OMAP5/DRA7XX/AM57XX silicon revisions (SPRZ426D - November 2014 - Revised February 2018 [1]) mentions unexpected tuning pattern errors. A small failure band may be present in the tuning range which may be missed by the current algorithm. Furthermore, the failure bands vary with temperature leading to different optimum tuning values for different temperatures. As suggested in the related Application Report (SPRACA9B - October 2017 - Revised July 2018 [2]), tuning should be done in two stages. In stage 1, assign the optimum ratio in the maximum pass window for the current temperature. In stage 2, if the chosen value is close to the small failure band, move away from it in the appropriate direction. References: [1] http://www.ti.com/lit/pdf/sprz426 [2] http://www.ti.com/lit/pdf/SPRACA9 Signed-off-by: Faiz Abbas <faiz_abbas@ti.com> Acked-by: Adrian Hunter <adrian.hunter@intel.com> Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
Diffstat (limited to 'drivers/xen/gntdev-dmabuf.h')
0 files changed, 0 insertions, 0 deletions