From: Matthias Brugger <matthias.bgg@gmail.com>
To: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>
Cc: AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
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: Wed, 7 Jun 2023 08:54:33 +0200 [thread overview]
Message-ID: <9ec115dd-e419-ec4e-45f1-0865d703fd6a@gmail.com> (raw)
In-Reply-To: <0e9667dc-8f91-49a0-903e-6725204e11ad@notapiano>
On 06/06/2023 15:00, Nícolas F. R. A. Prado wrote:
> On Tue, Jun 06, 2023 at 08:38:42AM +0200, Matthias Brugger wrote:
>>
>>
>> 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
>
> Hi Matthias,
>
> this patch doesn't show in your v6.4-next/dts64 branch, while the other patch
> you just applied does, so I just wanted to double check it was really applied.
>
I forgot to push it, should be fixed now.
Regards,
Matthias
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-06-07 6:55 UTC|newest]
Thread overview: 5+ 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-05 8:21 ` AngeloGioacchino Del Regno
2023-06-06 6:38 ` Matthias Brugger
2023-06-06 13:00 ` Nícolas F. R. A. Prado
2023-06-07 6:54 ` Matthias Brugger [this message]
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=9ec115dd-e419-ec4e-45f1-0865d703fd6a@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).