| author | Archit Taneja <archit@ti.com> | |
| Wed, 7 Nov 2012 09:17:24 +0000 (14:47 +0530) | ||
| committer | Tomi Valkeinen <tomi.valkeinen@ti.com> | |
| Mon, 12 Nov 2012 11:52:59 +0000 (13:52 +0200) | ||
| commit | c90929020986d12577570139ed6b787367823ade | |
| tree | 9d9cd1fa496d1f69254483368c2a3f08c7cc3647 | tree | snapshot (tar.xz tar.gz zip) |
| parent | ca8d4e8bb201db9bc5619561f3c13f6beb58329c | commit | diff |
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>
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>
| drivers/video/omap2/dss/apply.c | diff | blob | history |