From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932537AbdLOPus (ORCPT ); Fri, 15 Dec 2017 10:50:48 -0500 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:57974 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932311AbdLOPup (ORCPT ); Fri, 15 Dec 2017 10:50:45 -0500 Date: Fri, 15 Dec 2017 15:50:41 +0000 From: Catalin Marinas To: Viresh Kumar Cc: arm@kernel.org, Will Deacon , Vincent Guittot , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH] arm64: defconfig: Select schedutil as default cpufreq governor Message-ID: <20171215155040.mlvd56i2rfgd2e2t@armageddon.cambridge.arm.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Nov 16, 2017 at 11:51:36AM +0530, Viresh Kumar wrote: > Currently performance governor is getting selected by default, which is > surely not a very good choice as its pretty much power hungry. > > Select schedutil instead. And why do we care about this in defconfig? People deploying their own kernels in mobile may opt for this config, others may prefer the default governor. Also it seems it would be the only architecture make this governor the default, so NAK. -- Catalin