From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [PATCH 0/4] drm/i915/dp: aux and dpcd fixes
Date: Fri, 20 Sep 2013 16:42:13 +0300 [thread overview]
Message-ID: <cover.1379684248.git.jani.nikula@intel.com> (raw)
I haven't received confirmation from various bug reporters whether these
actually fix any issues, but here goes anyway.
We may want to revisit patch 2/4 in a future patch, adding some
heuristic to increase delay with each retry, and maybe taking into
account i2c bit rate capabilities if reported in dpcd.
BR,
Jani.
Jani Nikula (4):
drm/i915/dp: retry i2c-over-aux seven times on AUX DEFER
drm/i915/dp: increase i2c-over-aux retry interval on AUX DEFER
drm/i915/dp: downstream port capabilities are not present in DPCD 1.0
drm/i915/dp: read DPCD PSR capability only on eDP
drivers/gpu/drm/i915/intel_dp.c | 52 +++++++++++++++++++++++++++++----------
1 file changed, 39 insertions(+), 13 deletions(-)
--
1.7.9.5
next reply other threads:[~2013-09-20 13:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-20 13:42 Jani Nikula [this message]
2013-09-20 13:42 ` [PATCH 1/4] drm/i915/dp: retry i2c-over-aux seven times on AUX DEFER Jani Nikula
2013-09-20 20:38 ` Todd Previte
2013-09-24 6:39 ` Jani Nikula
2013-09-27 11:51 ` Jani Nikula
2013-09-27 19:07 ` Todd Previte
2013-09-27 19:59 ` Daniel Vetter
2013-09-20 13:42 ` [PATCH 2/4] drm/i915/dp: increase i2c-over-aux retry interval " Jani Nikula
2013-09-20 20:56 ` Todd Previte
2013-09-20 21:53 ` Daniel Vetter
2013-09-20 13:42 ` [PATCH 3/4] drm/i915/dp: downstream port capabilities are not present in DPCD 1.0 Jani Nikula
2013-09-20 13:42 ` [PATCH 4/4] drm/i915/dp: read DPCD PSR capability only on eDP Jani Nikula
2013-09-20 20:50 ` Todd Previte
2013-09-20 20:57 ` Paulo Zanoni
2013-09-20 22:31 ` Todd Previte
2013-09-23 7:29 ` Daniel Vetter
2013-09-23 5:59 ` [PATCH 0/4] drm/i915/dp: aux and dpcd fixes Jani Nikula
2013-09-23 7:30 ` 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=cover.1379684248.git.jani.nikula@intel.com \
--to=jani.nikula@intel.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