From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933047AbcFOOWn (ORCPT ); Wed, 15 Jun 2016 10:22:43 -0400 Received: from foss.arm.com ([217.140.101.70]:37759 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932406AbcFOOWl (ORCPT ); Wed, 15 Jun 2016 10:22:41 -0400 Date: Wed, 15 Jun 2016 15:22:39 +0100 From: Juri Lelli To: Mark Brown Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, peterz@infradead.org, vincent.guittot@linaro.org, robh+dt@kernel.org, mark.rutland@arm.com, linux@arm.linux.org.uk, sudeep.holla@arm.com, lorenzo.pieralisi@arm.com, catalin.marinas@arm.com, will.deacon@arm.com, morten.rasmussen@arm.com, dietmar.eggemann@arm.com, sgurrappadi@nvidia.com, Pawel Moll , Ian Campbell , Kumar Gala , Maxime Ripard , Olof Johansson , Gregory CLEMENT , Paul Walmsley , Linus Walleij , Chen-Yu Tsai , Thomas Petazzoni Subject: Re: [PATCH v5 1/8] Documentation: arm: define DT cpu capacity-dmips-mhz bindings Message-ID: <20160615142239.GD5981@e106622-lin> References: <1465985877-18271-1-git-send-email-juri.lelli@arm.com> <1465985877-18271-2-git-send-email-juri.lelli@arm.com> <20160615140447.GB2282@sirena.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160615140447.GB2282@sirena.org.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 15/06/16 15:04, Mark Brown wrote: > On Wed, Jun 15, 2016 at 11:17:50AM +0100, Juri Lelli wrote: > > > +CPU capacities are obtained by running a suitable benchmark. This binding makes > > +no aspersions on the validity or suitability of any particular benchmark, the > > +final capacity should, however, be: > > Makes no guarantees. An aspersion is an insult! > Whoops! :-/ Sure, I'll change that. > > +CPU capacities are obtained by running the Dhrystone benchmark on each CPU at > > +max frequency. The obtained DMIPS score is then divided by the frequency (in > > +MHz) at which the benchmark has been run, so that DMIPS/MHz are obtained. > > +Such values are then normalized w.r.t. the highest score obtained in the > > +system. > > Perhaps worth mentioning that caches and so on should be enabled (based > on previous experience with people doing bringup)? OK. I'll add something along this line. Thanks, - Juri