Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753998Ab3IMQ06 (ORCPT ); Fri, 13 Sep 2013 12:26:58 -0400 Received: from caramon.arm.linux.org.uk ([78.32.30.218]:54693 "EHLO caramon.arm.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752112Ab3IMQ05 (ORCPT ); Fri, 13 Sep 2013 12:26:57 -0400 Date: Fri, 13 Sep 2013 17:26:43 +0100 From: Russell King - ARM Linux To: Viresh Kumar Cc: "Rafael J. Wysocki" , Lists linaro-kernel , Patch Tracking , "cpufreq@vger.kernel.org" , "linux-pm@vger.kernel.org" , Linux Kernel Mailing List , "linux-arm-kernel@lists.infradead.org" Subject: Re: [PATCH 206/228] cpufreq: sa11x0: remove calls to cpufreq_notify_transition() Message-ID: <20130913162643.GF12758@n2100.arm.linux.org.uk> References: <6e2ca86ce948c0bc35f7709baf22672771fcf1e8.1379063063.git.viresh.kumar@linaro.org> <20130913155424.GB12758@n2100.arm.linux.org.uk> <20130913161527.GE12758@n2100.arm.linux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.19 (2009-01-05) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1386 Lines: 33 On Fri, Sep 13, 2013 at 09:52:31PM +0530, Viresh Kumar wrote: > On 13 September 2013 21:45, Russell King - ARM Linux > wrote: > > The patch to which I'm replying removes the above calls. These calls are > > necessary to shutdown various bits of CPU-clock dependent hardware > > before changing the CPU clock, and restore them - reconfiguring them > > for the new clock rate after the transition has happened. > > > > So, if you're removing these calls, what replaces them? I don't see > > anything which does without the above set. > > The other patch on which you commented about unnecessary read > locks being taken: > > [PATCH 181/228] cpufreq: move freq change notifications to cpufreq > > That calls these notifiers, for all platforms except the ones that have > set CPUFREQ_ASYNC_NOTIFICATION, before and after calling > ->target_index().. > > And so functionally the code is supposed to be the same.. Unless I > have done some stupid mistake.. Ah, sorry, read that that test the other way around. In that case, this patch is fine and can have my ack as per the other acks I've already given. Thanks. -- 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/