[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKohpompkiUqOati4B8F0HqN2eTMEADm01SnUuE0_GxnTAWJdQ@mail.gmail.com>
Date: Mon, 25 Nov 2013 15:44:02 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: "Rafael J. Wysocki" <rjw@...ysocki.net>
Cc: Stephen Warren <swarren@...dotorg.org>,
Stephen Warren <swarren@...dia.com>,
Kukjin Kim <kgene@...nel.org>,
Amit Daniel Kachhap <amit.daniel@...sung.com>,
Sachin Kamat <sachin.kamat@...aro.org>,
Lists linaro-kernel <linaro-kernel@...ts.linaro.org>,
Patch Tracking <patches@...aro.org>,
"cpufreq@...r.kernel.org" <cpufreq@...r.kernel.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Lan Tianyu <tianyu.lan@...el.com>, Nishanth Menon <nm@...com>,
jinchoi@...adcom.com,
Sebastian Capella <sebastian.capella@...aro.org>,
Peter De Schrijver <pdeschrijver@...dia.com>
Subject: Re: [PATCH V2 2/2] cpufreq: Change freq before suspending governors
On 25 November 2013 09:58, Viresh Kumar <viresh.kumar@...aro.org> wrote:
> Giving cpufreq-drivers a chance to do whatever they want looks to be
> correct. So, maybe prepare() or suspend_prepare() for them can be
> implemented.
I have used the existing infrastructure here, i.e. suspend/resume callbacks
for drivers.. As we don't need two suspend calls now..
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists