summaryrefslogtreecommitdiff
path: root/drivers/video/omap2/dss/apply.c
diff options
context:
space:
mode:
authorArchit Taneja <archit@ti.com>2012-11-07 13:17:24 +0400
committerTomi Valkeinen <tomi.valkeinen@ti.com>2012-11-12 15:52:59 +0400
commitc90929020986d12577570139ed6b787367823ade (patch)
tree9d9cd1fa496d1f69254483368c2a3f08c7cc3647 /drivers/video/omap2/dss/apply.c
parentca8d4e8bb201db9bc5619561f3c13f6beb58329c (diff)
downloadlinux-c90929020986d12577570139ed6b787367823ade.tar.xz
OMAPDSS: APPLY: Remove unnecessary call to mg_clear_shadow_dirty
When doing a manual update in dss_mgr_start_update, we clear the shadow dirty flags. Although there isn't any harm in clearing them. The need to clear them out here should never arrive. When applying configurations for a manual update manager, we never do any register writes, i.e, calls to dss_mgr_write_regs and dss_mgr_write_regs_extra never happen while applying. We do all these writes only when we call dss_mgr_start_update. Hence, there is never a time when the shadow registers are dirty. Remove the call to mg_clear_shadow_dirty. Signed-off-by: Archit Taneja <archit@ti.com> Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Diffstat (limited to 'drivers/video/omap2/dss/apply.c')
-rw-r--r--drivers/video/omap2/dss/apply.c2
1 files changed, 0 insertions, 2 deletions
diff --git a/drivers/video/omap2/dss/apply.c b/drivers/video/omap2/dss/apply.c
index 55fb5d778ae5..4a5cc5c64d4b 100644
--- a/drivers/video/omap2/dss/apply.c
+++ b/drivers/video/omap2/dss/apply.c
@@ -770,8 +770,6 @@ void dss_mgr_start_update(struct omap_overlay_manager *mgr)
dispc_mgr_enable_sync(mgr->id);
- mgr_clear_shadow_dirty(mgr);
-
spin_unlock_irqrestore(&data_lock, flags);
}