From: Chris Wilson <chris@chris-wilson.co.uk>
To: Damien Lespiau <damien.lespiau@gmail.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/4] drm/i915/hdmi: Read the HPD status before trying to read the EDID
Date: Thu, 13 Dec 2012 08:40:40 +0000 [thread overview]
Message-ID: <6c3329$7ku15h@orsmga002.jf.intel.com> (raw)
In-Reply-To: <1355341841-4595-2-git-send-email-damien.lespiau@gmail.com>
On Wed, 12 Dec 2012 19:50:39 +0000, Damien Lespiau <damien.lespiau@gmail.com> wrote:
> From: Damien Lespiau <damien.lespiau@intel.com>
>
> If you unplug the hdmi connector slowly enough, the hotplug interrupt
> fires but then the kernel code tries to read the EDID and succeeds
> (because the connector is still half connected, the HPD pin is shorter
> than the others, and DDC works). Since EDID succeeds it thinks the
> monitor is still connected.
>
> To prevent that, read the live HPD status in the hotplug handler before
> trying to read the EDID.
>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=55372
> Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
> ---
> drivers/gpu/drm/i915/intel_display.c | 33 +++++++++++++++++++++++++++++++++
> drivers/gpu/drm/i915/intel_drv.h | 3 +++
> drivers/gpu/drm/i915/intel_hdmi.c | 10 ++++++++--
> 3 files changed, 44 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index 115bf62..117d9e6 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -994,6 +994,39 @@ void intel_wait_for_pipe_off(struct drm_device *dev, int pipe)
> }
> }
>
> +/*
> + * intel_ironlake_digital_port_connected - is the specified port connected?
> + * @dev_priv: i915 private structure
> + * @port: the port to test
> + *
> + * Returns true if @port is connected, false otherwise.
> + */
> +bool intel_ironlake_digital_port_connected(struct drm_i915_private *dev_priv,
> + struct intel_digital_port *port)
intel_ironlake_digital_port_connected() is a horrible bastard of a
naming scheme. ibx_digital_port_connected() please.
^intel_ -> applies to (nearly-)all display generations
^ilk_/ironlake_ -> applies to ironlake and maybe subsequent generations
In this case since we are PCH specific, using the PCH chipset
identifiers makes more sense.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-12-13 8:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 19:50 [PATCH 1/4] drm/i915: Cleanup SHOTPLUG_CTL status bits definitions Damien Lespiau
2012-12-12 19:50 ` [PATCH 2/4] drm/i915/hdmi: Read the HPD status before trying to read the EDID Damien Lespiau
2012-12-13 8:40 ` Chris Wilson [this message]
2012-12-13 11:11 ` Jani Nikula
2012-12-12 19:50 ` [PATCH 3/4] drm/i915/dp: Read the HPD status before trying to read the DPCD Damien Lespiau
2012-12-13 11:16 ` Jani Nikula
2012-12-12 19:50 ` [PATCH 4/4] drm/i915/dp: Don't log the DPCD if we are disconnected Damien Lespiau
2012-12-13 8:33 ` Jani Nikula
2012-12-13 8:39 ` [PATCH 1/4] drm/i915: Cleanup SHOTPLUG_CTL status bits definitions Jani Nikula
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='6c3329$7ku15h@orsmga002.jf.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=damien.lespiau@gmail.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.