From: "Kumar, Shobhit" <shobhit.kumar@linux.intel.com>
To: Gary Wang <gary.c.wang@intel.com>, intel-gfx@lists.freedesktop.org
Cc: Shobhit Kumar <shobhit.kumar@intel.com>,
drm-intel-fixes@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: increase the tries for HDMI hotplug live status checking
Date: Wed, 23 Dec 2015 17:04:29 +0530 [thread overview]
Message-ID: <567A86C5.2010004@linux.intel.com> (raw)
In-Reply-To: <1450858295-12804-1-git-send-email-gary.c.wang@intel.com>
On 12/23/2015 01:41 PM, Gary Wang wrote:
> The total delay of HDMI hotplug detecting with 30ms is sometimes not
> enoughtfor HDMI live status up with specific HDMI monitors in BSW platform.
>
> After doing experiments for following monitors, it needs 80ms at least
> for those worst cases.
>
> Lenovo L246 1xwA (4 failed, necessary hot-plug delay: 58/40/60/40ms)
> Philips HH2AP (9 failed, necessary hot-plug delay: 80/50/50/60/46/40/58/58/39ms)
> BENQ ET-0035-N (6 failed, necessary hot-plug delay: 60/50/50/80/80/40ms)
> DELL U2713HM (2 failed, necessary hot-plug delay: 58/59ms)
> HP HP-LP2475w (5 failed, necessary hot-plug delay: 70/50/40/60/40ms)
>
> It looks like 70-80 ms is BSW platform needs in some bad cases of the
> monitors at this end (8 times delay at most). Keep less than 100ms for
> HDCP pulse HPD low (with at least 100ms) to respond a plug out.
>
Tested-by: Shobhit Kumar <shobhit.kumar@intel.com>
Adding
Cc: drm-intel-fixes@lists.freedesktop.org
> Reviewed-by: Cooper Chiou <cooper.chiou@intel.com>
> Tested-by: Gary Wang <gary.c.wang@intel.com>
> Cc: Gavin Hindman <gavin.hindman@intel.com>
> Cc: Sonika Jindal <sonika.jindal@intel.com>
> Cc: Shashank Sharma <shashank.sharma@intel.com>
> Cc: Shobhit Kumar <shobhit.kumar@intel.com>
> Signed-off-by: Gary Wang <gary.c.wang@intel.com>
> ---
> drivers/gpu/drm/i915/intel_hdmi.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> mode change 100644 => 100755 drivers/gpu/drm/i915/intel_hdmi.c
>
> diff --git a/drivers/gpu/drm/i915/intel_hdmi.c b/drivers/gpu/drm/i915/intel_hdmi.c
> old mode 100644
> new mode 100755
> index 6214175..4a77639
> --- a/drivers/gpu/drm/i915/intel_hdmi.c
> +++ b/drivers/gpu/drm/i915/intel_hdmi.c
> @@ -1392,7 +1392,7 @@ intel_hdmi_detect(struct drm_connector *connector, bool force)
>
> intel_display_power_get(dev_priv, POWER_DOMAIN_GMBUS);
>
> - for (try = 0; !live_status && try < 4; try++) {
> + for (try = 0; !live_status && try < 9; try++) {
> if (try)
> msleep(10);
> live_status = intel_digital_port_connected(dev_priv,
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-12-23 11:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 8:11 [PATCH] drm/i915: increase the tries for HDMI hotplug live status checking Gary Wang
2015-12-23 8:30 ` Wang, Gary C
2015-12-23 8:49 ` ✗ failure: Fi.CI.BAT Patchwork
2015-12-23 11:34 ` Kumar, Shobhit [this message]
2015-12-25 11:58 ` [PATCH] drm/i915: increase the tries for HDMI hotplug live status checking Sharma, Shashank
2015-12-30 11:57 ` Jani Nikula
2015-12-30 17:47 ` Kumar, Shobhit
2016-01-04 2:00 ` Wang, Gary C
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=567A86C5.2010004@linux.intel.com \
--to=shobhit.kumar@linux.intel.com \
--cc=drm-intel-fixes@lists.freedesktop.org \
--cc=gary.c.wang@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=shobhit.kumar@intel.com \
/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.