From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dominik Brodowski Subject: Re: [linux-pm] [patch] pm: fix runtime powermanagement's /sys interface Date: Thu, 5 Jan 2006 23:13:34 +0100 Message-ID: <20060105221334.GA925@isilmar.linta.de> References: <20051227213439.GA1884@elf.ucw.cz> <20051227220533.GA1914@elf.ucw.cz> <20060104213405.GC1761@elf.ucw.cz> <20060105215528.GF2095@elf.ucw.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20060105215528.GF2095@elf.ucw.cz> Sender: linux-kernel-owner@vger.kernel.org To: Pavel Machek Cc: Patrick Mochel , Andrew Morton , Linux-pm mailing list , kernel list List-Id: linux-pm@vger.kernel.org On Thu, Jan 05, 2006 at 10:55:29PM +0100, Pavel Machek wrote: > > I have a firewire controller in a desktop system, and a ATI Radeon in a > > T42 that support D1 and D2.. > > Ok, now we have a concrete example. So Radeon supports D1. But putting > radeon into D1 means you probably want to blank your screen and turn > the backlight off; that takes *long* time anyway. So you can simply > put your radeon into D3 and save a bit more power. Using your logic, you never want to put your CPU into C2 power-saving state instead of C3 or C4. Which is ridiculous. There are technical reasons why you want to put devices into different power-saving states. E.g. wakeup latency, ability to receive wakeup signals, snooping and so on. In addition, your patch breaks pcmcia / pcmciautils which already uses numbers (which I already had to change from "3" to "2" before...). Dominik