From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>,
ville.syrjala@linux.intel.com, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 2/2] drm/i915: Kill intel_crtc->vbl_wait
Date: Thu, 22 May 2014 18:05:34 +0200 [thread overview]
Message-ID: <20140522160534.GV14357@phenom.ffwll.local> (raw)
In-Reply-To: <20140522154903.GC12436@nuc-i3427.alporthouse.com>
On Thu, May 22, 2014 at 04:49:03PM +0100, Chris Wilson wrote:
> On Thu, May 22, 2014 at 06:39:33PM +0300, ville.syrjala@linux.intel.com wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > Share the waitqueue that drm_irq uses when performing the vblank evade
> > trick for atomic pipe updates.
> >
> > Suggested-by: Daniel Vetter <daniel@ffwll.ch>
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > ---
> > drivers/gpu/drm/i915/i915_irq.c | 25 ++++++-------------------
> > drivers/gpu/drm/i915/intel_display.c | 2 --
> > drivers/gpu/drm/i915/intel_drv.h | 2 --
> > drivers/gpu/drm/i915/intel_sprite.c | 5 +++--
> > 4 files changed, 9 insertions(+), 25 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c
> > index 304f86a..5905a9d 100644
> > --- a/drivers/gpu/drm/i915/i915_irq.c
> > +++ b/drivers/gpu/drm/i915/i915_irq.c
> > @@ -1724,19 +1724,6 @@ static void gen6_rps_irq_handler(struct drm_i915_private *dev_priv, u32 pm_iir)
> > }
> > }
> >
> > -static bool intel_pipe_handle_vblank(struct drm_device *dev, enum pipe pipe)
> > -{
> > - struct intel_crtc *crtc;
> > -
> > - if (!drm_handle_vblank(dev, pipe))
> > - return false;
> > -
> > - crtc = to_intel_crtc(intel_get_crtc_for_pipe(dev, pipe));
> > - wake_up(&crtc->vbl_wait);
> > -
> > - return true;
> > -}
>
> Can we keep this bare wrapper? It is quite useful for hooking in vblank
> checks - i.e. saves me having to reinrtoduce it.
Just smash them into drm_handle_vblank?
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-05-22 16:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 15:39 [PATCH 1/2] drm: Add drm_crtc_vblank_waitqueue() ville.syrjala
2014-05-22 15:39 ` [PATCH 2/2] drm/i915: Kill intel_crtc->vbl_wait ville.syrjala
2014-05-22 15:49 ` Chris Wilson
2014-05-22 16:00 ` [PATCH v2 " ville.syrjala
2014-07-25 21:10 ` Daniel Vetter
2014-05-22 16:05 ` Daniel Vetter [this message]
2014-05-22 19:30 ` [Intel-gfx] [PATCH " Chris Wilson
2014-05-22 20:21 ` Daniel Vetter
2014-05-22 16:06 ` [Intel-gfx] [PATCH 1/2] drm: Add drm_crtc_vblank_waitqueue() Daniel Vetter
2014-05-22 16:36 ` [PATCH v2 " ville.syrjala
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=20140522160534.GV14357@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.intel.com \
/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