Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: fixup assert_pipe to take the pipe A quirk into account
Date: Tue, 24 Jan 2012 10:24:21 -0800	[thread overview]
Message-ID: <20120124102421.14965c4f@jbarnes-desktop> (raw)
In-Reply-To: <20120123194027.GC5998@phenom.ffwll.local>


[-- Attachment #1.1: Type: text/plain, Size: 1073 bytes --]

On Mon, 23 Jan 2012 20:40:27 +0100
Daniel Vetter <daniel@ffwll.ch> wrote:

> On Sat, Jan 21, 2012 at 08:36:38PM -0800, Keith Packard wrote:
> > On Sun, 22 Jan 2012 01:36:48 +0100, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> > > This was completely spamming dmesg on my i855gm.
> > 
> > This comes from intel_disable_pll, which wants to turn the pll off, but
> > if the pipe is still active, it won't be able to. This seems bad to me.
> 
> I honestly can't reconcile your comment with the code&patch. Afaics
> - the pll disable code checks for the pipe a quirk and does an early exit
>   before mucking around with the hw and calling assert_pipe.
> - assert_pipe only does a WARN and the patch only changes whether we hit
>   that WARN. All reg reads/writes should be unchanged.
> - the backtrace I'm seeing goes through crtc_disable.

Ah ok so it's coming from the new pipe disabled check Chris added.
Patch looks fine... and reminds me to be puzzled about the pipe a force
quirk on 855. :)

-- 
Jesse Barnes, Intel Open Source Technology Center

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2012-01-24 18:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-22  0:36 [PATCH] drm/i915: fixup assert_pipe to take the pipe A quirk into account Daniel Vetter
2012-01-22  4:36 ` Keith Packard
2012-01-23 19:40   ` Daniel Vetter
2012-01-24 18:24     ` Jesse Barnes [this message]
2012-01-24 18:49       ` 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=20120124102421.14965c4f@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.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