Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932694Ab3CVJFL (ORCPT ); Fri, 22 Mar 2013 05:05:11 -0400 Received: from mail-oa0-f54.google.com ([209.85.219.54]:34027 "EHLO mail-oa0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932373Ab3CVJFI (ORCPT ); Fri, 22 Mar 2013 05:05:08 -0400 MIME-Version: 1.0 In-Reply-To: References: <1363872506-3630-3-git-send-email-rajagopal.venkat@linaro.org> Date: Fri, 22 Mar 2013 14:35:07 +0530 Message-ID: Subject: Re: [PATCH 2/2] PM / devfreq: tie suspend/resume to runtime-pm From: Rajagopal Venkat To: Alan Stern Cc: myungjoo.ham@samsung.com, rjw@sisk.pl, Kevin Hilman , linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1536 Lines: 42 On 21 March 2013 20:32, Alan Stern wrote: > On Thu, 21 Mar 2013, Rajagopal Venkat wrote: > >> Allow device devfreq to be suspend/resume automatically with >> runtime pm suspend/resume. The devfreq drivers should be least >> cared when to suspend/resume the devfreq. >> >> pm_runtime_suspend(dev) will first suspend device devfreq(if available) >> before device is suspended from runtime pm core. >> >> pm_runtime_resume(dev) will resume device devfreq(if available) after >> device is resumed from runtime pm core. > > Aren't these backward? The device continues to need its clocks and > frequency settings until _after_ it has been suspended. Similarly, it > needs them to be available _before_ it resumes. > To clarify, devfreq suspend/resume means suspend/resume of load monitoring of a device. The clocks and other resources are still taken care by the devfreq driver runtime-pm callbacks. The devfreq must be suspended _before_ runtime-pm suspend callback in order to stop load monitoring while device is suspending. Similarly devfreq resume should happen _after_ runtime-pm resume callback. Just realised both devfreq suspend/resume are done _before_ invoking runtime-pm callbacks. I will fix this up. Thanks. > Alan Stern > -- Regards, Rajagopal -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/