[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1207038460.10388.214.camel@pasglop>
Date: Tue, 01 Apr 2008 19:27:40 +1100
From: Benjamin Herrenschmidt <benh@...nel.crashing.org>
To: Nigel Cunningham <ncunningham@...a.org.au>
Cc: "Rafael J. Wysocki" <rjw@...k.pl>,
pm list <linux-pm@...ts.linux-foundation.org>,
ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
Alan Stern <stern@...land.harvard.edu>,
Greg KH <greg@...ah.com>, Len Brown <lenb@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
Alexey Starikovskiy <astarikovskiy@...e.de>,
David Brownell <david-b@...bell.net>,
Pavel Machek <pavel@....cz>, Oliver Neukum <oliver@...kum.org>
Subject: Re: [RFC][PATCH] PM: Introduce new top level suspend and
hibernation callbacks (rev. 6)
On Tue, 2008-04-01 at 19:15 +1100, Nigel Cunningham wrote:
> > + * However, drivers may NOT assume anything about the availability of the
> > + * user space at that time and it is not correct to request firmware from
> > + * within @prepare() (it's too late to do that).
>
> That doesn't sound good. It would be good to be able to get drivers to
> request firmware early in the process.
Agreed. Prepare() should still allow request_firmware and full userspace
communication / helper usage.
> > + * @complete: Undo the changes made by @prepare(). This method is executed for
> > + * all kinds of resume transitions, following one of the resume callbacks:
> > + * @resume(), @thaw(), @restore(). Also called if the state transition
> > + * fails before the driver's suspend callback (@suspend(), @freeze(),
> > + * @poweroff()) can be executed (e.g. if the suspend callback fails for one
> > + * of the other devices that the PM core has unsucessfully attempted to
Ben.
--
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