From: Mika Kahola <mika.kahola@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH v5 0/3] drm/i915: Disable link training optimization if DP config has changed
Date: Mon, 4 Jan 2016 13:21:21 +0200 [thread overview]
Message-ID: <1451906484-4659-1-git-send-email-mika.kahola@intel.com> (raw)
These three patches are fixes for DP link trainging failures and flickering issues
reported by
Mika Kahola (3):
drm/i915: Disable fast link training if DP config changes
drm/i915: Check DP no aux transaction bit on link training
drm/i915: DP channel EQ check for use of DP link training optimization
drivers/gpu/drm/i915/intel_dp.c | 8 +++++++-
drivers/gpu/drm/i915/intel_dp_link_training.c | 22 ++++++++++++++++++++++
drivers/gpu/drm/i915/intel_drv.h | 1 +
3 files changed, 30 insertions(+), 1 deletion(-)
--
1.9.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2016-01-04 11:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 11:21 Mika Kahola [this message]
2016-01-04 11:21 ` [PATCH v5 1/3] drm/i915: Disable fast link training if DP config changes Mika Kahola
2016-01-04 16:42 ` Ville Syrjälä
2016-01-05 12:13 ` Mika Kahola
2016-01-04 11:21 ` [PATCH v5 2/3] drm/i915: Check DP no aux transaction bit on link training Mika Kahola
2016-01-04 11:21 ` [PATCH v5 3/3] drm/i915: DP channel EQ check for use of DP link training optimization Mika Kahola
2016-01-04 16:44 ` Ville Syrjälä
2016-01-04 16:53 ` Ville Syrjälä
2016-01-05 11:08 ` Mika Kahola
2016-01-11 18:28 ` Ville Syrjälä
2016-01-05 9:37 ` Mika Kahola
2016-01-04 11:49 ` ✗ warning: Fi.CI.BAT Patchwork
2016-01-04 12:11 ` [PATCH v5 0/3] drm/i915: Disable link training optimization if DP config has changed Maarten Lankhorst
2016-01-04 12:16 ` Mika Kahola
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=1451906484-4659-1-git-send-email-mika.kahola@intel.com \
--to=mika.kahola@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.