summaryrefslogtreecommitdiff
path: root/drivers/video/omap2/dss/dss.c
diff options
context:
space:
mode:
authorTomi Valkeinen <tomi.valkeinen@ti.com>2012-05-15 12:31:01 (GMT)
committerTomi Valkeinen <tomi.valkeinen@ti.com>2012-05-22 07:59:13 (GMT)
commit3568f2a46f2a73bab18c914df06afd98a97e0e0e (patch)
treeff90a459d943101693a74e4ccf44112d1e9d3423 /drivers/video/omap2/dss/dss.c
parent6f28c2964b535f9439d52c437aa2fbfef7ed149c (diff)
downloadlinux-fsl-qoriq-3568f2a46f2a73bab18c914df06afd98a97e0e0e.tar.xz
OMAPDSS: use DSI_FIFO_BUG workaround only for manual update displays
There is a problem related to DSS FIFO thresholds and power management on OMAP3. It seems that when the full PM hits in, we get underflows. The core reason is unknown, but after experiments it looks like only particular FIFO thresholds work correctly. This bug is related to an earlier patch, which added special FIFO threshold configuration for OMAP3, because DSI command mode output didn't work with the normal threshold configuration. However, as the above work-around worked fine for other output types also, we currently always configure thresholds in this special way on OMAP3. In theory there should be negligible difference with this special way and the standard way. The first paragraph explains what happens in practice. This patch changes the driver to use the special threshold configuration only when the output is a manual update display on OMAP3. This does include RFBI displays also, and although it hasn't been tested (no boards using RFBI) I suspect the similar behaviour is present there also, as the DISPC side should work similarly for DSI command mode and RFBI. Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com> Cc: Joe Woodward <jw@terrafix.co.uk>
Diffstat (limited to 'drivers/video/omap2/dss/dss.c')
0 files changed, 0 insertions, 0 deletions