From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Fix PCH PLL assertions to not assume CRTC:PLL relationship
Date: Tue, 22 May 2012 21:01:00 +0200 [thread overview]
Message-ID: <20120522190100.GF4629@phenom.ffwll.local> (raw)
In-Reply-To: <1337533850-5669-1-git-send-email-chris@chris-wilson.co.uk>
On Sun, May 20, 2012 at 06:10:50PM +0100, Chris Wilson wrote:
> The existing assertions were written under the assumption that we wanted
> to test the related PLL to a CRTC. With the split of PLL into a
> separately managed entity which may be shared amongst CRTCs, we need to
> pass in both the CRTC and the PLL to the assertion routine.
> Occassionally, this means passing NULL for the CRTC as we wish to check
> the status of the PLL irrespective of the current CRTC.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
Picked up for -fixes, thanks for the patch.
-Daniel
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
prev parent reply other threads:[~2012-05-22 18:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-20 17:10 [PATCH] drm/i915: Fix PCH PLL assertions to not assume CRTC:PLL relationship Chris Wilson
2012-05-22 19:01 ` Daniel Vetter [this message]
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=20120522190100.GF4629@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=chris@chris-wilson.co.uk \
--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