LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org> To: "Rafael J. Wysocki" <rjw@sisk.pl> Cc: 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>, Benjamin Herrenschmidt <benh@kernel.crashing.org>, 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 14:41:07 -0700 [thread overview] Message-ID: <200804031441.07703.jbarnes@virtuousgeek.org> (raw) In-Reply-To: <200804032323.59133.rjw@sisk.pl> On Thursday, April 03, 2008 2:23 pm Rafael J. Wysocki wrote: > > +static int i915_poweroff(struct device *dev) > > +{ > > + /* Shut down the device */ > > + pci_disable_device(dev->pdev); > > + pci_set_power_state(dev->pdev, PCI_D3hot); > > I think you may need to do that in ->suspend() too, as opposed to > ->freeze(), ... Because ->poweroff won't be called in the paths that do ->suspend? Ah yeah, must have skipped over that section of the documentation... > > > +} > > + > > +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 */ > > + .suspend = i915_save, > > + .resume = i915_restore, > > + .freeze = i915_save, > > ... so perhaps define ->suspend() as ->save() + ->poweroff()? Yep, I can just make a wrapper for it in the driver. Thanks a lot for making these changes to the core. My only worry is that all the old-style stuff will stick around forever... so fwiw you can add my Acked-by: Jesse Barnes <jesse.barnes@intel.com> to the series. Thanks, Jesse
next prev parent reply other threads:[~2008-04-03 21:49 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 [this message] 2008-04-03 21:47 ` Benjamin Herrenschmidt 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=200804031441.07703.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: linkBe 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; as well as URLs for NNTP newsgroup(s).