From: Matt Roper <matthew.d.roper@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH] drm/i915: Clear crtc atomic flags at beginning of transaction
Date: Thu, 9 Apr 2015 10:48:38 -0700 [thread overview]
Message-ID: <1428601718-9670-1-git-send-email-matthew.d.roper@intel.com> (raw)
In-Reply-To: <20150409155152.GT12038@phenom.ffwll.local>
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>
---
drivers/gpu/drm/i915/intel_atomic.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/i915/intel_atomic.c b/drivers/gpu/drm/i915/intel_atomic.c
index 3903b90..b4ea676 100644
--- a/drivers/gpu/drm/i915/intel_atomic.c
+++ b/drivers/gpu/drm/i915/intel_atomic.c
@@ -76,6 +76,8 @@ int intel_atomic_check(struct drm_device *dev,
state->allow_modeset = false;
for (i = 0; i < ncrtcs; i++) {
struct intel_crtc *crtc = to_intel_crtc(state->crtcs[i]);
+ if (crtc)
+ memset(&crtc->atomic, 0, sizeof(crtc->atomic));
if (crtc && crtc->pipe != nuclear_pipe)
not_nuclear = true;
}
--
1.8.5.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-04-09 17:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 1:56 [PATCH 0/4] Misc atomic-related updates Matt Roper
2015-04-09 1:56 ` [PATCH 1/4] drm/i915: Make atomic use in-flight state for CRTC active value Matt Roper
2015-04-09 12:42 ` Daniel Vetter
2015-04-09 14:00 ` Matt Roper
2015-04-09 14:45 ` Daniel Vetter
2015-04-09 14:49 ` Matt Roper
2015-04-09 13:18 ` Ville Syrjälä
2015-04-09 14:10 ` Matt Roper
2015-04-09 14:46 ` Ville Syrjälä
2015-04-09 14:54 ` Matt Roper
2015-04-10 7:24 ` Daniel Vetter
2015-04-09 1:56 ` [PATCH 2/4] drm/i915: Lookup CRTC for plane directly Matt Roper
2015-04-09 12:44 ` Daniel Vetter
2015-04-09 14:36 ` Matt Roper
2015-04-09 1:56 ` [PATCH 3/4] drm/i915: Switch to full atomic helpers for plane updates/disable, take two Matt Roper
2015-04-09 12:46 ` Daniel Vetter
2015-04-09 18:03 ` Matt Roper
2015-04-15 0:48 ` Konduru, Chandra
2015-04-09 1:56 ` [PATCH 4/4] drm/i915: Clear crtc atomic flags at beginning of transaction Matt Roper
2015-04-09 12:48 ` Daniel Vetter
2015-04-09 15:03 ` Matt Roper
2015-04-09 15:51 ` Daniel Vetter
2015-04-09 17:48 ` Matt Roper [this message]
2015-04-10 7:37 ` [PATCH] " Daniel Vetter
2015-04-10 20:05 ` shuang.he
2015-04-10 2:36 ` [PATCH 4/4] " shuang.he
-- strict thread matches above, loose matches on Subject: below --
2015-02-24 1:52 [PATCH] drm/i915: Fix frontbuffer false positve Rodrigo Vivi
2015-02-24 2:14 ` [PATCH] drm/i915: Clear crtc atomic flags at beginning of transaction Matt Roper
2015-02-24 17:43 ` Rodrigo Vivi
2015-02-24 17:52 ` Rodrigo Vivi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1428601718-9670-1-git-send-email-matthew.d.roper@intel.com \
--to=matthew.d.roper@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox