Attachment 71917 Details for Bug 53926 – Probe for the EDID using GPIO as a fallback

[patch] Probe for the EDID using GPIO as a fallback

0001-drm-i915-Try-to-get-the-EDID-using-bit-banging-if-GM.patch (text/plain), 1.26 KB, created by Chris Wilson on 2012-12-21 10:13:34 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Chris Wilson

Created: 2012-12-21 10:13:34 UTC

Size: 1.26 KB

patch

obsolete

>From 4ff81b8da582ab00c03ffc67d278ef390ad36f98 Mon Sep 17 00:00:00 2001
>From: Chris Wilson <chris@chris-wilson.co.uk>
>Date: Fri, 21 Dec 2012 10:06:55 +0000
>Subject: [PATCH] drm/i915: Try to get the EDID using bit-banging if GMBUS
> fails
>
>As a single-shot probe as to whether the EDID exists at all, we can
>double-check using GPIO.
>
>References: https://bugs.freedesktop.org/show_bug.cgi?id=53926
>Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>---
> drivers/gpu/drm/i915/intel_lvds.c |    6 ++++++
> 1 file changed, 6 insertions(+)
>
>diff --git a/drivers/gpu/drm/i915/intel_lvds.c b/drivers/gpu/drm/i915/intel_lvds.c
>index e1c6145..b12ea27 100644
>--- a/drivers/gpu/drm/i915/intel_lvds.c
>+++ b/drivers/gpu/drm/i915/intel_lvds.c
>@@ -1173,6 +1173,12 @@ bool intel_lvds_init(struct drm_device *dev)
> 	 * preferred mode is the right one.
> 	 */
> 	edid = drm_get_edid(connector, intel_gmbus_get_adapter(dev_priv, pin));
>+	if (!edid && !intel_gmbus_is_forced_bit(i2c)) {
>+		DRM_DEBUG_KMS("LVDS GMBUS EDID read failed, retry using GPIO bit-banging\n");
>+		intel_gmbus_force_bit(i2c, true);
>+		edid = drm_get_edid(connector, i2c);
>+		intel_gmbus_force_bit(i2c, false);
>+	}
> 	if (edid) {
> 		if (drm_add_edid_modes(connector, edid)) {
> 			drm_mode_connector_update_edid_property(connector,
>-- 
>1.7.10.4
>

Actions: View | Splinter Review

Attachments on bug 53926: 65947 | 65993 | 65994 | 65995 | 66054 | 66055 | 66134 | 71385 | 71540 | 71912 | 71917 | 72707 | 72708 | 72710 | 72711 | 72938

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.