From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rabin Vincent Subject: Re: i2c runtime suspend and system wide suspend Date: Thu, 30 Dec 2010 12:02:53 +0530 Message-ID: References: <4D1C0CFE.5010008@codeaurora.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: Received: from mail-fx0-f46.google.com ([209.85.161.46]:40996 "EHLO mail-fx0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751322Ab0L3Gc5 (ORCPT ); Thu, 30 Dec 2010 01:32:57 -0500 In-Reply-To: <4D1C0CFE.5010008@codeaurora.org> Sender: linux-arm-msm-owner@vger.kernel.org List-Id: linux-arm-msm@vger.kernel.org To: Abhijeet Dharmapurikar Cc: "Rafael J. Wysocki" , Mark Brown , Jean Delvare , Rajendra Nayak , Kevin Hilman , Vishwanath BS , Partha Basak , linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-pm@lists.linux-foundation.org, linux-i2c@vger.kernel.org On Thu, Dec 30, 2010 at 10:09 AM, Abhijeet Dharmapurikar wrote: > The i2c-core driver mixes runtime suspend and system wide suspend, in that, > during a system wide suspend, it skips calling ->suspend if the device is > runtime suspended. > > I have an interrupt controller running over the i2c bus and that driver is > oblivious of the runtime pm framework, IOW, it doesn't do any runtime pm > calls. CONFIG_RUNTIME_PM is enabled however (for some other bus drivers). > The issue I am facing is that all such i2c devices are assumed runtime > suspended and the ->suspend for these devices is not invoked during > systemwide suspend. This was discussed on linux-pm recently. Rafael had a fix, I'm don't know whether it's applied yet: https://lists.linux-foundation.org/pipermail/linux-pm/2010-December/029567.html https://lists.linux-foundation.org/pipermail/linux-pm/2010-December/029596.html Also relevant: https://lists.linux-foundation.org/pipermail/linux-pm/2010-December/029600.html https://lists.linux-foundation.org/pipermail/linux-pm/2010-December/029658.html