public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Manasi Navare <manasi.d.navare@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: [PATCH 2/2] drm/i915/edp: Increase the T12 delay quirk to 1300ms
Date: Tue,  3 Oct 2017 16:37:25 -0700	[thread overview]
Message-ID: <1507073845-13420-2-git-send-email-manasi.d.navare@intel.com> (raw)
In-Reply-To: <1507073845-13420-1-git-send-email-manasi.d.navare@intel.com>

For this specific PCI device, the eDP panel requires a higher
panel power cycle delay of 1300ms where the minimum spec
requirement of panel power cycle delay is 500ms.
This fix in combination with correct timestamp at which we get the
panel power off time fixes the dP AUX CH timeouts seen on various IGT tests.

Fixes: c99a259b4b5192ba ("drm/i915/edp: Add a T12 panel delay quirk to fix
DP AUX CH timeouts")
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=101144,
https://bugs.freedesktop.org/show_bug.cgi?id=101518
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Ville Syrjala <ville.syrjala@linux.intel.com>
Signed-off-by: Manasi Navare <manasi.d.navare@intel.com>
---
 drivers/gpu/drm/i915/intel_dp.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
index 0fd41cd..ca48bce 100644
--- a/drivers/gpu/drm/i915/intel_dp.c
+++ b/drivers/gpu/drm/i915/intel_dp.c
@@ -5286,7 +5286,7 @@ intel_dp_init_panel_power_sequencer(struct drm_device *dev,
 	 * seems sufficient to avoid this problem.
 	 */
 	if (dev_priv->quirks & QUIRK_INCREASE_T12_DELAY) {
-		vbt.t11_t12 = max_t(u16, vbt.t11_t12, 900 * 10);
+		vbt.t11_t12 = max_t(u16, vbt.t11_t12, 1300 * 10);
 		DRM_DEBUG_KMS("Increasing T12 panel delay as per the quirk to %d\n",
 			      vbt.t11_t12);
 	}
-- 
2.1.4

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-10-03 23:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-03 23:37 [PATCH 1/2] drm/i915/edp: Get the Panel Power Off timestamp after panel is off Manasi Navare
2017-10-03 23:37 ` Manasi Navare [this message]
2017-10-04 15:13   ` [PATCH 2/2] drm/i915/edp: Increase the T12 delay quirk to 1300ms Daniel Vetter
2017-10-03 23:57 ` ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915/edp: Get the Panel Power Off timestamp after panel is off Patchwork
2017-10-04  2:17 ` ✓ Fi.CI.IGT: " Patchwork
2017-10-04  8:10 ` ✓ Fi.CI.BAT: " Patchwork
2017-10-04 11:06   ` Arkadiusz Hiler
2017-10-04  8:46 ` [PATCH 1/2] " Jani Nikula
2017-10-04 10:18 ` ✓ Fi.CI.IGT: success for series starting with [1/2] " Patchwork
2017-10-04 15:11 ` [PATCH 1/2] " Daniel Vetter
2017-10-04 16:48 ` [PATCH v2 " Manasi Navare
2017-10-05  6:54   ` Jani Nikula
2017-10-05 19:03     ` Manasi Navare
2017-10-04 17:39 ` ✗ Fi.CI.BAT: warning for series starting with [v2,1/2] drm/i915/edp: Get the Panel Power Off timestamp after panel is off (rev2) Patchwork
2017-10-04 18:43 ` ✗ Fi.CI.BAT: failure " Patchwork
2017-10-04 19:28 ` ✓ Fi.CI.BAT: success " Patchwork
2017-10-04 21:15 ` ✗ Fi.CI.IGT: failure " Patchwork

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=1507073845-13420-2-git-send-email-manasi.d.navare@intel.com \
    --to=manasi.d.navare@intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --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