All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/hdmi: Fix weak connector detection
Date: Fri, 1 Apr 2016 18:46:02 +0300	[thread overview]
Message-ID: <20160401154602.GU4329@intel.com> (raw)
In-Reply-To: <CAAEAJfDx5Ur+5NM+knRL0Ds4n5_aJW0DghWyekGUgbX28jUDzg@mail.gmail.com>

On Fri, Apr 01, 2016 at 12:38:11PM -0300, Ezequiel Garcia wrote:
> El abr. 1, 2016 11:47 AM, "Ville Syrjälä" <ville.syrjala@linux.intel.com>
> escribió:
> >
> > On Thu, Mar 31, 2016 at 05:55:03PM -0300, Ezequiel Garcia wrote:
> > > Currently, our implementation of drm_connector_funcs.detect is
> > > based on getting a valid EDID.
> > >
> > > This requirement makes the driver fail to detect connected
> > > connectors in case of EDID corruption, which prevents from falling
> > > back to modes provided by builtin or user-provided EDIDs.
> >
> > So why are you getting corrupted EDIDs?
> >
> 
> Does it matter?

Yes. We should fix the real cause (if possible) instead of adding
more duct tape.

> 
> > >
> > > Let's fix this by improving the detection, with a DDC probe,
> > > if the current EDID-based detection failed.
> > >
> > > Note that a better way of dealing with this could calling
> > > drm_probe_ddc in drm_connector_funcs.detect, and do the
> > > EDID full reading and parsing in drm_connector_helper_funcs.get_modes,
> > > when it's actually needed.
> > >
> > > However, this would be more invasive and thus more error-prone.
> > > The current commit is an attempt to get some uninvasive fix,
> > > and allow for easier backporting.
> > >
> > > Signed-off-by: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
> > > ---
> > >  drivers/gpu/drm/i915/intel_hdmi.c | 14 ++++++++++++++
> > >  1 file changed, 14 insertions(+)
> > >
> > > diff --git a/drivers/gpu/drm/i915/intel_hdmi.c
> b/drivers/gpu/drm/i915/intel_hdmi.c
> > > index a0d8daed2470..c079206e6681 100644
> > > --- a/drivers/gpu/drm/i915/intel_hdmi.c
> > > +++ b/drivers/gpu/drm/i915/intel_hdmi.c
> > > @@ -1428,6 +1428,20 @@ intel_hdmi_detect(struct drm_connector
> *connector, bool force)
> > >       } else
> > >               status = connector_status_disconnected;
> > >
> > > +     /*
> > > +      * The above call to intel_hdmi_set_edid() checked for a valid
> EDID.
> > > +      * However, the EDID can get corrupted for several reasons,
> resulting
> > > +      * in a disconnected status despite the connector being connected.
> > > +      * Hence, let's try one more time, by only probing the DDC.
> > > +      *
> > > +      * This allows the DRM core to fallback to builtin or
> user-provided
> > > +      * EDID firmware, e.g. in drm_helper_probe_single_connector_modes.
> > > +      */
> > > +     if (status == connector_status_disconnected)
> > > +             if (drm_probe_ddc(intel_gmbus_get_adapter(dev_priv,
> > > +                                             intel_hdmi->ddc_bus)))
> > > +                     status = connector_status_connected;
> > > +
> > >       intel_display_power_put(dev_priv, POWER_DOMAIN_GMBUS);
> > >
> > >       return status;
> > > --
> > > 2.7.0
> > >
> > > _______________________________________________
> > > dri-devel mailing list
> > > dri-devel@lists.freedesktop.org
> > > https://lists.freedesktop.org/mailman/listinfo/dri-devel
> >
> > --
> > Ville Syrjälä
> > Intel OTC

-- 
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-04-01 15:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-31 20:55 [PATCH] drm/i915/hdmi: Fix weak connector detection Ezequiel Garcia
2016-04-01  9:07 ` ✓ Fi.CI.BAT: success for " Patchwork
2016-04-01 14:47 ` [PATCH] " Ville Syrjälä
2016-04-01 15:38   ` Ezequiel Garcia
2016-04-01 15:46     ` Ville Syrjälä [this message]
2016-04-01 19:50       ` Ezequiel Garcia
2016-04-05 14:54         ` Ezequiel Garcia
2016-04-14  5:11           ` Ezequiel Garcia

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=20160401154602.GU4329@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=ezequiel@vanguardiasur.com.ar \
    --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.