Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965021Ab3E2Hjo (ORCPT ); Wed, 29 May 2013 03:39:44 -0400 Received: from mail-qe0-f50.google.com ([209.85.128.50]:62581 "EHLO mail-qe0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935099Ab3E2Hjm (ORCPT ); Wed, 29 May 2013 03:39:42 -0400 MIME-Version: 1.0 In-Reply-To: <20130529090902.66c29c26@amdc308.digital.local> References: <1367590072-10496-1-git-send-email-jonghwa3.lee@samsung.com> <2272781.tC3OqoQmKI@vostro.rjw.lan> <20130528152625.1b7833e5@amdc308.digital.local> <76114024.UaPHgm94jK@vostro.rjw.lan> <20130529090902.66c29c26@amdc308.digital.local> Date: Wed, 29 May 2013 13:09:41 +0530 Message-ID: Subject: Re: [RFC v2 0/3][TESTS] LAB: Support for Legacy Application Booster governor - tests results From: Viresh Kumar To: Lukasz Majewski Cc: "Rafael J. Wysocki" , Jonghwa Lee , "linux-kernel@vger.kernel.org" , "cpufreq@vger.kernel.org" , "linux-pm@vger.kernel.org" , Vicent Guittot , Daniel Lezcano , MyungJoo Ham , Lukasz Majewski 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: 1585 Lines: 46 On 29 May 2013 12:39, Lukasz Majewski wrote: > I also agree. Moreover, I think that there should be only one set of > "boost" sysfs entries either it is supported by HW (Intel) or SW (ARM). Yes, you need to change acpi-cpufreq driver too to use this common infrastructure. > I can think of two "basic" one: > - max_turbo_freq (ro) This is surely per policy as two separate clusters can have separate values. And probably a better one would be scaling_boost_frequencies, that will list all boost frequencies. > - turbo_mode/boost (rw) I am confused with these two names: boost and turbo.. Probably we should use a single name everywhere. Because acpi-cpufreq is already using boost, we might shift to that. > - /sys/devices/system/cpu/cpufreq/boost Obviously this one. > On the other hand first option would be used with systems, where > per-core (or core sets) frequency setting is possible (b.L, Snapdragon > S4) For now this feature would be enabled on all clusters and controlled by cpu/cpufreq/boost. > To sum up - the idea is as follow: > > 1. cpufreq_driver exports turbo_mode=1 when it supports overclocking > (this support can be hardcoded or read from device tree) > > 2. Then proper entries are exported to sysfs. > > 3. User via sysfs (at [*]) can enable/disable the feature on demand Bingo!! -- 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/