public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Sivakumar Thulasimani <sivakumar.thulasimani@intel.com>
Cc: jani.nikula@intel.com, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: storm detection documentation update
Date: Wed, 8 Jul 2015 17:20:59 +0200	[thread overview]
Message-ID: <20150708152059.GR7568@phenom.ffwll.local> (raw)
In-Reply-To: <559D2476.9010003@intel.com>

On Wed, Jul 08, 2015 at 06:54:06PM +0530, Sivakumar Thulasimani wrote:
> 
> 
> On 7/7/2015 5:01 PM, Daniel Vetter wrote:
> >On Tue, Jul 07, 2015 at 04:10:49PM +0530, Sivakumar Thulasimani wrote:
> >>From: "Thulasimani,Sivakumar" <sivakumar.thulasimani@intel.com>
> >>
> >>Update the hotplug documentation to explain that hotplug storm
> >>is not expected for Display port panels and hence is not handled
> >>in current code.
> >>
> >>Signed-off-by: Sivakumar Thulasimani <sivakumar.thulasimani@intel.com>
> >>---
> >>  drivers/gpu/drm/i915/intel_hotplug.c |    4 ++++
> >>  1 file changed, 4 insertions(+)
> >>
> >>diff --git a/drivers/gpu/drm/i915/intel_hotplug.c b/drivers/gpu/drm/i915/intel_hotplug.c
> >>index bac91a1..7dc5e6a 100644
> >>--- a/drivers/gpu/drm/i915/intel_hotplug.c
> >>+++ b/drivers/gpu/drm/i915/intel_hotplug.c
> >>@@ -66,6 +66,10 @@
> >>   * while before being re-enabled. The intention is to mitigate issues raising
> >>   * from broken hardware triggering massive amounts of interrupts and grinding
> >>   * the system to a halt.
> >>+ *
> >>+ * Hotplug interrupt storm is not expected on Display port panel, hence the
> >>+ * current code only handles disabling and later enabling of HPD interrupts
> >>+ * for HDMI panels through the storm handling set of functions.
> >This isn't accurate, we handle storms on everything _but_ DP (tv, vga,
> >sdvo, ...). I'd go with
> >
> >  * Hotplug interrupt storm is not expected on Display port panel, hence the
> >  * current code doesn't handle irq reenabling when a DP sink is connected
> >  * and the hpd is handled by the DP callbacks. But on DP+ ports
> >  * storms are still handled correctly in all other cases (e.g. due to HDMI
> >  * sinks).
> >
> >Could still be improved I think.
> >
> >-Daniel
> >
> Sorry i don't get the "DP+" reference here. By DP+, do you mean dongles ?
> passive dongles will report them selves as HDMI to respective detect
> routines
> active dongles will be still treated as DP hence not handling HPD will apply
> to any
> display connected through active dongle as well.

DP+ is DP with support for HDMI with level shifter cables (i.e. all the
ports on intel chips). I just wanted to make it clear that storm handling
doesn't work if we have a confirmed DP sink on the port, but will work in
any other cases (nothing or HDMI sink or DVI or whatever connected). Like
I said some room for improvement ;-)
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-07-08 15:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-07 10:40 [PATCH] drm/i915: storm detection documentation update Sivakumar Thulasimani
2015-07-07 11:31 ` Daniel Vetter
2015-07-08 13:24   ` Sivakumar Thulasimani
2015-07-08 15:20     ` Daniel Vetter [this message]
2015-07-09 12:52       ` Sivakumar Thulasimani
2015-07-09 16:19         ` Daniel Vetter
2015-07-11  1:17 ` shuang.he
  -- strict thread matches above, loose matches on Subject: below --
2015-07-10  7:00 Sivakumar Thulasimani
2015-07-11 11:32 ` shuang.he
2015-07-13  9:22 ` Daniel Vetter

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=20150708152059.GR7568@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=sivakumar.thulasimani@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox