Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753384Ab3ILFgR (ORCPT ); Thu, 12 Sep 2013 01:36:17 -0400 Received: from mail-qc0-f180.google.com ([209.85.216.180]:52633 "EHLO mail-qc0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752700Ab3ILFgP (ORCPT ); Thu, 12 Sep 2013 01:36:15 -0400 MIME-Version: 1.0 In-Reply-To: <52310E43.1090808@intel.com> References: <2703632.ul5ekQh5oq@vostro.rjw.lan> <2013615.oHjWkmedue@vostro.rjw.lan> <52310E43.1090808@intel.com> Date: Thu, 12 Sep 2013 11:06:14 +0530 Message-ID: Subject: Re: "cpufreq: fix serialization issues with freq change notifiers" breaks cpufreq too From: Viresh Kumar To: "Rafael J. Wysocki" 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 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: 693 Lines: 18 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 -- 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/