devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Brugger <matthias.bgg@gmail.com>
To: AngeloGioacchino Del Regno  <angelogioacchino.delregno@collabora.com>
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	seiya.wang@mediatek.com, tinghan.shen@mediatek.com,
	allen-kh.cheng@mediatek.com, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] Fix MT8186/92/95 topology and idle state names
Date: Tue, 31 Jan 2023 12:42:36 +0100	[thread overview]
Message-ID: <2a091926-653c-6deb-12b9-85ae5ecef8cc@gmail.com> (raw)
In-Reply-To: <20230126103526.417039-1-angelogioacchino.delregno@collabora.com>



On 26/01/2023 11:35, AngeloGioacchino Del Regno wrote:
> MT8186, MT8192 and MT8195 use ARM DynamIQ, which combines big and
> LITTLE cores in one single cluster! A two cluster topology is simply
> wrong in this case.
> 
> While at it, after some research, I've also noticed that the names
> assigned to the idle states are misleading, so I went on changing
> them to reflect the actual function.
> 
> The names change commits, unlike the CPU map ones, didn't get any
> Fixes tag, as naming changes aren't fixing anything that would be
> meaningful for functionality (it's cosmetic, nothing else).
> 
> AngeloGioacchino Del Regno (6):
>    arm64: dts: mt8195: Fix CPU map for single-cluster SoC
>    arm64: dts: mt8192: Fix CPU map for single-cluster SoC
>    arm64: dts: mt8186: Fix CPU map for single-cluster SoC
>    arm64: dts: mt8195: Change idle states names to reflect actual
>      function
>    arm64: dts: mt8186: Change idle states names to reflect actual
>      function
>    arm64: dts: mt8192: Change idle states names to reflect actual
>      function
> 

Whole series applied, thanks!
Matthias

>   arch/arm64/boot/dts/mediatek/mt8186.dtsi | 30 ++++++++++----------
>   arch/arm64/boot/dts/mediatek/mt8192.dtsi | 35 +++++++++++-------------
>   arch/arm64/boot/dts/mediatek/mt8195.dtsi | 34 +++++++++++------------
>   3 files changed, 46 insertions(+), 53 deletions(-)
> 

      parent reply	other threads:[~2023-01-31 11:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-26 10:35 [PATCH 0/6] Fix MT8186/92/95 topology and idle state names AngeloGioacchino Del Regno
2023-01-26 10:35 ` [PATCH 1/6] arm64: dts: mt8195: Fix CPU map for single-cluster SoC AngeloGioacchino Del Regno
2023-01-26 10:35 ` [PATCH 2/6] arm64: dts: mt8192: " AngeloGioacchino Del Regno
2023-01-26 10:35 ` [PATCH 3/6] arm64: dts: mt8186: " AngeloGioacchino Del Regno
2023-01-26 10:35 ` [PATCH 4/6] arm64: dts: mt8195: Change idle states names to reflect actual function AngeloGioacchino Del Regno
2023-01-26 10:35 ` [PATCH 5/6] arm64: dts: mt8186: " AngeloGioacchino Del Regno
2023-01-26 10:35 ` [PATCH 6/6] arm64: dts: mt8192: " AngeloGioacchino Del Regno
2023-01-31 11:42 ` 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=2a091926-653c-6deb-12b9-85ae5ecef8cc@gmail.com \
    --to=matthias.bgg@gmail.com \
    --cc=allen-kh.cheng@mediatek.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=devicetree@vger.kernel.org \
    --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=robh+dt@kernel.org \
    --cc=seiya.wang@mediatek.com \
    --cc=tinghan.shen@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).