public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>
To: "ville.syrjala@linux.intel.com" <ville.syrjala@linux.intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 1/4] drm/i915: Avoid EBUSY retry on intel_dp_aux_ch.
Date: Wed, 21 Oct 2015 14:24:23 +0000	[thread overview]
Message-ID: <1445437586.24860.97.camel@intel.com> (raw)
In-Reply-To: <20151021091942.GX26517@intel.com>

On Wed, 2015-10-21 at 12:19 +0300, Ville Syrjälä wrote:
> On Wed, Oct 21, 2015 at 10:28:51AM -0700, Rodrigo Vivi wrote:
> > EBUSY retries are already in place at drm level.
> > We don't need to replicate the job here.
> > 
> > Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > ---
> >  drivers/gpu/drm/i915/intel_dp.c | 20 ++------------------
> >  1 file changed, 2 insertions(+), 18 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/i915/intel_dp.c 
> > b/drivers/gpu/drm/i915/intel_dp.c
> > index 09bdd94..d054129 100644
> > --- a/drivers/gpu/drm/i915/intel_dp.c
> > +++ b/drivers/gpu/drm/i915/intel_dp.c
> > @@ -818,24 +818,8 @@ intel_dp_aux_ch(struct intel_dp *intel_dp,
> >  
> >  	intel_aux_display_runtime_get(dev_priv);
> >  
> > -	/* Try to wait for any previous AUX channel activity */
> > -	for (try = 0; try < 3; try++) {
> > -		status = I915_READ_NOTRACE(ch_ctl);
> > -		if ((status & DP_AUX_CH_CTL_SEND_BUSY) == 0)
> > -			break;
> > -		msleep(1);
> 
> The dp helper doesn't sleep at all between the retries, so dropping 
> the
> sleep from here may change the behaviour.

hm indeed... what about 
+ msleep(1);
+ ret = -EBUSY
+ goto out;
?
> 
> > -	}
> > -
> > -	if (try == 3) {
> > -		static u32 last_status = -1;
> > -		const u32 status = I915_READ(ch_ctl);
> > -
> > -		if (status != last_status) {
> > -			WARN(1, "dp_aux_ch not started status 
> > 0x%08x\n",
> > -			     status);
> > -			last_status = status;
> > -		}
> > -
> > +	status = I915_READ_NOTRACE(ch_ctl);
> > +	if ((status & DP_AUX_CH_CTL_SEND_BUSY) != 0) {
> >  		ret = -EBUSY;
> >  		goto out;
> >  	}
> > -- 
> > 2.4.3
> > 
> > _______________________________________________
> > 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-10-21 14:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-21 17:28 [PATCH 0/4] Organize aux retries Rodrigo Vivi
2015-10-21 17:28 ` [PATCH 1/4] drm/i915: Avoid EBUSY retry on intel_dp_aux_ch Rodrigo Vivi
2015-10-21  9:19   ` Ville Syrjälä
2015-10-21 14:24     ` Vivi, Rodrigo [this message]
2015-10-21 18:01       ` Thulasimani, Sivakumar
2015-10-21 19:55         ` Vivi, Rodrigo
2015-10-21 17:28 ` [PATCH 2/4] drm/i915: Remove remaining retries from intel_dp_aux_ch Rodrigo Vivi
2015-10-21 17:28 ` [PATCH 3/4] drm/i915: Fix random aux transactions failures Rodrigo Vivi
2015-10-21  7:18   ` Daniel Vetter
2015-10-21  7:23     ` Daniel Vetter
2015-10-21 18:17       ` Thulasimani, Sivakumar
2015-10-21 19:57         ` Vivi, Rodrigo
2015-10-21 17:28 ` [PATCH 4/4] drm/i915: Kill intel_dp_dpcd_read_wake Rodrigo Vivi
2015-10-21  9:23   ` Ville Syrjälä
2015-10-21 14:31     ` Vivi, Rodrigo
2015-10-21 14:34       ` 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=1445437586.24860.97.camel@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ville.syrjala@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