From: Daniel Vetter <daniel@ffwll.ch>
To: Paulo Zanoni <przanoni@gmail.com>
Cc: intel-gfx@lists.freedesktop.org,
Paulo Zanoni <paulo.r.zanoni@intel.com>,
stable@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: fix cursor handling when runtime suspended
Date: Thu, 24 Jul 2014 00:41:11 +0200 [thread overview]
Message-ID: <20140723224111.GI15237@phenom.ffwll.local> (raw)
In-Reply-To: <20140723223525.GH15237@phenom.ffwll.local>
On Thu, Jul 24, 2014 at 12:35:25AM +0200, Daniel Vetter wrote:
> On Wed, Jul 23, 2014 at 06:30:59PM -0300, Paulo Zanoni wrote:
> > From: Paulo Zanoni <paulo.r.zanoni@intel.com>
> >
> > If we're runtime suspended and try to use the cursor interfaces, we
> > will get a lot of WARNs saying we did the wrong thing.
> >
> > For intel_crtc_update_cursor(), all we need to do is return if the
> > CRTC is not active, since writing the registers won't really have any
> > effect if the screen is not visible, and we will write the registers
> > later when enabling the screen.
> >
> > For intel_crtc_cursor_set_obj(), we just get the proper power domain
> > reference, since this function does a lot of stuff.
> >
> > Testcase: igt/pm_rpm/cursor
> > Testcase: igt/pm_rpm/cursor-dpms
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=81645
> > Cc: stable@vger.kernel.org
> > Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
> > ---
> > drivers/gpu/drm/i915/intel_display.c | 15 ++++++++++++---
> > 1 file changed, 12 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> > index d1e9570..c8f36b0 100644
> > --- a/drivers/gpu/drm/i915/intel_display.c
> > +++ b/drivers/gpu/drm/i915/intel_display.c
> > @@ -8151,6 +8151,9 @@ static void intel_crtc_update_cursor(struct drm_crtc *crtc,
> > if (base == 0 && intel_crtc->cursor_base == 0)
> > return;
> >
> > + if (!intel_crtc->active)
> > + return;
>
> Don't we need the same trick in intel_crtc_cursor_set_obj? This gets
> called if the cursor object changes (instead of just moving it around).
Rechecked and realized the only I915_WRITE in there is for gen2. I guess
we don't care ;-)
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-07-23 22:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 21:30 [PATCH] drm/i915: fix cursor handling when runtime suspended Paulo Zanoni
2014-07-23 21:31 ` [PATCH] tests/pm_rpm: add cursor subtests Paulo Zanoni
2014-07-23 22:35 ` [Intel-gfx] [PATCH] drm/i915: fix cursor handling when runtime suspended Daniel Vetter
2014-07-23 22:41 ` Daniel Vetter [this message]
2014-07-23 23:38 ` Paulo Zanoni
2014-07-24 7:35 ` Daniel Vetter
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=20140723224111.GI15237@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=paulo.r.zanoni@intel.com \
--cc=przanoni@gmail.com \
--cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.