From: Chris Wilson <chris@chris-wilson.co.uk>
To: Zdenek Kabelac <zdenek.kabelac@gmail.com>,
Sean Paul <seanpaul@chromium.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
intel-gfx@lists.freedesktop.org, daniel@ffwll.ch,
jbarnes@virtuousgeek.org
Subject: Re: Regression on GMA965 - display seems to have slow jump changes in brightness
Date: Wed, 23 May 2012 09:59:23 +0100 [thread overview]
Message-ID: <1337763574_198483@CP5-2952> (raw)
In-Reply-To: <CAJJYPdnoEu6QGuACUn0e10TG3XQQsaM5AqfbhqRbH6pwUQoVwg@mail.gmail.com>
On Wed, 23 May 2012 08:59:07 +0200, Zdenek Kabelac <zdenek.kabelac@gmail.com> wrote:
> 2012/5/23 Sean Paul <seanpaul@chromium.org>:
> > Hmm, seems like your display doesn't like to be downclocked, or rather
> > you don't like it to be downclocked :) The reason this patch triggered
> > it is because it does a better job of finding a compatible clock. You
> > can disable lvds downclocking on the kernel command line by setting
> > i915.lvds_downclock=0
> >
>
> Hmm I've been using i915.lvds_downclock=1 on grub command line, and
> haven't noticed any visible problems with 3.3 kernel. So I'd rather
> ask if the problematic patch isn't doing downclocking in a wrong way?
> Or maybe detection that downclocking is not supported properly is not
> correct now ?
It is more likely that we did not detect a downclock mode before now and
so this is the first time that is being used in anger. (There should be
some telltales in drm.debug dmesg) If you are really, really brave you
can try http://cgit.freedesktop.org/~ickle/linux-2.6/log/?h=fastboot
which only triggers the downclock on a vblank.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
prev parent reply other threads:[~2012-05-23 8:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 12:08 Regression on GMA965 - display seems to have slow jump changes in brightness Zdenek Kabelac
2012-05-22 12:30 ` Daniel Vetter
2012-05-22 14:36 ` Zdenek Kabelac
2012-05-22 14:44 ` Daniel Vetter
2012-05-22 14:55 ` Zdenek Kabelac
2012-05-22 22:15 ` Zdenek Kabelac
2012-05-22 22:21 ` Sean Paul
2012-05-23 6:49 ` Daniel Vetter
2012-05-23 6:59 ` Zdenek Kabelac
2012-05-23 7:07 ` Daniel Vetter
2012-05-23 9:11 ` Daniel Vetter
2012-05-23 11:48 ` Zdenek Kabelac
2012-05-23 12:03 ` [Intel-gfx] " Daniel Vetter
2012-05-24 14:21 ` Zdenek Kabelac
2012-05-24 14:41 ` Daniel Vetter
2012-05-23 8:59 ` Chris Wilson [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=1337763574_198483@CP5-2952 \
--to=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seanpaul@chromium.org \
--cc=zdenek.kabelac@gmail.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