public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org, consume.noise@gmail.com
Subject: Re: [PATCH 1/2] drm/i915/dp: increase native aux defer retry timeout
Date: Tue, 11 Feb 2014 12:36:08 +0200	[thread overview]
Message-ID: <87mwhyym07.fsf@intel.com> (raw)
In-Reply-To: <20140211100033.GA11275@nuc-i3427.alporthouse.com>

On Tue, 11 Feb 2014, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Tue, Feb 11, 2014 at 11:52:04AM +0200, Jani Nikula wrote:
>> Give more slack to sink devices before retrying on native aux
>> defer. AFAICT the 100 us timeout was not based on the DP spec.
>
> If the issue is that there is an unknown amount of time that must be
> waited before the device is ready, should we not try increasing the
> sleep value on each iteration?
>
> If you were to do that, I would put patch 2 (which lgtm) first.

All of this code will change when we eventually move to the common DP
aux helpers. I'd like to get such fixes in the common code after it's
been merged. Diverging now makes the conversion harder.

I also thought this would be the better order bisect-wise. 2/2 first
might be unnecessarily strict, possibly creating a false culprit in
bisect for any other possible DP issues. Maybe that is a silly thing to
worry about.

BR,
Jani.


-- 
Jani Nikula, Intel Open Source Technology Center

  reply	other threads:[~2014-02-11 10:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-11  9:52 [PATCH 0/2] drm/i915/dp: native aux defer retry timeout & retry limit Jani Nikula
2014-02-11  9:52 ` [PATCH 1/2] drm/i915/dp: increase native aux defer retry timeout Jani Nikula
2014-02-11 10:01   ` Chris Wilson
2014-02-11 10:36     ` Jani Nikula [this message]
2014-02-11  9:52 ` [PATCH 2/2] drm/i915/dp: add native aux defer retry limit Jani Nikula
2014-02-11 14:17   ` Daniel Vetter
2014-02-13  8:45     ` Daniel Vetter
2014-02-13 14:17       ` Jani Nikula

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=87mwhyym07.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=consume.noise@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /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