public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com, consume.noise@gmail.com
Subject: [PATCH 0/2] drm/i915/dp: native aux defer retry timeout & retry limit
Date: Tue, 11 Feb 2014 11:52:03 +0200	[thread overview]
Message-ID: <cover.1392111874.git.jani.nikula@intel.com> (raw)

These should fix the hang in the bug referenced in patch 2/2. Based on
some links the actual error might be a firmware bug in the docking
station, but we shouldn't trust on DP sinks to not keep replying aux
defer indefinitely.

Even with the docking station's firmware fixed, this may not be enough
to actually get the output working. They are branch devices, possibly
MST devices, which we still suck at.

But hey, at least we won't freeze the system.

The retry timeout and limit are in line with Thierry's dp aux series
[1], so this should in fact ease the transition by catching any
regressions caused by this change up front.

BR,
Jani.

[1] http://mid.gmane.org/1390332263-11974-1-git-send-email-treding@nvidia.com


Jani Nikula (2):
  drm/i915/dp: increase native aux defer retry timeout
  drm/i915/dp: add native aux defer retry limit

 drivers/gpu/drm/i915/intel_dp.c |   19 +++++++++++++------
 1 file changed, 13 insertions(+), 6 deletions(-)

-- 
1.7.9.5

             reply	other threads:[~2014-02-11  9:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-11  9:52 Jani Nikula [this message]
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
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=cover.1392111874.git.jani.nikula@intel.com \
    --to=jani.nikula@intel.com \
    --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