On Wed, 23 May 2012 08:59:07 +0200, Zdenek Kabelac <zdenek.kabelac at gmail.com> wrote: > 2012/5/23 Sean Paul <seanpaul at 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
