[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200807011735.05618.rjw@sisk.pl>
Date: Tue, 1 Jul 2008 17:35:04 +0200
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Uwe Kleine-König <Uwe.Kleine-Koenig@...i.com>
Cc: Andrew Morton <akpm@...l.org>,
David Brownell <dbrownell@...rs.sourceforge.net>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Pavel Machek <pavel@....cz>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: A minimally power-aware driver treats all messages as SUSPEND?
On Tuesday, 1 of July 2008, Uwe Kleine-König wrote:
> Hello Rafael,
>
> Rafael J. Wysocki wrote:
> > On Tuesday, 1 of July 2008, Uwe Kleine-König wrote:
> > > include/linux/pm.h claims:
> > >
> > > A minimally power-aware driver treats all messages as SUSPEND
> > > [...].
> > >
> > > This was introduced in commit 82bb67f2 by David Brownell. At this time
> > > PM_EVENT_HIBERNATE didn't exist. This was added in 3a2d5b70 by Rafael
> > > J. Wysocki without updating the above sentence. I think a minimally
> > > power-aware driver should treat all messages as HIBERNATE, shouldn't it?
> >
> > No, I don't think so. In the majority of cases, SUSPEND is equivalent to the
> > combination of FREEZE and HIBERNATE.
> I didn't get that. I thought SUSPEND is suspend-to-ram and HIBERNATE is
> suspend-to-disk, so HIBERNATE is the "deeper sleep".
> With that I might have to do less on SUSPEND because some state might be
> preserved after the machine comes up again.
>
> > Still, this is going to change anyway with the introduction of the new
> > suspend/hibernation callbacks that are scheduled for 2.6.27.
> in next?
Yes.
Thanks,
Rafael
--
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