From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Govindraj.R" <govindraj.raja@ti.com>
Cc: Paul Walmsley <paul@pwsan.com>, Kevin Hilman <khilman@ti.com>,
linux-omap@vger.kernel.org, linux-pm@lists.linux-foundation.org,
Vishwanath Sripathy <vishwanath.bs@ti.com>,
Partha Basak <p-basak2@ti.com>, Felipe Balbi <balbi@ti.com>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Rajendra Nayak <rnayak@ti.com>, Benoit Cousson <b-cousson@ti.com>,
Tero Kristo <t-kristo@ti.com>,
Keshava Munegowda <keshava_mgowda@ti.com>
Subject: Re: Issue: Runtime API usage in wake-up device irq_handler during wakeup from system-wide-suspend.
Date: Fri, 26 Aug 2011 22:52:40 +0200 [thread overview]
Message-ID: <201108262252.40366.rjw@sisk.pl> (raw)
In-Reply-To: <1314363693-20831-1-git-send-email-govindraj.raja@ti.com>
On Friday, August 26, 2011, Govindraj.R wrote:
> Hello,
>
> During system_wide_suspend pm runtime is disabled.
> I.e. __pm_runtime_disable is called from __device_suspend.
> Now, if a wakeup interrupt is triggered and the wakeup device irq handler
> is called even before device_resume and pm_runtime_enable happens,
> the device irq_handler proceeds to enable clock with runtime API to
> handle wakeup event.
>
> Wouldn't this result in system wide abort since the pm_runtime is not enabled
> yet from dpm_resume?
> As we end up accessing regs after doing runtime get_sync.
>
> Looks like this scenario is not handled currently.
> Or Am I missing something here?
To be precise, what do you mean by "wakeup interrupt"?
Rafael
prev parent reply other threads:[~2011-08-26 20:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-26 13:01 Issue: Runtime API usage in wake-up device irq_handler during wakeup from system-wide-suspend Govindraj.R
2011-08-26 18:36 ` [linux-pm] " Alan Stern
2011-08-27 6:30 ` Santosh
2011-08-27 14:01 ` Alan Stern
2011-08-27 14:49 ` Santosh
2011-08-27 19:42 ` Alan Stern
2011-09-07 15:48 ` Tero Kristo
2011-09-07 17:59 ` Kevin Hilman
2011-09-08 4:58 ` Tero Kristo
2011-09-08 13:51 ` Kevin Hilman
2011-08-26 20:52 ` Rafael J. Wysocki [this message]
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=201108262252.40366.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=b-cousson@ti.com \
--cc=balbi@ti.com \
--cc=govindraj.raja@ti.com \
--cc=keshava_mgowda@ti.com \
--cc=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=p-basak2@ti.com \
--cc=paul@pwsan.com \
--cc=rnayak@ti.com \
--cc=santosh.shilimkar@ti.com \
--cc=t-kristo@ti.com \
--cc=vishwanath.bs@ti.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