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>,
	"jani.nikula@linux.intel.com" <jani.nikula@linux.intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Retry on every aux read.
Date: Tue, 20 Oct 2015 17:45:29 +0000	[thread overview]
Message-ID: <1445363249.24860.54.camel@intel.com> (raw)
In-Reply-To: <1445355480.24860.41.camel@intel.com>

On Tue, 2015-10-20 at 08:38 -0700, Rodrigo Vivi wrote:
> On Tue, 2015-10-20 at 09:39 +0200, Daniel Vetter wrote:
> > On Tue, Oct 20, 2015 at 10:02:21AM +0300, Jani Nikula wrote:
> > > On Tue, 20 Oct 2015, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> > > > We have an inconsistency on our code on using 
> > > > intel_dp_dpcd_read_wake with
> > > > retries and when using drm_dp_dpcd_read helper without retry.
> > > 
> > > We're supposed to do the retries when the sink may be in a power 
> > > down
> > > state. We're not very good at tracking that, and we've cargo 
> > > culted 
> > > the
> > > retry variants all over the place without thinking. This is why 
> > > we're
> > > inconsistent.
> > > 
> > > > Since the retries help in many cases let's be consistent and be 
> > > > on
> > > > the safe side retrying on every aux read, including i2c ones.
> > > 
> > > Please let's not add superfluous retries at different levels of 
> > > the
> > > stack just to be safe. It's like a variant of the C programmer's
> > > disease.
> 
> I'm not the one who is adding, but just being consistent on our side. 
> 
> > > 
> > > If the retries really help [citation needed] we need to figure 
> > > out 
> > > what
> > > we're doing wrong and where, and preferrably fix this at the DP 
> > > helper
> > > level for all drivers, if possible.
> 
> Yes, I'm sorry, I forgot to copy the citation from the first patch in
> this thread that mentions this fix sink crc for Skylake... and also 
> for
> some Broadwells what made me to remind about this patch....
> 
> > 
> > Yeah, same comment as I've done last time around. If we need this, 
> > we 
> > need
> > to do this in core dp helpers.
> 
> If it is "superfluous" and "disease" to make the consistence in our
> driver I can't imagine the words that I'm going to hear if I try to
> touch other drivers...
> 
> To see if we should actually do this in our level or on the drm level 
> I
> was trying to understand where does:
> " Sinks are *supposed* to come up within 1ms from an off state, but
> we're also- * supposed to retry 3 times per the spec."
> 
> But I couldn't find anything in Vesa spec that tells that neither on
> BSPec... at BSpec for some platforms I found the 3 times retry for 
> aux
> ctl programming what we do already...

Besides, I noticed on drm level we have 32 times retry already but when
aux return -EBUSY... 

So I wonder if it would be acceptable to retry for all errors not only
for -EBUSY or if we should find out when to return EBUSY propperly on
our aux transfer...

> 
> So, yeah, I'm not convinced that we should through this to another
> level... So it is either this or the first one that fix the sink crc
> case individually and let sink crc reliable...
> 
> > -Daniel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-10-20 17:45 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
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 [this message]
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=1445363249.24860.54.camel@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=daniel@ffwll.ch \
    --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