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,
nfraprado@collabora.com, kernel@collabora.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/5] Add CPU caches information for some MediaTek SoCs
Date: Fri, 16 Dec 2022 12:53:13 +0100 [thread overview]
Message-ID: <06e969b5-3be2-4b23-de5a-93aa9ae6d95c@gmail.com> (raw)
In-Reply-To: <20221206112330.78431-1-angelogioacchino.delregno@collabora.com>
On 06/12/2022 12:23, AngeloGioacchino Del Regno wrote:
> In devicetrees for MediaTek SoCs the CPU caches information, if
> present, is incomplete as it misses cache size, cache line size
> and number of cache sets which, in turn, will also prevent any
> cache associativity calculation.
>
> For all of the SoCs that I know and/or I have information for,
> I've added the right information for I/D, L2 and L3 where present.
> This will also make the cacheinfo driver to correctly export the
> CPU cache information to sysfs.
>
Whole series applied, thanks!
> AngeloGioacchino Del Regno (5):
> arm64: dts: mt8195: Add complete CPU caches information
> arm64: dts: mt8192: Add complete CPU caches information
> arm64: dts: mt8186: Add complete CPU caches information
> arm64: dts: mt8183: Add complete CPU caches information
> arm64: dts: mt6795: Add complete CPU caches information
>
> arch/arm64/boot/dts/mediatek/mt6795.dtsi | 50 ++++++++++++++++
> arch/arm64/boot/dts/mediatek/mt8183.dtsi | 74 ++++++++++++++++++++++++
> arch/arm64/boot/dts/mediatek/mt8186.dtsi | 58 +++++++++++++++++++
> arch/arm64/boot/dts/mediatek/mt8192.dtsi | 58 +++++++++++++++++++
> arch/arm64/boot/dts/mediatek/mt8195.dtsi | 58 +++++++++++++++++++
> 5 files changed, 298 insertions(+)
>
WARNING: multiple messages have this Message-ID (diff)
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,
nfraprado@collabora.com, kernel@collabora.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/5] Add CPU caches information for some MediaTek SoCs
Date: Fri, 16 Dec 2022 12:53:13 +0100 [thread overview]
Message-ID: <06e969b5-3be2-4b23-de5a-93aa9ae6d95c@gmail.com> (raw)
In-Reply-To: <20221206112330.78431-1-angelogioacchino.delregno@collabora.com>
On 06/12/2022 12:23, AngeloGioacchino Del Regno wrote:
> In devicetrees for MediaTek SoCs the CPU caches information, if
> present, is incomplete as it misses cache size, cache line size
> and number of cache sets which, in turn, will also prevent any
> cache associativity calculation.
>
> For all of the SoCs that I know and/or I have information for,
> I've added the right information for I/D, L2 and L3 where present.
> This will also make the cacheinfo driver to correctly export the
> CPU cache information to sysfs.
>
Whole series applied, thanks!
> AngeloGioacchino Del Regno (5):
> arm64: dts: mt8195: Add complete CPU caches information
> arm64: dts: mt8192: Add complete CPU caches information
> arm64: dts: mt8186: Add complete CPU caches information
> arm64: dts: mt8183: Add complete CPU caches information
> arm64: dts: mt6795: Add complete CPU caches information
>
> arch/arm64/boot/dts/mediatek/mt6795.dtsi | 50 ++++++++++++++++
> arch/arm64/boot/dts/mediatek/mt8183.dtsi | 74 ++++++++++++++++++++++++
> arch/arm64/boot/dts/mediatek/mt8186.dtsi | 58 +++++++++++++++++++
> arch/arm64/boot/dts/mediatek/mt8192.dtsi | 58 +++++++++++++++++++
> arch/arm64/boot/dts/mediatek/mt8195.dtsi | 58 +++++++++++++++++++
> 5 files changed, 298 insertions(+)
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-12-16 11:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 11:23 [PATCH 0/5] Add CPU caches information for some MediaTek SoCs AngeloGioacchino Del Regno
2022-12-06 11:23 ` AngeloGioacchino Del Regno
2022-12-06 11:23 ` [PATCH 1/5] arm64: dts: mt8195: Add complete CPU caches information AngeloGioacchino Del Regno
2022-12-06 11:23 ` AngeloGioacchino Del Regno
2022-12-06 11:23 ` [PATCH 2/5] arm64: dts: mt8192: " AngeloGioacchino Del Regno
2022-12-06 11:23 ` AngeloGioacchino Del Regno
2022-12-06 11:23 ` [PATCH 3/5] arm64: dts: mt8186: " AngeloGioacchino Del Regno
2022-12-06 11:23 ` AngeloGioacchino Del Regno
2022-12-06 11:23 ` [PATCH 4/5] arm64: dts: mt8183: " AngeloGioacchino Del Regno
2022-12-06 11:23 ` AngeloGioacchino Del Regno
2022-12-06 11:23 ` [PATCH 5/5] arm64: dts: mt6795: " AngeloGioacchino Del Regno
2022-12-06 11:23 ` AngeloGioacchino Del Regno
2022-12-16 11:53 ` Matthias Brugger [this message]
2022-12-16 11:53 ` [PATCH 0/5] Add CPU caches information for some MediaTek SoCs 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=06e969b5-3be2-4b23-de5a-93aa9ae6d95c@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--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 \
/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.