Re: What PM should be and do (Was Re: Solving suspend-level confusion)
From: Qric?= Brunet (ebrunet_at_quatramaran.ens.fr)
Date: 08/07/04
- Previous message: Josh Radel: "elevator abstraction, anticipatory I/O backported to 2.4?"
- In reply to: Nigel Cunningham: "Re: What PM should be and do (Was Re: Solving suspend-level confusion)"
- Next in thread: Pavel Machek: "Re: What PM should be and do (Was Re: Solving suspend-level confusion)"
- Reply: Pavel Machek: "Re: What PM should be and do (Was Re: Solving suspend-level confusion)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: linux-kernel@vger.kernel.org Date: Sat, 7 Aug 2004 02:08:24 +0200
Dans ens.mailing-lists.linux-kernel, vous avez écrit :
>> > - support for telling what class of device a driver is handling (I'm
>> > particularly interested in keeping the keyboard, screen and storage
>> > devices alive while suspending).
>>
>> You can see that info today from userspace by looking in
>> /sys/class/input, /sys/class/graphics, and /sys/block
It is a minor point, but as many people are working on swsuspend right
now, I thought I'd mentionned it. It seems (as of 2.6.8.rc1) that the
screen is not shut down or put in a low power state when suspending to
disk.
I guess that for 99.5 % of the population, it is not an issue as the
monitor is usually plugged in the power supply of the computer and
power is cut when the computer shuts down. My monitor, however, is
directly plugged in the mains outlet and, after a suspend to disk, it
displays indefinitely an information box stating that it has no video
signal coming in.
The X server knows how to shutdown (DPMS) the screen afer some
inactivity, so I guess the kernel could do that while suspending. And it
would be very nice if it would. But I believe there is no device
driver handling the monitor, so I don't know where to do it.
Éric Brunet
-
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/
- Previous message: Josh Radel: "elevator abstraction, anticipatory I/O backported to 2.4?"
- In reply to: Nigel Cunningham: "Re: What PM should be and do (Was Re: Solving suspend-level confusion)"
- Next in thread: Pavel Machek: "Re: What PM should be and do (Was Re: Solving suspend-level confusion)"
- Reply: Pavel Machek: "Re: What PM should be and do (Was Re: Solving suspend-level confusion)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|