From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 2/2] drm/i915: fixup load-detect on enabled, but not active pipe
Date: Sun, 22 Apr 2012 11:17:48 +0200 [thread overview]
Message-ID: <20120422091748.GC4723@phenom.ffwll.local> (raw)
In-Reply-To: <1334951122_7754@CP5-2952>
On Fri, Apr 20, 2012 at 08:44:59PM +0100, Chris Wilson wrote:
> On Fri, 20 Apr 2012 21:03:36 +0200, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> > Somehow we have a fast-path that tries to avoid going through
> > the load-detect code when the encode already has a crtc associated.
> > But this fails horribly when the crtc is off. The load detect pipe
> > itself manages this case well (and also does not forget to restore the
> > dpms state), so just rip out this special case.
> >
> > The issue seems to go back all the way to the commit that originally
> > introduced load-detection on the vga output:
> >
> > commit e4a5d54f924ea5ce2913d9d0687d034004816465
> > Author: Ma Ling <ling.ma@intel.com>
> > Date: Tue May 26 11:31:00 2009 +0800
> >
> > drm/i915: Add support for VGA load detection (pre-945).
> >
> > Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=43020
> > Reported-by: Jean Delvare <khali@linux-fr.org>
> > Signed-Off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>
> I'm happy that intel_get_load_detect_pipe() does the right thing if the
> connector is already active (so that we don't blank an active display
> when checking for disconnections). I was worried that this meant we had
> a deeper bug with our connection state, but as Daniel made me realise it
> is that the "fast path" is lacking the enable.
>
> For this and subsuquent TV fix, begone foul code,
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
I've picked up this one for -fixes ant the other two for -next, thanks for
the review.
-Daniel
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
next prev parent reply other threads:[~2012-04-22 9:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 19:03 [PATCH 1/2] drm/i915: time out of load detect busy-waits Daniel Vetter
2012-04-20 19:03 ` [PATCH 2/2] drm/i915: fixup load-detect on enabled, but not active pipe Daniel Vetter
2012-04-20 19:44 ` Chris Wilson
2012-04-22 9:17 ` Daniel Vetter [this message]
2012-04-20 19:25 ` [PATCH] drm/fixup: fixup tv load-detect on enabled but not active crtc Daniel Vetter
2012-04-20 19:42 ` [PATCH 1/2] drm/i915: time out of load detect busy-waits Chris Wilson
2012-04-25 17:14 ` Chris Wilson
2012-04-25 19:26 ` Daniel Vetter
2012-04-28 21:00 ` Chris Wilson
2012-05-01 17:26 ` 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=20120422091748.GC4723@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox