Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751633Ab1BDLQW (ORCPT ); Fri, 4 Feb 2011 06:16:22 -0500 Received: from cantor.suse.de ([195.135.220.2]:50080 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751082Ab1BDLQU (ORCPT ); Fri, 4 Feb 2011 06:16:20 -0500 Date: Fri, 04 Feb 2011 12:16:17 +0100 Message-ID: From: Takashi Iwai To: Linus Torvalds Cc: Keith Packard , Dave Airlie , Carlos Mafra , Dave Airlie , "Rafael J. Wysocki" , Linux Kernel Mailing List , Maciej Rutecki , Florian Mickler , Andrew Morton , Kernel Testers List , Network Development , Linux ACPI , Linux PM List , Linux SCSI List , Linux Wireless List , DRI Subject: Re: 2.6.38-rc3-git1: Reported regressions 2.6.36 -> 2.6.37 In-Reply-To: References: <201102032009.17100.rjw@sisk.pl> User-Agent: Wanderlust/2.15.6 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.7 Emacs/23.2 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1394 Lines: 36 At Thu, 3 Feb 2011 17:11:14 -0800, Linus Torvalds wrote: > > On Thu, Feb 3, 2011 at 5:05 PM, Keith Packard wrote: > > > > The goal is to make it so that when you *do* set a mode, DPMS gets set > > to ON (as the monitor will actually be "on" at that point). Here's a > > patch which does the DPMS_ON precisely when setting a mode. > > Ok, patch looks sane, but it does leave me with the "what about the > 'fb_changed' case?" question. Is that case basically guaranteed to not > change any existing dpms state? > > > (note, this patch compiles, but is otherwise only lightly tested). > > Carlos? Takashi? Ignore my crazy patch, try this one instead. Does it > fix things for you? Yes, the patch fixes the issue with xrandr off and on. However, another issue I reported in that bugzilla still remains: namely, DPMS value returned via ioctl or obtained via sysfs is inconsistent with the actually applied value. The reason is that there are two places keeping the current DPMS values, in connector and in crtc device properties. A similar fix like my patch in the bugzilla would be still needed, I guess. thanks, Takashi -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/