From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Fei Shao <fshao@chromium.org>
Cc: Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 3/6] arm64: dts: mediatek: mt8188: Define CPU big core cluster
Date: Thu, 26 Sep 2024 10:33:38 +0200 [thread overview]
Message-ID: <fbdbe9ff-586a-429c-a987-b8ec39b485e8@collabora.com> (raw)
In-Reply-To: <20240925110044.3678055-4-fshao@chromium.org>
Il 25/09/24 12:57, Fei Shao ha scritto:
> The MT8188 SoC features two CPU clusters: one with 6 little Cortex-A55
> cores, and the other with 2 big Cortex-A78 cores.
No, it doesn't. It features only one cluster, so...
>
> Update the CPU topology to reflect the actual hardware configurations.
...the actual hardware configuration is already reflected by the currently
declared CPU topology, so for this commit: NAK.
This SoC uses the ARM DynamIQ technology and embeds both LITTLE and big
cores in one single cluster.
Check the MT8188 datasheet for more information :-)
Cheers,
Angelo
>
> Signed-off-by: Fei Shao <fshao@chromium.org>
> ---
>
> arch/arm64/boot/dts/mediatek/mt8188.dtsi | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/mediatek/mt8188.dtsi b/arch/arm64/boot/dts/mediatek/mt8188.dtsi
> index cd27966d2e3c..51bf08b2ff9b 100644
> --- a/arch/arm64/boot/dts/mediatek/mt8188.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt8188.dtsi
> @@ -195,12 +195,14 @@ core4 {
> core5 {
> cpu = <&cpu5>;
> };
> + };
>
> - core6 {
> + cluster1 {
> + core0 {
> cpu = <&cpu6>;
> };
>
> - core7 {
> + core1 {
> cpu = <&cpu7>;
> };
> };
next prev parent reply other threads:[~2024-09-26 8:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 10:57 [PATCH 0/6] MT8188 DT and binding fixes Fei Shao
2024-09-25 10:57 ` [PATCH 1/6] dt-bindings: power: mediatek: Add another nested power-domain layer Fei Shao
2024-09-25 10:57 ` [PATCH 2/6] dt-bindings: PCI: mediatek-gen3: Allow exact number of clocks only Fei Shao
2024-09-25 13:59 ` Krzysztof Kozlowski
2024-10-01 19:53 ` Bjorn Helgaas
2024-10-02 3:35 ` Fei Shao
2024-10-02 20:31 ` Bjorn Helgaas
2024-09-25 10:57 ` [PATCH 3/6] arm64: dts: mediatek: mt8188: Define CPU big core cluster Fei Shao
2024-09-26 8:33 ` AngeloGioacchino Del Regno [this message]
2024-09-26 10:41 ` Fei Shao
2024-09-25 10:57 ` [PATCH 4/6] arm64: dts: mediatek: mt8188: Add missing dma-ranges to soc node Fei Shao
2024-09-26 8:33 ` AngeloGioacchino Del Regno
2024-09-25 10:57 ` [PATCH 5/6] arm64: dts: mediatek: mt8188: Move vdec1 power domain under vdec0 Fei Shao
2024-09-26 8:33 ` AngeloGioacchino Del Regno
2024-09-26 10:42 ` Fei Shao
2024-09-30 9:35 ` Fei Shao
2024-09-25 10:57 ` [PATCH 6/6] arm64: dts: mediatek: mt8188: Update vppsys node names to syscon Fei Shao
2024-09-26 8:33 ` AngeloGioacchino Del Regno
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=fbdbe9ff-586a-429c-a987-b8ec39b485e8@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fshao@chromium.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
/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