public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915: Ignore long hpds on eDP ports
Date: Fri, 17 Oct 2014 12:00:53 +0300	[thread overview]
Message-ID: <20141017090053.GP4284@intel.com> (raw)
In-Reply-To: <87d29rm66l.fsf@intel.com>

On Fri, Oct 17, 2014 at 11:49:54AM +0300, Jani Nikula wrote:
> On Thu, 16 Oct 2014, ville.syrjala@linux.intel.com wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > Turning vdd on/off can generate a long hpd pulse on eDP ports. In order
> > to handle hpd we would need to turn on vdd to perform aux transfers.
> > This would lead to an endless cycle of
> > "vdd off -> long hpd -> vdd on -> detect -> vdd off -> ..."
> >
> > So ignore long hpd pulses on eDP ports. eDP panels should be physically
> > tied to the machine anyway so they should not actually disappear and
> > thus don't need long hpd handling. Short hpds are still needed for link
> > re-train and whatnot so we can't just turn off the hpd interrupt
> > entirely for eDP ports. Perhaps we could turn it off whenever the panel
> > is disabled, but just ignoring the long hpd seems sufficient.
> 
> Did you test this with my short vs. long hpd fix applied?

Yes. Well, with my own version of it :)

Now someone should go and implement HPD support for port A.

> 
> In any case, makes sense,
> 
> Reviewed-by: Jani Nikula <jani.nikula@intel.com>
> 
> 
> 
> 
> 
> >
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > ---
> >  drivers/gpu/drm/i915/intel_dp.c | 12 ++++++++++++
> >  1 file changed, 12 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
> > index f07f02c..4455009 100644
> > --- a/drivers/gpu/drm/i915/intel_dp.c
> > +++ b/drivers/gpu/drm/i915/intel_dp.c
> > @@ -4611,6 +4611,18 @@ intel_dp_hpd_pulse(struct intel_digital_port *intel_dig_port, bool long_hpd)
> >  	if (intel_dig_port->base.type != INTEL_OUTPUT_EDP)
> >  		intel_dig_port->base.type = INTEL_OUTPUT_DISPLAYPORT;
> >  
> > +	if (long_hpd && intel_dig_port->base.type == INTEL_OUTPUT_EDP) {
> > +		/*
> > +		 * vdd off can generate a long pulse on eDP which
> > +		 * would require vdd on to handle it, and thus we
> > +		 * would end up in an endless cycle of
> > +		 * "vdd off -> long hpd -> vdd on -> detect -> vdd off -> ..."
> > +		 */
> > +		DRM_DEBUG_KMS("ignoring long hpd on eDP port %c\n",
> > +			      port_name(intel_dig_port->port));
> > +		return false;
> > +	}
> > +
> >  	DRM_DEBUG_KMS("got hpd irq on port %c - %s\n",
> >  		      port_name(intel_dig_port->port),
> >  		      long_hpd ? "long" : "short");
> > -- 
> > 2.0.4
> >
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/intel-gfx
> 
> -- 
> Jani Nikula, Intel Open Source Technology Center

-- 
Ville Syrjälä
Intel OTC

  reply	other threads:[~2014-10-17  9:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-16 17:46 [PATCH 1/2] drm/i915: Do a dummy DPCD read before the actual read ville.syrjala
2014-10-16 17:46 ` [PATCH 2/2] drm/i915: Ignore long hpds on eDP ports ville.syrjala
2014-10-16 19:38   ` Todd Previte
2014-10-17  8:43     ` Ville Syrjälä
2014-10-17 16:08       ` Todd Previte
2014-10-21 16:00         ` Daniel Vetter
2014-10-22  1:22           ` Dave Airlie
2014-10-22  7:39           ` Ville Syrjälä
2014-10-22 13:42           ` Jani Nikula
2014-10-17  3:37   ` Dave Airlie
2014-10-17  8:49   ` Jani Nikula
2014-10-17  9:00     ` Ville Syrjälä [this message]
2014-10-16 19:39 ` [PATCH 1/2] drm/i915: Do a dummy DPCD read before the actual read Todd Previte
2014-10-17  9:06   ` Ville Syrjälä
2014-10-17 16:13     ` Todd Previte
2014-10-21 15:57   ` Daniel Vetter
2014-10-17  8:43 ` Jani Nikula
2014-10-17  8:59   ` Ville Syrjälä
2014-10-17 16:38     ` Todd Previte
2014-10-17 16:10   ` Todd Previte

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=20141017090053.GP4284@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@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