From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752487AbbBRP7Q (ORCPT ); Wed, 18 Feb 2015 10:59:16 -0500 Received: from v094114.home.net.pl ([79.96.170.134]:56487 "HELO v094114.home.net.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1751860AbbBRP7P (ORCPT ); Wed, 18 Feb 2015 10:59:15 -0500 From: "Rafael J. Wysocki" To: Peter Zijlstra Cc: Lorenzo Pieralisi , "linux-kernel@vger.kernel.org" , "mingo@kernel.org" , "tglx@linutronix.de" , Nicolas Pitre , Russell King Subject: Re: [PATCH 34/35] tick: Provide tick_suspend_local() Date: Wed, 18 Feb 2015 17:22:26 +0100 Message-ID: <7465245.qd0pH8CNtP@vostro.rjw.lan> User-Agent: KMail/4.11.5 (Linux/3.19.0+; KDE/4.11.5; x86_64; ; ) In-Reply-To: <20150218133524.GU5029@twins.programming.kicks-ass.net> References: <20150216121435.203983131@infradead.org> <20150217143142.GB15881@red-moon> <20150218133524.GU5029@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wednesday, February 18, 2015 02:35:24 PM Peter Zijlstra wrote: > On Tue, Feb 17, 2015 at 02:31:42PM +0000, Lorenzo Pieralisi wrote: > > On Mon, Feb 16, 2015 at 12:15:09PM +0000, Peter Zijlstra wrote: > > > From: Thomas Gleixner > > > > > > This function is intended to use by the freezer once the freezer folks > > > solved their race issues. Also required to get rid of the ARM BL > > > switcher tick hackery. > > > > Totally agree with the patch(es), but I noticed that the ARM bL switcher > > does not depend on PM_SLEEP, so I do not think you can compile > > tick_{suspend/resume}_local() out if !PM_SLEEP, unless dependency > > is enforced by the ARM bL switcher config but I do not think that > > the config dependency really exists, Nico please correct me if I am > > wrong. > > Ah I see, the headers seem to do the right thing and declare the > function in core (GENERIC_CLOCKEVENTS) with a comment. > > But then the patch continues defining the functions under PM_SLEEP. > > I wonder why the build robot has not reported fail on this.. > > Would the below make sense? That needs to be done on top of the suspend-to-idle material that has just been merged. Why don't you drop the PM_SLEEP-related changes from the series for the time being and let's clean things up top of it? That should be more straightforward I think. Rafael