public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>
To: "daniel@ffwll.ch" <daniel@ffwll.ch>
Cc: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"vivijim@rdvivi-budapest.jf.intel.com"
	<vivijim@rdvivi-budapest.jf.intel.com>
Subject: Re: [PATCH] drm/i915: Use dpcd read wake for sink crc calls.
Date: Wed, 26 Aug 2015 16:41:51 +0000	[thread overview]
Message-ID: <1440607384.3879.271.camel@intel.com> (raw)
In-Reply-To: <20150826090608.GN20434@phenom.ffwll.local>

On Wed, 2015-08-26 at 11:06 +0200, Daniel Vetter wrote:
> On Thu, Aug 20, 2015 at 04:12:00PM -0700, Rodrigo Vivi wrote:
> > From: Rodrigo Vivi <vivijim@rdvivi-budapest.jf.intel.com>
> > 
> > Let's use a native read with retry as suggested per spec to
> > fix Sink CRC on SKL when PSR is enabled.
> > 
> > With PSR enabled panel is probably taking more time to wake
> > and dpcd read is faling.
> > 
> > Cc: Sonika Jindal <sonika.jindal@intel.com>
> > Signed-off-by: Rodrigo Vivi <vivijim@rdvivi-budapest.jf.intel.com>
> 
> Seems like we should just move the trickery we do in our own version 
> into
> the dp helpers in the core if this is needed all over the place?

I've wondered this, but I thought there was a good reason to let this
trick separated.

> At least in i915 we use it everywhere and it doesn't seem actively 
> harmful
> really ... Maybe the only exception would be the i2c-over-dp_aux 
> code.

Why this would be the exception? Maybe this was the good reason?


> -Daniel
> > ---
> >  drivers/gpu/drm/i915/intel_dp.c | 15 +++++++++------
> >  1 file changed, 9 insertions(+), 6 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/i915/intel_dp.c 
> > b/drivers/gpu/drm/i915/intel_dp.c
> > index d32ce48..34f5e33 100644
> > --- a/drivers/gpu/drm/i915/intel_dp.c
> > +++ b/drivers/gpu/drm/i915/intel_dp.c
> > @@ -4037,7 +4037,8 @@ static int intel_dp_sink_crc_stop(struct 
> > intel_dp *intel_dp)
> >  	u8 buf;
> >  	int ret = 0;
> >  
> > -	if (drm_dp_dpcd_readb(&intel_dp->aux, DP_TEST_SINK, &buf) 
> > < 0) {
> > +	if (intel_dp_dpcd_read_wake(&intel_dp->aux, DP_TEST_SINK,
> > +				    &buf, 1) < 0) {
> >  		DRM_DEBUG_KMS("Sink CRC couldn't be stopped 
> > properly\n");
> >  		ret = -EIO;
> >  		goto out;
> > @@ -4069,7 +4070,8 @@ static int intel_dp_sink_crc_start(struct 
> > intel_dp *intel_dp)
> >  			return ret;
> >  	}
> >  
> > -	if (drm_dp_dpcd_readb(&intel_dp->aux, DP_TEST_SINK_MISC, 
> > &buf) < 0)
> > +	if (intel_dp_dpcd_read_wake(&intel_dp->aux, 
> > DP_TEST_SINK_MISC,
> > +				    &buf, 1) < 0)
> >  		return -EIO;
> >  
> >  	if (!(buf & DP_TEST_CRC_SUPPORTED))
> > @@ -4077,7 +4079,7 @@ static int intel_dp_sink_crc_start(struct 
> > intel_dp *intel_dp)
> >  
> >  	intel_dp->sink_crc.last_count = buf & DP_TEST_COUNT_MASK;
> >  
> > -	if (drm_dp_dpcd_readb(&intel_dp->aux, DP_TEST_SINK, &buf) 
> > < 0)
> > +	if (intel_dp_dpcd_read_wake(&intel_dp->aux, DP_TEST_SINK, 
> > &buf, 1) < 0)
> >  		return -EIO;
> >  
> >  	hsw_disable_ips(intel_crtc);
> > @@ -4109,8 +4111,8 @@ int intel_dp_sink_crc(struct intel_dp 
> > *intel_dp, u8 *crc)
> >  	do {
> >  		intel_wait_for_vblank(dev, intel_crtc->pipe);
> >  
> > -		if (drm_dp_dpcd_readb(&intel_dp->aux,
> > -				      DP_TEST_SINK_MISC, &buf) < 
> > 0) {
> > +		if (intel_dp_dpcd_read_wake(&intel_dp->aux,
> > +					    DP_TEST_SINK_MISC, 
> > &buf, 1) < 0) {
> >  			ret = -EIO;
> >  			goto stop;
> >  		}
> > @@ -4123,7 +4125,8 @@ int intel_dp_sink_crc(struct intel_dp 
> > *intel_dp, u8 *crc)
> >  		if (count == 0)
> >  			intel_dp->sink_crc.last_count = 0;
> >  
> > -		if (drm_dp_dpcd_read(&intel_dp->aux, 
> > DP_TEST_CRC_R_CR, crc, 6) < 0) {
> > +		if (intel_dp_dpcd_read_wake(&intel_dp->aux, 
> > DP_TEST_CRC_R_CR,
> > +					    crc, 6) < 0) {
> >  			ret = -EIO;
> >  			goto stop;
> >  		}
> > -- 
> > 2.1.0
> > 
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/intel-gfx
> 
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-08-26 16:41 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20 23:12 [PATCH] drm/i915: Use dpcd read wake for sink crc calls Rodrigo Vivi
2015-08-20 23:23 ` Rodrigo Vivi
2015-08-24  4:57   ` Jindal, Sonika
2015-08-24 19:54   ` Zanoni, Paulo R
2015-08-24 21:20     ` Vivi, Rodrigo
2015-10-21 18:31       ` Thulasimani, Sivakumar
2015-10-21 19:59         ` Vivi, Rodrigo
2015-10-21 20:14         ` Damien Lespiau
2015-10-22  3:26           ` Thulasimani, Sivakumar
2015-11-16 16:05             ` Rodrigo Vivi
2015-11-17 14:08               ` Daniel Vetter
2015-11-18 18:31                 ` Vivi, Rodrigo
2015-11-19  9:12                   ` Daniel Vetter
2015-08-26  9:06 ` Daniel Vetter
2015-08-26 16:41   ` Vivi, Rodrigo [this message]
2015-08-27  9:21     ` Daniel Vetter
2015-08-27 10:45       ` Jani Nikula
2015-10-19 23:08   ` [PATCH] drm/i915: Retry on every aux read Rodrigo Vivi
2015-10-20  7:02     ` Jani Nikula
2015-10-20  7:39       ` Daniel Vetter
2015-10-20 15:36         ` Vivi, Rodrigo
2015-10-20 17:45           ` Vivi, Rodrigo
2015-10-20 18:31             ` Daniel Vetter

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=1440607384.3879.271.camel@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=vivijim@rdvivi-budapest.jf.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