From: Robin Murphy <robin.murphy@arm.com>
To: Rob Herring <robh@kernel.org>, Thierry Reding <thierry.reding@gmail.com>
Cc: Jon Hunter <jonathanh@nvidia.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-tegra@vger.kernel.org, Mark Rutland <mark.rutland@arm.com>,
Will Deacon <will@kernel.org>
Subject: Re: [PATCH 2/2] arm64: tegra: Describe Tegra234 CPU hierarchy
Date: Mon, 29 Nov 2021 22:53:37 +0000 [thread overview]
Message-ID: <8ea071d7-a8ff-813a-6268-7445dbbf0c1a@arm.com> (raw)
In-Reply-To: <YaVAxNiU2O7kWXoQ@robh.at.kernel.org>
On 2021-11-29 21:06, Rob Herring wrote:
> On Fri, Nov 12, 2021 at 02:19:04PM +0100, Thierry Reding wrote:
>> From: Thierry Reding <treding@nvidia.com>
>>
>> The NVIDIA Tegra234 SoC has 3 clusters of 4 Cortex-A78AE CPU cores each,
>> for a total of 12 CPUs. Each CPU has 64 KiB instruction and data caches
>> with each cluster having an additional 256 KiB unified L2 cache and a 2
>> MiB L3 cache.
>>
>> Signed-off-by: Thierry Reding <treding@nvidia.com>
>> ---
>> arch/arm64/boot/dts/nvidia/tegra234.dtsi | 365 ++++++++++++++++++++++-
>> 1 file changed, 363 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/arm64/boot/dts/nvidia/tegra234.dtsi b/arch/arm64/boot/dts/nvidia/tegra234.dtsi
>> index 104e5fdd5f8a..db24f48edc9f 100644
>> --- a/arch/arm64/boot/dts/nvidia/tegra234.dtsi
>> +++ b/arch/arm64/boot/dts/nvidia/tegra234.dtsi
>> @@ -736,12 +736,373 @@ cpus {
>> #address-cells = <1>;
>> #size-cells = <0>;
>>
>> - cpu@0 {
>> + cpu0_0: cpu@0 {
>> + compatible = "arm,cortex-a78";
>> device_type = "cpu";
>> - reg = <0x000>;
>> + reg = <0x00000>;
>>
>> enable-method = "psci";
>> +
>
>> + i-cache-size = <65536>;
>> + i-cache-line-size = <64>;
>> + i-cache-sets = <256>;
>> + d-cache-size = <65536>;
>> + d-cache-line-size = <64>;
>> + d-cache-sets = <256>;
>
> Isn't all this discoverable?
No. The required parameters for cache maintenance by set/way are
discoverable from the CTR, and if you're particularly lucky they might
even happen to reflect the underlying physical cache structures, but
there's absolutely no guarantee of that, and there definitely exist
cases where they don't.
[...]
>> + pmu {
>> + compatible = "arm,armv8-pmuv3";
Oh, I'd missed this - per the current state of things, we should really
have a proper compatible for the PMU as well.
(Suggestions for ways to improve the current state of things for better
forward- and backward- compatibility welcome - I started having a mad
idea about autogenerating a PMU name from the CPU compatible if the
generic PMU compatible is present, but I'm not sure that's realistic).
Robin.
>> + interrupts = <GIC_PPI 7 IRQ_TYPE_LEVEL_HIGH>;
>> + status = "okay";
>
> That's the default.
>
>> };
>>
>> psci {
>> --
>> 2.33.1
>>
>>
next prev parent reply other threads:[~2021-11-29 22:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 13:19 [PATCH 1/2] dt-bindings: arm: cpus: Add ARM Cortex-A78 Thierry Reding
2021-11-12 13:19 ` [PATCH 2/2] arm64: tegra: Describe Tegra234 CPU hierarchy Thierry Reding
2021-11-29 21:06 ` Rob Herring
2021-11-29 22:53 ` Robin Murphy [this message]
2021-12-14 12:27 ` Thierry Reding
2021-11-12 13:39 ` [PATCH 1/2] dt-bindings: arm: cpus: Add ARM Cortex-A78 Robin Murphy
2021-11-29 21:06 ` Rob Herring
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=8ea071d7-a8ff-813a-6268-7445dbbf0c1a@arm.com \
--to=robin.murphy@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).