From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: benh@kernel.crashing.org
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
pm list <linux-pm@lists.linux-foundation.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Alan Stern <stern@rowland.harvard.edu>, Greg KH <greg@kroah.com>,
Len Brown <lenb@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
Alexey Starikovskiy <astarikovskiy@suse.de>,
David Brownell <david-b@pacbell.net>, Pavel Machek <pavel@ucw.cz>,
Oliver Neukum <oliver@neukum.org>,
Nigel Cunningham <ncunningham@crca.org.au>,
Dave Airlie <airlied@linux.ie>
Subject: Re: [RFC][PATCH 1/3] use new pm_ops in DRM drivers
Date: Thu, 3 Apr 2008 16:48:59 -0700 [thread overview]
Message-ID: <200804031648.59630.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <1207259267.10388.334.camel@pasglop>
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
next prev parent reply other threads:[~2008-04-03 23:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 0:07 [RFC][PATCH 0/3] PM: Rework suspend and hibernation code for devices (rev. 4) Rafael J. Wysocki
2008-04-02 0:09 ` [RFC][PATCH 1/3] PM: Introduce new top level suspend and hibernation callbacks (rev. 7) Rafael J. Wysocki
2008-04-02 0:09 ` Rafael J. Wysocki
2008-04-02 0:09 ` Rafael J. Wysocki
2008-04-02 13:12 ` Pavel Machek
2008-04-02 13:12 ` Pavel Machek
2008-04-02 13:12 ` Pavel Machek
2008-04-03 18:50 ` [RFC][PATCH 1/3] use new pm_ops in DRM drivers Jesse Barnes
2008-04-03 18:50 ` Jesse Barnes
2008-04-03 21:23 ` Rafael J. Wysocki
2008-04-03 21:23 ` Rafael J. Wysocki
2008-04-03 21:41 ` Jesse Barnes
2008-04-03 21:41 ` Jesse Barnes
2008-04-03 21:23 ` Rafael J. Wysocki
2008-04-03 21:47 ` Benjamin Herrenschmidt
2008-04-03 21:47 ` Benjamin Herrenschmidt
2008-04-03 23:48 ` Jesse Barnes [this message]
2008-04-03 23:48 ` Jesse Barnes
2008-04-03 18:50 ` Jesse Barnes
2008-04-02 0:10 ` [RFC][PATCH 2/3] PM: New suspend and hibernation callbacks for platform bus type (rev. 3) Rafael J. Wysocki
2008-04-02 13:14 ` Pavel Machek
2008-04-02 13:14 ` Pavel Machek
2008-04-02 13:14 ` Pavel Machek
2008-04-02 0:10 ` Rafael J. Wysocki
2008-04-02 0:11 ` [RFC][PATCH 3/3] PM: New suspend and hibernation callbacks for PCI " Rafael J. Wysocki
2008-04-02 0:11 ` Rafael J. Wysocki
2008-03-25 20:23 ` Pavel Machek
2008-03-25 20:23 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200804031648.59630.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=airlied@linux.ie \
--cc=astarikovskiy@suse.de \
--cc=benh@kernel.crashing.org \
--cc=david-b@pacbell.net \
--cc=greg@kroah.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=ncunningham@crca.org.au \
--cc=oliver@neukum.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.