Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756527Ab3FLLOL (ORCPT ); Wed, 12 Jun 2013 07:14:11 -0400 Received: from hydra.sisk.pl ([212.160.235.94]:34869 "EHLO hydra.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753106Ab3FLLOJ (ORCPT ); Wed, 12 Jun 2013 07:14:09 -0400 From: "Rafael J. Wysocki" To: Lukasz Majewski Cc: Viresh Kumar , "cpufreq@vger.kernel.org" , Linux PM list , Vincent Guittot , Jonghwa Lee , Myungjoo Ham , linux-kernel , Lukasz Majewski , Andre Przywara , Daniel Lezcano , Kukjin Kim Subject: Re: [PATCH v2 1/3] cpufreq:boost: CPU frequency boost code unification for software and hardware solutions Date: Wed, 12 Jun 2013 13:23:20 +0200 Message-ID: <2535901.EBhXeQ6J8O@vostro.rjw.lan> User-Agent: KMail/4.9.5 (Linux/3.10.0-rc5+; KDE/4.9.5; x86_64; ; ) In-Reply-To: <20130612093938.1cf73c9a@amdc308.digital.local> References: <1370502472-7249-1-git-send-email-l.majewski@samsung.com> <20130612093938.1cf73c9a@amdc308.digital.local> 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 Content-Length: 3061 Lines: 103 On Wednesday, June 12, 2013 09:39:38 AM Lukasz Majewski wrote: > Hi Viresh, > > > Hi, > > > > Change subject to: "cpufreq: Add boost frequency support in core" > > Ok. > > > > > On 11 June 2013 14:33, Lukasz Majewski wrote: > > > This commit adds support for software based frequency boosting. > > > > No. It adds support for both software and hardware boosting. So just > > write: This commit adds boost frequency support in cpufreq core > > (Hardware & Software). > > Ok. > > > > > Some SoC (like Exynos4 - e.g. 4x12) allow setting frequency above > > > its normal condition limits. Such a change shall be only done for a > > > short > > > > s/condition/operation > > s/change/mode > > s/done/used > > > > Ok. > > > > time. > > > > > > Overclocking (boost) support is essentially provided by platform > > > dependent cpufreq driver. > > > > > > This commit unifies support for SW and HW (Intel) over clocking > > > solutions in the core cpufreq driver. Previously the "boost" sysfs > > > attribute was defined at acpi driver code. > > > By default boost is disabled. One global attribute is available at: > > > /sys/devices/system/cpu/cpufreq/boost. > > > > Enter a blank line here. > > Ok > > > > > > It only shows up when cpufreq driver supports overclocking. > > > Under the hood frequencies dedicated for boosting are marked with a > > > special flag (CPUFREQ_BOOST_FREQ) at driver's frequency table. > > > It is the user's concern to enable/disable overclocking with proper > > > call to sysfs. > > > > Good. > > > > > Signed-off-by: Lukasz Majewski > > > Signed-off-by: Myungjoo Ham > > > > > > --- > ^^^^ > [*] this --- was added manually by me. > > > > Changes for v2: > > > - Removal of cpufreq_boost structure and move its fields to > > > cpufreq_driver structure > > > - Flag to indicate if global boost attribute is already defined > > > - Extent the pr_{err|debbug} functions to show current function > > > names --- > > > > You don't have to manually add "---" here. Just keep a blank line > > instead. > > One "---" is added by git automatically. The [*] was added to distinct > the changelog from rest of the commit. At least older versions of GIT > required this to not include changelog to commit messages. Which doesn't matter anyway. None of them will show up in git log, so don't worry. :-) [...] > > > And so we must have used > > boost_en here. > > boost_en has two meanings: > 0 - either boost disabled or not supported (when low_level_boost=NULL). > 1 - boost is enabled. Gosh, please don't do that. Use *two* flags, one meaning "supported" and the second meaning "enabled". Thanks, Rafael -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. -- 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/