[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200907252204.44875.rjw@sisk.pl>
Date: Sat, 25 Jul 2009 22:04:44 +0200
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: Arnaud Faucher <arnaud.faucher@...il.com>,
linux-kernel@...r.kernel.org,
Carlos Corbacho <carlos@...angeworlds.co.uk>,
pm list <linux-pm@...ts.linux-foundation.org>,
Alan Stern <stern@...land.harvard.edu>
Subject: Re: [PATCH 1/1] acer-wmi: switch driver to dev_pm_ops
On Saturday 25 July 2009, Dmitry Torokhov wrote:
> Hi Arnaud,
>
> On Sat, Jul 25, 2009 at 09:04:51AM -0400, Arnaud Faucher wrote:
> > Gets rid of the following warning:
> > Platform driver 'acer-wmi' needs updating - please use dev_pm_ops
> >
>
> Have you tested it with Suspend to disk? You are [potentially] breaking
> it since the new suspend and resume methods are not used by it, it calls
> freeze() and thaw() instead.
>
> Rafael,
>
> I wonder if PM core should automatically use suspend()/resume() in place of
> freeze()/thaw() when the latter pair is missing.
Well, in fact it often is not necessary to do .thaw() at all, because the
state of the device doesn't change in .freeze(). Also, PCI drivers should
not need .thaw(), unless they manipulate the standard PM registers of the
device themselves.
That said, if .suspend() is defined, then most probably .freeze() is necessary
as well. Also, if .resume() is defined, .restore() is most probably necessary
and it should be safe to use .suspend() as .freeze() and .resume() as
.restore().
OTOH, it's really easy to point .restore() to the same routine as .resume()
etc., so I'm not sure.
Best,
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