From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Initialize panel_pipe to INVALID_PIPE
Date: Wed, 23 May 2018 18:21:38 +0300 [thread overview]
Message-ID: <20180523152138.GN23723@intel.com> (raw)
In-Reply-To: <87wovujthv.fsf@intel.com>
On Wed, May 23, 2018 at 06:12:44PM +0300, Jani Nikula wrote:
> On Wed, 23 May 2018, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > We can always figure out which pipe is affected by the panel power
> > sequencer lockout mechanism. So no need for the pipe A fallback
> > anymore. The only case we may have to worry about is an invalid
> > port select in the power sequencer, but INVALID_PIPE is just fine
> > in that case. We'll get the WARN about the bogus pps port select
> > anyway.
> >
> > Cc: Jani Nikula <jani.nikula@intel.com>
> > Suggested-by: Jani Nikula <jani.nikula@intel.com>
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Reviewed-by: Jani Nikula <jani.nikula@intel.com>
>
> Hmm, do the same for cpt_dp_port_selected() fail path? Or keep that as
> pipe A to cause mismatch and error?
I think we can change it back to INVALID_PIPE too. I had some idea why
I'd have to make it a valid pipe even if the port is disabled, but I
guess that was just nonsense. Or at least I can't see why anything
would fail badly with INVALID_PIPE now.
>
>
> > ---
> > drivers/gpu/drm/i915/intel_display.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> > index 1afd70fdbd85..25285939f987 100644
> > --- a/drivers/gpu/drm/i915/intel_display.c
> > +++ b/drivers/gpu/drm/i915/intel_display.c
> > @@ -1202,7 +1202,7 @@ void assert_panel_unlocked(struct drm_i915_private *dev_priv, enum pipe pipe)
> > {
> > i915_reg_t pp_reg;
> > u32 val;
> > - enum pipe panel_pipe = PIPE_A;
> > + enum pipe panel_pipe = INVALID_PIPE;
> > bool locked = true;
> >
> > if (WARN_ON(HAS_DDI(dev_priv)))
>
> --
> Jani Nikula, Intel Open Source Graphics Center
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-05-23 15:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 14:57 [PATCH] drm/i915: Initialize panel_pipe to INVALID_PIPE Ville Syrjala
2018-05-23 15:12 ` Jani Nikula
2018-05-23 15:21 ` Ville Syrjälä [this message]
2018-05-23 16:46 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-05-23 19:02 ` ✓ Fi.CI.IGT: " 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=20180523152138.GN23723@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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