From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Use enum pipe for PCH transcoders
Date: Tue, 10 Oct 2017 18:43:12 +0300 [thread overview]
Message-ID: <20171010154312.GR10981@intel.com> (raw)
In-Reply-To: <20171010140042.b4nsjresp4kirogm@phenom.ffwll.local>
On Tue, Oct 10, 2017 at 04:00:42PM +0200, Daniel Vetter wrote:
> On Tue, Oct 10, 2017 at 03:55:56PM +0300, Ville Syrjala wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > One more place where we've failed to switch to enum pipe when talking
> > about PCH transcoders.
> >
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Pushed to dinq. Thanks for the review.
>
> > ---
> > drivers/gpu/drm/i915/intel_display.c | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> > index 45d6e57fbe89..57d886cece16 100644
> > --- a/drivers/gpu/drm/i915/intel_display.c
> > +++ b/drivers/gpu/drm/i915/intel_display.c
> > @@ -14758,10 +14758,10 @@ static struct intel_connector *intel_encoder_find_connector(struct intel_encoder
> > }
> >
> > static bool has_pch_trancoder(struct drm_i915_private *dev_priv,
> > - enum transcoder pch_transcoder)
> > + enum pipe pch_transcoder)
> > {
> > return HAS_PCH_IBX(dev_priv) || HAS_PCH_CPT(dev_priv) ||
> > - (HAS_PCH_LPT_H(dev_priv) && pch_transcoder == TRANSCODER_A);
> > + (HAS_PCH_LPT_H(dev_priv) && pch_transcoder == PIPE_A);
> > }
> >
> > static void intel_sanitize_crtc(struct intel_crtc *crtc,
> > @@ -14844,7 +14844,7 @@ static void intel_sanitize_crtc(struct intel_crtc *crtc,
> > * PCH transcoders B and C would prevent enabling the south
> > * error interrupt (see cpt_can_enable_serr_int()).
> > */
> > - if (has_pch_trancoder(dev_priv, (enum transcoder)crtc->pipe))
> > + if (has_pch_trancoder(dev_priv, crtc->pipe))
> > crtc->pch_fifo_underrun_disabled = true;
> > }
> > }
> > --
> > 2.13.6
> >
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> http://blog.ffwll.ch
--
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-10-10 15:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 12:55 [PATCH] drm/i915: Use enum pipe for PCH transcoders Ville Syrjala
2017-10-10 13:28 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-10-10 14:00 ` [PATCH] " Daniel Vetter
2017-10-10 15:43 ` Ville Syrjälä [this message]
2017-10-10 17:38 ` ✗ Fi.CI.IGT: warning for " Patchwork
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=20171010154312.GR10981@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=daniel@ffwll.ch \
--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