From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Ohad Ben-Cohen <ohad@wizery.com>,
linux-pm@lists.linux-foundation.org, linux-mmc@vger.kernel.org
Subject: Re: [linux-pm] generic runtime pm callbacks
Date: Mon, 6 Sep 2010 15:59:51 +0100 [thread overview]
Message-ID: <20100906145951.GI10367@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1009061025300.14908-100000@netrider.rowland.org>
On Mon, Sep 06, 2010 at 10:30:05AM -0400, Alan Stern wrote:
> The real issue with USB interfaces is that they are only logical
> sub-devices; they can't be power-managed separately from their parent.
> Indeed, the runtime_suspend and runtime_resume callbacks for interfaces
> always return 0 immediately without doing anything, and the
> runtime_idle callback always calls pm_runtime_suspend.
> So why not tell the PM core about this behavior? Let's put a
> "no_callbacks" flag in dev_pm_info. When this flag is set the core
> won't bother invoking the runtime callbacks; it can always assume
> success. More importantly, an asynchronous request may never need to
> use the workqueue:
...
> Does that look like what you're talking about?
That'd cover my use case, though it would still be nice to have the
flexibility to just omit individual callbacks in the same way that it's
possible to do so with regular suspend and resume (eg, if you only have
to restore some state after the bus has suspended your device).
next prev parent reply other threads:[~2010-09-06 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-06 12:32 generic runtime pm callbacks Ohad Ben-Cohen
2010-09-06 13:22 ` [linux-pm] " Mark Brown
2010-09-06 14:30 ` Alan Stern
2010-09-06 14:59 ` Mark Brown [this message]
2010-09-06 19:07 ` Rafael J. Wysocki
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=20100906145951.GI10367@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=ohad@wizery.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox