From: Hector Martin <marcan@marcan.st>
To: Rob Herring <robh@kernel.org>, Sven Peter <sven@svenpeter.dev>,
Alyssa Rosenzweig <alyssa@rosenzweig.io>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: asahi@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: apple: Add t600x L1/L2 cache properties and nodes
Date: Mon, 28 Nov 2022 20:57:34 +0900 [thread overview]
Message-ID: <9410ffc0-3bc0-028d-cf67-b67bc54ef600@marcan.st> (raw)
In-Reply-To: <20221122220619.659174-1-robh@kernel.org>
On 23/11/2022 07.06, Rob Herring wrote:
> The t600x CPU nodes are missing the cache hierarchy information. The
> cache hierarchy on Arm can not be detected and needs to be described in
> DT. The OS scheduler can make use of this information for scheduling
> decisions.
>
> The cache size information is based on various articles about the
> processors. There's also an L3 system level cache (SLC). It's not
> described here because SLCs typically have some MMIO interface which
> would need to be described.
>
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> Based on apple dts changes in linux-next.
>
> This fixes the warning: Unable to detect cache hierarchy for CPU %d
> ---
> arch/arm64/boot/dts/apple/t6002.dtsi | 51 +++++++++++++++++++++
> arch/arm64/boot/dts/apple/t600x-common.dtsi | 51 +++++++++++++++++++++
> 2 files changed, 102 insertions(+)
>
[...]
Applied to asahi-soc/dt, thanks!
I probably won't send this one up until the 6.3 cycle; I've rebased our
downstream bits/000-devicetree on top so it'll get some downstream
testing before going upstream (and in the meantime someone should get
around to adding these for the other chips too ;)).
Cheers,
- Hector
prev parent reply other threads:[~2022-11-28 11:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 22:06 [PATCH] arm64: dts: apple: Add t600x L1/L2 cache properties and nodes Rob Herring
2022-11-28 11:57 ` Hector Martin [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=9410ffc0-3bc0-028d-cf67-b67bc54ef600@marcan.st \
--to=marcan@marcan.st \
--cc=alyssa@rosenzweig.io \
--cc=asahi@lists.linux.dev \
--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=robh@kernel.org \
--cc=sven@svenpeter.dev \
/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).