[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <094CE21F-9AB6-4DD5-AF89-3A72116887E6@mac.com>
Date: Sun, 29 Jul 2007 22:47:57 -0400
From: Kyle Moffett <mrmacman_g4@....com>
To: Richard Hughes <hughsient@...il.com>
Cc: "Rafael J. Wysocki" <rjw@...k.pl>, Adrian Bunk <bunk@...sta.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Len Brown <lenb@...nel.org>, david@...g.hm,
Andrew Morton <akpm@...ux-foundation.org>,
linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org,
Pavel Machek <pavel@....cz>,
Stefan Richter <stefanr@...6.in-berlin.de>,
Nigel Cunningham <nigel@...el.suspend2.net>,
pm list <linux-pm@...ts.linux-foundation.org>
Subject: Re: [PATCH 2/2] Introduce CONFIG_SUSPEND
On Jul 29, 2007, at 17:30:40, Richard Hughes wrote:
> So are you guys using:
>
> "standby" = idle state, ~0.5 seconds
> "suspend" = sleep to ram, ~10 seconds
> "hibernate" = sleep to disk, ~30 seconds
>
> If so - you rock. This is the common nomenclature I've been pushing
> for
> a few months now in GNOME, KDE and general userspace. I've written
> up a
> spec here:
> http://cvs.gnome.org/viewcvs/*checkout*/gnome-power-manager/docs/
> sleep-names.html
Well, those times don't quite work for my PowerBook. If we fixed
suspend-to-RAM to reinitialize devices in parallel then it would
easily hit 0.5 second transition times, but even now it's only at
most 2 seconds. Also once in a while I'll be too hasty plugging my
USB devices and manage to hardlock one of the USB busses, but that's
an isolated USB driver suspend issue.
And it's certainly not called "standby", because the box can
literally remain asleep for 7 days on a full charge, versus about 5
hours when just idle with wireless, backlight, and HDD off.
Cheers,
Kyle Moffett
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists