[PATCH v5 1/8] Documentation: arm: define DT cpu capacity-dmips-mhz bindings
From: Juri Lelli <hidden>
Date: 2016-06-15 14:22:43
Also in:
linux-devicetree, linux-pm, lkml
From: Juri Lelli <hidden>
Date: 2016-06-15 14:22:43
Also in:
linux-devicetree, linux-pm, lkml
On 15/06/16 15:04, Mark Brown wrote:
On Wed, Jun 15, 2016 at 11:17:50AM +0100, Juri Lelli wrote:quoted
+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.
quoted
+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