From: Kevin Hilman <khilman@ti.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Rajendra Nayak <rnayak@ti.com>, Ben Dooks <ben-linux@fluff.org>,
linux-i2c@vger.kernel.org, linux-pm@lists.linux-foundation.org,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [linux-pm] [PATCH] i2c: OMAP: fix static suspend vs. runtime suspend
Date: Mon, 31 Jan 2011 08:09:12 -0800 [thread overview]
Message-ID: <877hdl9hsn.fsf@ti.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1101311010580.1931-100000@iolanthe.rowland.org> (Alan Stern's message of "Mon, 31 Jan 2011 10:13:13 -0500 (EST)")
Alan Stern <stern@rowland.harvard.edu> writes:
> On Mon, 31 Jan 2011, Rajendra Nayak wrote:
>
>> Can you elaborate a bit more on how/why runtime PM transitions
>> are disabled during system suspend, and how is it taken care
>> of that a runtime resume of a device works however a subsequent
>> runtime (re)suspend does not?
>
> I'll answer for Kevin. This is done by the PM core, in order to
> prevent runtime power transitions from interfering with a system power
> transition. The PM core increments the device's usage_count; this
> prevents the device from being runtime-suspended but it allows
> runtime-resume calls to go through.
I understand how this works, but frankly I'm still a bit fuzzy on why.
I guess I'm still missing a good understanding of what "interfering with a
system power transition" means, and why a runtime suspend qualifies as
interfering but not a runtime resume.
More specifically, the reason for $SUBJECT patch is precisely because a
runtime resume is allowed, a runtime suspend is not, and thus a system
power transititon is prevented.
Kevin
next prev parent reply other threads:[~2011-01-31 16:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 0:18 [PATCH] i2c: OMAP: fix static suspend vs. runtime suspend Kevin Hilman
2011-01-31 11:28 ` Rajendra Nayak
2011-01-31 15:13 ` [linux-pm] " Alan Stern
[not found] ` <Pine.LNX.4.44L0.1101311010580.1931-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2011-01-31 15:28 ` Rajendra Nayak
2011-01-31 16:09 ` Kevin Hilman [this message]
[not found] ` <877hdl9hsn.fsf-l0cyMroinI0@public.gmane.org>
2011-01-31 16:22 ` Alan Stern
[not found] ` <Pine.LNX.4.44L0.1101311119190.1931-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2011-01-31 18:19 ` Rafael J. Wysocki
[not found] ` <201101311919.49225.rjw-KKrjLPT3xs0@public.gmane.org>
2011-02-11 20:00 ` [PATCH] PM: Allow pm_runtime_suspend() to succeed during system suspend Rafael J. Wysocki
[not found] ` <201102112100.23996.rjw-KKrjLPT3xs0@public.gmane.org>
2011-02-11 20:36 ` Alan Stern
2011-02-11 20:38 ` Kevin Hilman
[not found] ` <87ei7e9uhy.fsf-l0cyMroinI0@public.gmane.org>
2011-02-11 21:25 ` Rafael J. Wysocki
2011-02-11 23:45 ` Kevin Hilman
[not found] ` <87aai26sq4.fsf-l0cyMroinI0@public.gmane.org>
2011-02-12 0:00 ` Rafael J. Wysocki
[not found] ` <1296173921-4832-1-git-send-email-khilman-l0cyMroinI0@public.gmane.org>
2011-02-05 16:08 ` [PATCH] i2c: OMAP: fix static suspend vs. runtime suspend Ben Dooks
[not found] ` <20110205160843.GD15795-SMNkleLxa3Z6Wcw2j4pizdi2O/JbrIOy@public.gmane.org>
2011-02-08 18:31 ` Kevin Hilman
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=877hdl9hsn.fsf@ti.com \
--to=khilman@ti.com \
--cc=ben-linux@fluff.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=rnayak@ti.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;
as well as URLs for NNTP newsgroup(s).