[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200804012216.08318.rjw@sisk.pl>
Date: Tue, 1 Apr 2008 22:16:07 +0200
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: benh@...nel.crashing.org
Cc: Nigel Cunningham <ncunningham@...a.org.au>,
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 Tuesday, 1 of April 2008, Benjamin Herrenschmidt wrote:
>
> 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.
This documents the current state which is that we have the freezer and we have
drivers that rely on it.
I can remove the comment, but then someone will invent ->prepare() relying
on the availability of the user space at this point and that won't work.
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