[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <200804031648.59630.jbarnes@virtuousgeek.org>
Date: Thu, 3 Apr 2008 16:48:59 -0700
From: Jesse Barnes <jbarnes@...tuousgeek.org>
To: benh@...nel.crashing.org
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>,
Nigel Cunningham <ncunningham@...a.org.au>,
Dave Airlie <airlied@...ux.ie>
Subject: Re: [RFC][PATCH 1/3] use new pm_ops in DRM drivers
On Thursday, April 03, 2008 2:47 pm Benjamin Herrenschmidt wrote:
> On Thu, 2008-04-03 at 11:50 -0700, Jesse Barnes wrote:
> > +static struct pm_ops i915_pm_ops = {
> > + .prepare = NULL, /* DRM core should prevent any new ioctls? */
> > + .complete = NULL, /* required to re-enable DRM client requests
> > */
>
> The DRM core could definitely provide generic prepare & complete that
> sync'up with user space, making sure the command streams stop etc...
Yeah, that's what I had in mind. I'll have to think a little harder about it
though, I think there may be some driver specific stuff required here as
well, which would mean a driver routine that calls into a core routine (both
of which still need to be written :).
Jesse
--
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