All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Brugger <matthias.bgg@gmail.com>
To: "AngeloGioacchino Del Regno"
	<angelogioacchino.delregno@collabora.com>,
	"Nícolas F. R. A. Prado" <nfraprado@collabora.com>
Cc: kernel@collabora.com, Conor Dooley <conor+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Seiya Wang <seiya.wang@mediatek.com>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH] arm64: dts: mediatek: mt8192: Fix CPUs capacity-dmips-mhz
Date: Tue, 6 Jun 2023 08:38:42 +0200	[thread overview]
Message-ID: <4b2fdd36-0871-ecc7-5d64-e088d7f51987@gmail.com> (raw)
In-Reply-To: <01c88a42-274c-f8cf-73a6-29741579d9db@collabora.com>



On 05/06/2023 10:21, AngeloGioacchino Del Regno wrote:
> Il 02/06/23 20:35, Nícolas F. R. A. Prado ha scritto:
>> The capacity-dmips-mhz parameter was miscalculated: this SoC runs
>> the first (Cortex-A55) cluster at a maximum of 2000MHz and the
>> second (Cortex-A76) cluster at a maximum of 2200MHz.
>>
>> In order to calculate the right capacity-dmips-mhz, the following
>> test was performed:
>> 1. CPUFREQ governor was set to 'performance' on both clusters
>> 2. Ran dhrystone with 500000000 iterations for 10 times on each cluster
>> 3. Calculated the mean result for each cluster
>> 4. Calculated DMIPS/MHz: dmips_mhz = dmips_per_second / cpu_mhz
>> 5. Scaled results to 1024:
>>     result_c0 = dmips_mhz_c0 / dmips_mhz_c1 * 1024
>>
>> The mean results for this SoC are:
>> Cluster 0 (LITTLE): 12016411 Dhry/s
>> Cluster 1 (BIG): 31702034 Dhry/s
>>
>> The calculated scaled results are:
>> Cluster 0: 426.953226899238 (rounded to 427)
>> Cluster 1: 1024
>>
>> Fixes: 48489980e27e ("arm64: dts: Add Mediatek SoC MT8192 and evaluation board 
>> dts and Makefile")
>> Signed-off-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
>>
> 

Applied, thanks
> Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> 
> 


WARNING: multiple messages have this Message-ID (diff)
From: Matthias Brugger <matthias.bgg@gmail.com>
To: "AngeloGioacchino Del Regno"
	<angelogioacchino.delregno@collabora.com>,
	"Nícolas F. R. A. Prado" <nfraprado@collabora.com>
Cc: kernel@collabora.com, Conor Dooley <conor+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Seiya Wang <seiya.wang@mediatek.com>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH] arm64: dts: mediatek: mt8192: Fix CPUs capacity-dmips-mhz
Date: Tue, 6 Jun 2023 08:38:42 +0200	[thread overview]
Message-ID: <4b2fdd36-0871-ecc7-5d64-e088d7f51987@gmail.com> (raw)
In-Reply-To: <01c88a42-274c-f8cf-73a6-29741579d9db@collabora.com>



On 05/06/2023 10:21, AngeloGioacchino Del Regno wrote:
> Il 02/06/23 20:35, Nícolas F. R. A. Prado ha scritto:
>> The capacity-dmips-mhz parameter was miscalculated: this SoC runs
>> the first (Cortex-A55) cluster at a maximum of 2000MHz and the
>> second (Cortex-A76) cluster at a maximum of 2200MHz.
>>
>> In order to calculate the right capacity-dmips-mhz, the following
>> test was performed:
>> 1. CPUFREQ governor was set to 'performance' on both clusters
>> 2. Ran dhrystone with 500000000 iterations for 10 times on each cluster
>> 3. Calculated the mean result for each cluster
>> 4. Calculated DMIPS/MHz: dmips_mhz = dmips_per_second / cpu_mhz
>> 5. Scaled results to 1024:
>>     result_c0 = dmips_mhz_c0 / dmips_mhz_c1 * 1024
>>
>> The mean results for this SoC are:
>> Cluster 0 (LITTLE): 12016411 Dhry/s
>> Cluster 1 (BIG): 31702034 Dhry/s
>>
>> The calculated scaled results are:
>> Cluster 0: 426.953226899238 (rounded to 427)
>> Cluster 1: 1024
>>
>> Fixes: 48489980e27e ("arm64: dts: Add Mediatek SoC MT8192 and evaluation board 
>> dts and Makefile")
>> Signed-off-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
>>
> 

Applied, thanks
> Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> 
> 

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-06-06  6:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-02 18:35 [PATCH] arm64: dts: mediatek: mt8192: Fix CPUs capacity-dmips-mhz Nícolas F. R. A. Prado
2023-06-02 18:35 ` Nícolas F. R. A. Prado
2023-06-05  8:21 ` AngeloGioacchino Del Regno
2023-06-05  8:21   ` AngeloGioacchino Del Regno
2023-06-06  6:38   ` Matthias Brugger [this message]
2023-06-06  6:38     ` Matthias Brugger
2023-06-06 13:00     ` Nícolas F. R. A. Prado
2023-06-06 13:00       ` Nícolas F. R. A. Prado
2023-06-07  6:54       ` Matthias Brugger
2023-06-07  6:54         ` Matthias Brugger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4b2fdd36-0871-ecc7-5d64-e088d7f51987@gmail.com \
    --to=matthias.bgg@gmail.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@collabora.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=nfraprado@collabora.com \
    --cc=robh+dt@kernel.org \
    --cc=seiya.wang@mediatek.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.