From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Daniel@freedesktop.org
Subject: Re: [PATCH] drm/i915: IBX has a fixed pch pll to pch pipe mapping
Date: Mon, 21 May 2012 07:48:40 -0700 [thread overview]
Message-ID: <20120521074840.77fabd5b@jbarnes-desktop> (raw)
In-Reply-To: <20120520185119.GF5145@phenom.ffwll.local>
On Sun, 20 May 2012 20:51:19 +0200
Daniel Vetter <daniel@ffwll.ch> wrote:
> On Sun, May 20, 2012 at 08:00:25PM +0200, Daniel Vetter wrote:
> > This should fix breakage introduced in
> >
> > commit ee7b9f93fd96a72e5d09e2b44024c11880873c6b
> > Author: Jesse Barnes <jbarnes@virtuousgeek.org>
> > Date: Fri Apr 20 17:11:53 2012 +0100
> >
> > drm/i915: manage PCH PLLs separately from pipes
> >
> > v2: Add a DRM_DEBUG_KMS message to explain why a given pll was
> > selected, suggested by Chris Wilson.
> >
> > v3: Actually run git add.
> >
> > Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
> > Cc: Chris Wilson <chris@chris-wilson.co.uk>
> > Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=49712
> > Signed-Off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>
> Ok, I've merged this one to dinq. I could reproduce a failure on my ilk
> by forcing the crtc which looked very much like what QA is hitting, and
> this patch does indeed fix that.
Great, thanks Daniel.
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2012-05-21 14:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-20 16:55 [PATCH] drm/i915: IBX has a fixed pch pll to pch pipe mapping Daniel Vetter
2012-05-20 17:16 ` Chris Wilson
2012-05-20 17:36 ` Daniel Vetter
2012-05-20 18:00 ` Daniel Vetter
2012-05-20 18:51 ` Daniel Vetter
2012-05-21 14:48 ` Jesse Barnes [this message]
2012-05-22 19:06 ` 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=20120521074840.77fabd5b@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=Daniel@freedesktop.org \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@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