From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rafael J. Wysocki" Subject: Re: "cpufreq: fix serialization issues with freq change notifiers" breaks cpufreq too Date: Thu, 12 Sep 2013 13:01:35 +0200 Message-ID: <3488595.xbBYlylYai@vostro.rjw.lan> References: <52310E43.1090808@intel.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7Bit Return-path: In-Reply-To: Sender: linux-pm-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii" To: Viresh Kumar Cc: "Rafael J. Wysocki" , Guennadi Liakhovetski , Greg KH , Linux Kernel Mailing List , "linux-arm-kernel@lists.infradead.org" , "linux-pm@vger.kernel.org" , "cpufreq@vger.kernel.org" , SH-Linux , Magnus Damm On Thursday, September 12, 2013 11:06:14 AM Viresh Kumar wrote: > On 12 September 2013 06:13, Rafael J. Wysocki > wrote: > > Yes, if you can point to a specific driver having this problem. > > There are so many of those (I know it because I went through almost all drivers > recently with my cleanup series): cpufreq-cpu0, omap-cpufreq, > exynos-cpufreq, etc.. > > They all do this: > > A. If new freq is more than old: Increase voltage > B. Change freq > C. If new freq is less than old: decrease voltage Well, if there's more than one it's even simpler. You can just pick one. :-) Like, "for example, does the following ... which may cause the hardware to misbehave, because ...". Thanks, Rafael