diff options
| author | Matt Roper <matthew.d.roper@intel.com> | 2015-04-09 10:48:38 -0700 |
|---|---|---|
| committer | Daniel Vetter <daniel.vetter@ffwll.ch> | 2015-04-10 09:37:01 +0200 |
| commit | f1e2daea79e96a50cdbca1bdd1a70900e1af5da1 (patch) | |
| tree | 074be95504e4d9b9a5f7d7752db8c51ac0283ccd /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | 70a101f8639a712576c3ca1d910564c7e2ec91d8 (diff) | |
drm/i915: Clear crtc atomic flags at beginning of transaction
Once we have full atomic modeset, these kind of flags should be in a
real intel_crtc_state that's tracked properly. In the meantime, make
sure we clear out any old flags at the beginning of a transaction so
that we don't wind up seeing leftover flags from old transactions that
were checked, but never went to the commit step. At the moment, a
failed check or prepare could leave stale flags behind that interfere
with the next atomic transaction.
v2: Just do a memset; the series this patch was originally part of
placed additional fields into the structure that shouldn't be
cleared, but that's no longer the case.
Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions
