From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Nigel Cunningham <ncunningham@crca.org.au>,
Dave Airlie <airlied@linux.ie>,
LKML <linux-kernel@vger.kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
pm list <linux-pm@lists.linux-foundation.org>,
Alexey Starikovskiy <astarikovskiy@suse.de>
Subject: Re: [RFC][PATCH 1/3] use new pm_ops in DRM drivers
Date: Fri, 04 Apr 2008 08:47:47 +1100 [thread overview]
Message-ID: <1207259267.10388.334.camel@pasglop> (raw)
In-Reply-To: <200804031150.55967.jbarnes@virtuousgeek.org>
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...
Ben.
next prev parent reply other threads:[~2008-04-03 21:47 UTC|newest]
Thread overview: 12+ 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 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 21:23 ` Rafael J. Wysocki
2008-04-03 21:41 ` Jesse Barnes
2008-04-03 21:47 ` Benjamin Herrenschmidt [this message]
2008-04-03 23:48 ` 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 0:11 ` [RFC][PATCH 3/3] PM: New suspend and hibernation callbacks for PCI " Rafael J. Wysocki
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=1207259267.10388.334.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=airlied@linux.ie \
--cc=astarikovskiy@suse.de \
--cc=jbarnes@virtuousgeek.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 \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox