From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: balbi@ti.com
Cc: Keshava Munegowda <keshava_mgowda@ti.com>,
linux-usb@vger.kernel.org, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org, gadiyar@ti.com,
sameo@linux.intel.com, parthab@india.ti.com, tony@atomide.com,
khilman@ti.com, b-cousson@ti.com, paul@pwsan.com
Subject: Re: [PATCH 4/4] mfd: global Suspend and resume support of ehci and ohci
Date: Sun, 5 Jun 2011 19:19:38 +0200 [thread overview]
Message-ID: <201106051919.38637.rjw@sisk.pl> (raw)
In-Reply-To: <20110601143256.GG2409@legolas.emea.dhcp.ti.com>
On Wednesday, June 01, 2011, Felipe Balbi wrote:
> Hi,
>
> On Wed, Jun 01, 2011 at 03:54:38PM +0200, Rafael J. Wysocki wrote:
> > > +static const struct dev_pm_ops usbhsomap_dev_pm_ops = {
> > > + .suspend = usbhs_suspend,
> > > + .resume = usbhs_resume,
> > > +};
> >
> > Please add .freeze()/.thaw() and .poweroff()/.restore() callbacks too.
> > They may point to the same routines, but must be present.
> >
> > You can actually use the SIMPLE_DEV_PM_OPS() convenience macro for this
> > purpose.
>
> good point. BTW, do we need this #ifdef CONFIG_PM stuff which has been
> popping on most drivers recently ? To me it looks like driver.pm field
> is always available even if PM is disabled, so what's the point ? Saving
> a few bytes ?
Basically, yes (you may want to avoid defining the object this points to if
CONFIG_PM is unset).
Thanks,
Rafael
next prev parent reply other threads:[~2011-06-05 17:19 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 13:27 [PATCH 0/4] arm: omap: usb: Hwmod and Runtime PM support for EHCI & OHCI Keshava Munegowda
2011-06-01 13:27 ` [PATCH 1/4] arm: omap: usb: ehci and ohci hwmod structures for omap3 and omap4 Keshava Munegowda
2011-06-01 13:27 ` [PATCH 2/4] arm: omap: usb: register hwmods of usbhs Keshava Munegowda
2011-06-01 13:27 ` [PATCH 3/4] arm: omap: usb: device name change for the clk names " Keshava Munegowda
2011-06-01 13:27 ` [PATCH 4/4] mfd: global Suspend and resume support of ehci and ohci Keshava Munegowda
2011-06-01 13:31 ` Felipe Balbi
2011-06-01 13:38 ` Munegowda, Keshava
2011-06-01 13:54 ` Rafael J. Wysocki
2011-06-01 14:32 ` Felipe Balbi
2011-06-05 17:19 ` Rafael J. Wysocki [this message]
2011-06-05 18:50 ` Felipe Balbi
2011-06-05 19:30 ` Alan Stern
2011-06-05 19:54 ` Felipe Balbi
2011-06-06 16:06 ` Alan Stern
2011-06-06 17:25 ` Felipe Balbi
2011-06-06 18:03 ` Alan Stern
2011-06-06 9:45 ` Mark Brown
2011-06-02 0:06 ` Kevin Hilman
2011-06-29 15:22 ` Munegowda, Keshava
2011-06-29 16:37 ` Munegowda, Keshava
2011-06-29 17:33 ` Alan Stern
2011-06-29 18:17 ` Partha Basak
2011-06-29 18:47 ` Alan Stern
2011-06-29 19:20 ` Kevin Hilman
2011-06-30 12:40 ` Munegowda, Keshava
2011-06-01 20:05 ` [PATCH 3/4] arm: omap: usb: device name change for the clk names of usbhs Kevin Hilman
2011-06-01 20:01 ` [PATCH 2/4] arm: omap: usb: register hwmods " Kevin Hilman
2011-06-01 20:04 ` Kevin Hilman
2011-06-01 19:56 ` [PATCH 1/4] arm: omap: usb: ehci and ohci hwmod structures for omap3 and omap4 Kevin Hilman
2011-06-02 6:55 ` Munegowda, Keshava
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=201106051919.38637.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=b-cousson@ti.com \
--cc=balbi@ti.com \
--cc=gadiyar@ti.com \
--cc=keshava_mgowda@ti.com \
--cc=khilman@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=parthab@india.ti.com \
--cc=paul@pwsan.com \
--cc=sameo@linux.intel.com \
--cc=tony@atomide.com \
/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
Powered by JetHome