From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: linux-pm@lists.linux-foundation.org, linux-omap@vger.kernel.org,
Alan Stern <stern@rowland.harvard.edu>,
Ming Lei <tom.leiming@gmail.com>
Subject: Re: [linux-pm] [PATCH] PM: runtime PM + idle: allow usage when interrupts are disabled
Date: Mon, 16 Aug 2010 23:18:03 +0200 [thread overview]
Message-ID: <201008162318.03923.rjw@sisk.pl> (raw)
In-Reply-To: <1281459261-30829-1-git-send-email-khilman@deeprootsystems.com>
On Tuesday, August 10, 2010, Kevin Hilman wrote:
> When using runtime PM in combination with CPUidle, the runtime PM
> transtions of some devices may be triggered during the idle path.
> Late in the idle sequence, interrupts will likely be disabled when
> runtime PM for these devices is initiated.
>
> Currently, the runtime PM core assumes methods are called with
> interrupts enabled. However, if it is called with interrupts
> disabled, the internal locking unconditionally enables interrupts, for
> example:
>
> pm_runtime_put_sync()
Please don't use that from interrupt context. There's pm_runtime_put()
exactly for this purpose that puts the _idle() call into a workqueue.
> __pm_runtime_put()
> pm_runtime_idle()
> spin_lock_irq()
> __pm_runtime_idle()
> spin_unlock_irq() <--- interrupts unconditionally enabled
That's because __pm_runtime_idle() has to be called from process context.
> dev->bus->pm->runtime_idle()
> spin_lock_irq()
> spin_unlock_irq()
Thanks,
Rafael
next prev parent reply other threads:[~2010-08-16 21:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 16:54 [PATCH] PM: runtime PM + idle: allow usage when interrupts are disabled Kevin Hilman
2010-08-14 1:15 ` [linux-pm] " Alan Stern
2010-08-19 21:30 ` Kevin Hilman
2010-08-20 14:14 ` Alan Stern
2010-08-23 15:22 ` Kevin Hilman
2010-08-23 7:18 ` Pavel Machek
2010-08-14 3:38 ` Ming Lei
2010-08-16 21:18 ` Rafael J. Wysocki [this message]
2010-08-19 11:02 ` [linux-pm] " Basak, Partha
2010-08-19 21:37 ` Kevin Hilman
2010-08-20 23:27 ` Rafael J. Wysocki
2010-08-23 15:24 ` 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=201008162318.03923.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=stern@rowland.harvard.edu \
--cc=tom.leiming@gmail.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;
as well as URLs for NNTP newsgroup(s).