Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754842AbaFKKOG (ORCPT ); Wed, 11 Jun 2014 06:14:06 -0400 Received: from service87.mimecast.com ([91.220.42.44]:43178 "EHLO service87.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751457AbaFKKOD convert rfc822-to-8bit (ORCPT ); Wed, 11 Jun 2014 06:14:03 -0400 Date: Wed, 11 Jun 2014 11:13:55 +0100 From: Lorenzo Pieralisi To: Chander Kashyap Cc: Nicolas Pitre , Doug Anderson , "linux-arm-kernel@lists.infradead.org" , Kukjin Kim , "linux@arm.linux.org.uk" , Kevin Hilman , Andrew Bresticker , Inderpal Singh , "linux-kernel@vger.kernel.org" , Chander Kashyap , "olof@lixom.net" , Tushar Behera , Thomas Abraham , Abhilash Kesavan , Javier Martinez Canillas , "linux-samsung-soc@vger.kernel.org" Subject: Re: [PATCH] ARM: EXYNOS: mcpm: Don't rely on firmware's secondary_cpu_start Message-ID: <20140611101353.GA18781@e102568-lin.cambridge.arm.com> References: <1402090985-8061-1-git-send-email-dianders@chromium.org> <20140607181221.GB25068@e102568-lin.cambridge.arm.com> <20140609223831.GB16889@e102568-lin.cambridge.arm.com> MIME-Version: 1.0 In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-OriginalArrivalTime: 11 Jun 2014 10:13:53.0757 (UTC) FILETIME=[D915C8D0:01CF855D] X-MC-Unique: 114061111140013801 Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: 8BIT Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jun 11, 2014 at 05:52:10AM +0100, Chander Kashyap wrote: > Hi Doug, > > On Tue, Jun 10, 2014 at 9:19 PM, Nicolas Pitre wrote: > > On Tue, 10 Jun 2014, Doug Anderson wrote: > > > >> My S-state knowledge is not strong, but I believe that Lorenzo's > >> questions matter if we're using S2 for CPUidle (where we actually turn > >> off power and hot unplug CPUs) but not when we're using S1 for CPUidle > >> (where we just enter WFI/WFE). > >> > > No Its not plain WFI. > > All cores in Exynos5420 can be powered off independently. > This functionality has been tested. > > Below is the link for the posted patches. > > https://lkml.org/lkml/2014/6/10/194 > > And as Nicolas wrote, these patches need MCPM for that. Chander, I cast a look into the code and I have a question (you also told me on CPUidle review that only core off is supported in CPUidle). When you say all cores can be powered off independently, do you also mean that clusters can be powered off (in CPUidle) ? I am pointing this out since in the MCPM backend I noticed: "/* TODO: Turn off the cluster here to save power. */" I do not see any cluster power down request in the down path. If I am wrong, ignore my message, I am just writing to help. If you can only power down cores, but not the clusters on idle, please keep in mind that you are currently cleaning and invalidating the L2 when last man is running and this must not be taken lightly since, if L2 stays on, that's a massive energy waste for nothing. So, if clusters stay up, you _have_ to tweak the MCPM backend slightly to avoid cleaning L2, that's pivotal. Lorenzo > > >> I believe that in ChromeOS we use S1 CPUidle and that it works fine. > >> We've never implemented S2 that I'm aware of. > > > > You'll have to rely on MCPM for that. That's probably why it hasn't > > been implemented before. > > > > > > Nicolas > > > > _______________________________________________ > > linux-arm-kernel mailing list > > linux-arm-kernel@lists.infradead.org > > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel > -- > 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/ > -- 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/