Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8BIT
To: Rodrigo Vivi <rodrigo.vivi@intel.com>,
        =?utf-8?q?Stefan_Br=C3=BCns?= <stefan.bruens@rwth-aachen.de>
From: Chris Wilson <chris@chris-wilson.co.uk>
In-Reply-To: <20180102191218.53beopvnxsg2etmg@intel.com>
Cc: "David Airlie" <airlied@linux.ie>, intel-gfx@lists.freedesktop.org,
        linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
References: <a39f080b-81a5-4c93-b3f7-7cb0a58daca3@rwthex-w2-a.rwth-ad.de>
 <20180102191218.53beopvnxsg2etmg@intel.com>
Message-ID: <151492106622.21495.250228197580562391@mail.alporthouse.com>
User-Agent: alot/0.3.6
Subject: Re: [Intel-gfx] [PATCH v2] drm/i915: Try EDID bitbanging on HDMI after
 failed read
Date: Tue, 02 Jan 2018 19:24:26 +0000
Sender: linux-kernel-owner@vger.kernel.org

Quoting Rodrigo Vivi (2018-01-02 19:12:18)
> On Sun, Dec 31, 2017 at 10:34:54PM +0000, Stefan Brüns wrote:
> > +     edid = drm_get_edid(connector, i2c);
> > +
> > +     if (!edid && !intel_gmbus_is_forced_bit(i2c)) {
> > +             DRM_DEBUG_KMS("HDMI 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);
> > +     }
> 
> Approach seems fine for this case.
> I just wonder what would be the risks of forcing this bit and edid read when nothing is present on the other end?

Should be no more risky than using GMBUS as the bit-banging is the
underlying HW protocol; it should just be adding an extra delay to
the disconnected probe. Offset against the chance that it fixes
detection of borderline devices.

I would say that given the explanation above, the question is why not
apply it universally? (Bonus points for including the explanation as
comments.)
-Chris