From: Daniel Vetter <daniel@ffwll.ch>
To: "Chris Wilson" <chris@chris-wilson.co.uk>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Intel Graphics Development" <intel-gfx@lists.freedesktop.org>,
"Meelis Roos" <mroos@ut.ee>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Subject: Re: [PATCH] drm/i915: preserve pipe A quirk in i9xx_set_pipeconf
Date: Tue, 24 Sep 2013 14:50:59 +0200 [thread overview]
Message-ID: <20130924125059.GS13668@phenom.ffwll.local> (raw)
In-Reply-To: <20130924120507.GF10644@nuc-i3427.alporthouse.com>
On Tue, Sep 24, 2013 at 01:05:07PM +0100, Chris Wilson wrote:
> On Tue, Sep 24, 2013 at 11:46:14AM +0200, Daniel Vetter wrote:
> > This regression has been introduced in
> >
> > commit 9f11a9e4e50006b615ba94722dfc33ced89664cf
> > Author: Daniel Vetter <daniel.vetter@ffwll.ch>
> > Date: Thu Jun 13 00:54:58 2013 +0200
> >
> > drm/i915: set up PIPECONF explicitly for i9xx/vlv platforms
> >
> > Ville brough up the idea that this is just the pipe A quirk gone
> > wrong.
> >
> > Note that after resume the bios might or might not have enabled pipe A
> > already. We have a bit of magic to make sure that on resume we set up
> > a decent mode for pipe A, but I fear if I just smash pipe A to always
> > on we'd enable it in a bogus state and hang the hw. Hence the
> > readback.
> >
> > v2: Clarify the logic a bit as suggested by Chris. Also amend the
> > commit message to clarify why we don't unconditionally enable the
> > pipe.
> >
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=66462
> > References: https://lkml.org/lkml/2013/8/26/238
> > Cc: Meelis Roos <mroos@ut.ee>
> > Cc: Chris Wilson <chris@chris-wilson.co.uk>
> > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
>
> would still prefer pipeconf |= PIPECONF_ENABLE though.
Yeah, makes sense. Fixed and applied, thanks for the review.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2013-09-24 12:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-22 18:51 [PATCH] drm/i915: preserve pipe A quirk in i9xx_set_pipeconf Daniel Vetter
2013-09-23 8:17 ` Ville Syrjälä
2013-09-23 8:37 ` Daniel Vetter
2013-09-23 9:55 ` Chris Wilson
2013-09-23 21:18 ` Meelis Roos
2013-09-23 21:19 ` Chris Wilson
2013-09-24 9:05 ` Daniel Vetter
2013-09-24 9:11 ` Chris Wilson
2013-09-23 12:06 ` Meelis Roos
2013-09-23 20:05 ` Meelis Roos
2013-09-23 20:11 ` Chris Wilson
2013-09-24 9:46 ` Daniel Vetter
2013-09-24 12:05 ` Chris Wilson
2013-09-24 12:50 ` Daniel Vetter [this message]
2013-09-23 15:15 ` Chris Wilson
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=20130924125059.GS13668@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mroos@ut.ee \
--cc=ville.syrjala@linux.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