From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rafael J. Wysocki" 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 Message-ID: <201108262252.40366.rjw@sisk.pl> References: <1314363693-20831-1-git-send-email-govindraj.raja@ti.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit Return-path: Received: from ogre.sisk.pl ([217.79.144.158]:41191 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754576Ab1HZUuw (ORCPT ); Fri, 26 Aug 2011 16:50:52 -0400 In-Reply-To: <1314363693-20831-1-git-send-email-govindraj.raja@ti.com> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: "Govindraj.R" Cc: Paul Walmsley , Kevin Hilman , linux-omap@vger.kernel.org, linux-pm@lists.linux-foundation.org, Vishwanath Sripathy , Partha Basak , Felipe Balbi , Santosh Shilimkar , Rajendra Nayak , Benoit Cousson , Tero Kristo , Keshava Munegowda 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