From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 01/17] drm/i915: Clear pipestat consistently
Date: Fri, 30 Jun 2017 14:59:35 +0300 [thread overview]
Message-ID: <20170630115935.GU12629@intel.com> (raw)
In-Reply-To: <149882291305.25960.4335867619661505010@mail.alporthouse.com>
On Fri, Jun 30, 2017 at 12:41:53PM +0100, Chris Wilson wrote:
> Quoting Ville Syrjälä (2017-06-30 12:34:15)
> > On Thu, Jun 22, 2017 at 01:39:47PM +0100, Chris Wilson wrote:
> > > Quoting ville.syrjala@linux.intel.com (2017-06-22 12:55:39)
> > > > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > >
> > > > We have a lot of different ways of clearing the PIPESTAT registers.
> > > > Let's unify it all into one function. There's no magic in PIPESTAT
> > > > that would require any of the double clearing and whatnot that
> > > > some of the code tries to do. All we can really do is clear the status
> > > > bits and disable the enable bits. There is no way to mask anything
> > > > so as soon as another event happens the status bit will become set
> > > > again, and trying to clear them twice or something can't protect
> > > > against that.
> > > >
> > > > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > > ---
> > > > drivers/gpu/drm/i915/i915_irq.c | 67 ++++++++++++++++++-----------------------
> > > > 1 file changed, 30 insertions(+), 37 deletions(-)
> > > >
> > > > diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c
> > > > index b1c7d1a04612..6daaf47482d4 100644
> > > > --- a/drivers/gpu/drm/i915/i915_irq.c
> > > > +++ b/drivers/gpu/drm/i915/i915_irq.c
> > > > @@ -1732,6 +1732,19 @@ static bool intel_pipe_handle_vblank(struct drm_i915_private *dev_priv,
> > > > return ret;
> > > > }
> > > >
> > > > +static void i9xx_pipestat_irq_reset(struct drm_i915_private *dev_priv)
> > > > +{
> > > > + enum pipe pipe;
> > > > +
> > > > + for_each_pipe(dev_priv, pipe) {
> > > > + I915_WRITE(PIPESTAT(pipe),
> > > > + PIPESTAT_INT_STATUS_MASK |
> > > > + PIPE_FIFO_UNDERRUN_STATUS);
> > >
> > > Hmm, is this change for i915/i965 significant? Maybe explain it away in
> > > the changelog?
> >
> > Sorry missed your question. Which change are we concerned about here
> > specifically?
>
> We didn't set PIPESTAT_INT_STATUS_MASK | PIPE_FIFO_UNDERRUN_STATUS
> previously afaics.
Ah. Those are the sticky status bits, so the earlier
I915_WRITE(PIPESTAT, I915_READ(PIPESTAT)) did the same thing
effectively.
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-06-30 11:59 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 11:55 [PATCH 00/17] drm/i915: Redo old gmch irq handling ville.syrjala
2017-06-22 11:55 ` [PATCH 01/17] drm/i915: Clear pipestat consistently ville.syrjala
2017-06-22 12:39 ` Chris Wilson
2017-06-30 11:34 ` Ville Syrjälä
2017-06-30 11:41 ` Chris Wilson
2017-06-30 11:59 ` Ville Syrjälä [this message]
2017-06-22 11:55 ` [PATCH 02/17] drm/i915: s/GEN3/GEN5/ ville.syrjala
2017-06-22 12:40 ` Chris Wilson
2017-06-26 7:06 ` Maarten Lankhorst
2017-06-22 11:55 ` [PATCH 03/17] drm/i915: Use GEN3_IRQ_RESET/INIT on gen3/4 ville.syrjala
2017-06-22 11:55 ` [PATCH 04/17] drm/i915: Introduce GEN2_IRQ_RESET/INIT ville.syrjala
2017-06-22 12:41 ` Chris Wilson
2017-06-22 11:55 ` [PATCH 05/17] drm/i915: Setup EMR first on all gen2-4 ville.syrjala
2017-06-22 12:42 ` Chris Wilson
2017-06-22 11:55 ` [PATCH 06/17] drm/i915: Eliminate PORT_HOTPLUG_EN setup from gen3/4 irq_postinstall ville.syrjala
2017-06-22 12:42 ` Chris Wilson
2017-06-22 11:55 ` [PATCH 07/17] drm/i915: Unify the appearance of gen3/4 irq_postistall hooks ville.syrjala
2017-06-22 12:43 ` Chris Wilson
2017-06-22 11:55 ` [PATCH 08/17] drm/i915: Remove NULL dev_priv checks from irq_uninstall ville.syrjala
2017-06-22 12:43 ` Chris Wilson
2017-06-22 11:55 ` [PATCH 09/17] drm/i915: Mask everything in ring HWSTAM on gen6+ in ringbuffer mode ville.syrjala
2017-06-22 11:55 ` [PATCH 10/17] drm/i915: Gen3 HWSTAM is actually 32 bits ville.syrjala
2017-06-22 12:45 ` Chris Wilson
2017-06-22 11:55 ` [PATCH 11/17] drm/i915: Clean up the HWSTAM mess ville.syrjala
2017-06-22 12:14 ` Chris Wilson
2017-06-22 11:55 ` [PATCH 12/17] drm/i915: Remove duplicated irq_preinstall/uninstall hooks ville.syrjala
2017-06-22 12:46 ` Chris Wilson
2017-06-22 11:55 ` [PATCH 13/17] drm/i915: Consolidatte intel_check_page_flip() into intel_pipe_handle_vblank() ville.syrjala
2017-06-22 12:48 ` Chris Wilson
2017-06-22 11:55 ` [PATCH 14/17] drm/i915: Move the gen2-4 page flip handling code around ville.syrjala
2017-06-22 12:49 ` Chris Wilson
2017-06-22 11:55 ` [PATCH 15/17] drm/i915: Simplify the gen2-4 flip_mask handling ville.syrjala
2017-06-22 12:51 ` Chris Wilson
2017-06-22 11:55 ` [PATCH 16/17] drm/i915: Extract PIPESTAT irq handling into separate functions ville.syrjala
2017-06-22 12:55 ` Chris Wilson
2017-06-22 11:55 ` [PATCH 17/17] drm/i915: Rewrite GMCH irq handlers to follow the VLV/CHV pattern ville.syrjala
2017-06-22 13:00 ` Chris Wilson
2017-06-22 13:10 ` Ville Syrjälä
2017-06-22 12:00 ` [PATCH 00/17] drm/i915: Redo old gmch irq handling Ville Syrjälä
2017-06-22 12:15 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-06-22 13:02 ` [PATCH 00/17] " Chris Wilson
2017-06-22 13:12 ` Ville Syrjälä
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=20170630115935.GU12629@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--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;
as well as URLs for NNTP newsgroup(s).