From: Robin Murphy <robin.murphy@arm.com>
To: will@kernel.org, catalin.marinas@arm.com, robh+dt@kernel.org
Cc: mark.rutland@arm.com, suzuki.poulose@arm.com,
thierry.reding@gmail.com, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org
Subject: [PATCH 1/5] dt-bindings: arm: Catch up with Cortex/Neoverse CPUs again
Date: Tue, 7 Dec 2021 18:20:39 +0000 [thread overview]
Message-ID: <a36014d06d308c73d3fa1ed55e8967fb8adadf0d.1638900542.git.robin.murphy@arm.com> (raw)
In-Reply-To: <cover.1638900542.git.robin.murphy@arm.com>
Add bindings for the 2020 and 2021 cohorts of Cortex-A and Neoverse
CPUs, now featuring their Cortex-X cousins as well.
Signed-off-by: Robin Murphy <robin.murphy@arm.com>
---
Documentation/devicetree/bindings/arm/cpus.yaml | 6 ++++++
Documentation/devicetree/bindings/arm/pmu.yaml | 6 ++++++
2 files changed, 12 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/cpus.yaml b/Documentation/devicetree/bindings/arm/cpus.yaml
index 452bfd1d4ecc..e81dfb81230a 100644
--- a/Documentation/devicetree/bindings/arm/cpus.yaml
+++ b/Documentation/devicetree/bindings/arm/cpus.yaml
@@ -138,6 +138,8 @@ properties:
- arm,cortex-a76
- arm,cortex-a77
- arm,cortex-a78
+ - arm,cortex-a510
+ - arm,cortex-a710
- arm,cortex-m0
- arm,cortex-m0+
- arm,cortex-m1
@@ -146,8 +148,12 @@ properties:
- arm,cortex-r4
- arm,cortex-r5
- arm,cortex-r7
+ - arm,cortex-x1
+ - arm,cortex-x2
- arm,neoverse-e1
- arm,neoverse-n1
+ - arm,neoverse-n2
+ - arm,neoverse-v1
- brcm,brahma-b15
- brcm,brahma-b53
- brcm,vulcan
diff --git a/Documentation/devicetree/bindings/arm/pmu.yaml b/Documentation/devicetree/bindings/arm/pmu.yaml
index e17ac049e890..541a483ec8d7 100644
--- a/Documentation/devicetree/bindings/arm/pmu.yaml
+++ b/Documentation/devicetree/bindings/arm/pmu.yaml
@@ -44,8 +44,14 @@ properties:
- arm,cortex-a76-pmu
- arm,cortex-a77-pmu
- arm,cortex-a78-pmu
+ - arm,cortex-a510-pmu
+ - arm,cortex-a710-pmu
+ - arm,cortex-x1-pmu
+ - arm,cortex-x2-pmu
- arm,neoverse-e1-pmu
- arm,neoverse-n1-pmu
+ - arm,neoverse-n2-pmu
+ - arm,neoverse-v1-pmu
- brcm,vulcan-pmu
- cavium,thunder-pmu
- qcom,krait-pmu
--
2.28.0.dirty
next prev parent reply other threads:[~2021-12-07 18:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 18:20 [PATCH 0/5] arm64: DT binding/PMU updates Robin Murphy
2021-12-07 18:20 ` Robin Murphy [this message]
2021-12-08 18:12 ` [PATCH 1/5] dt-bindings: arm: Catch up with Cortex/Neoverse CPUs again Rob Herring
2021-12-07 18:20 ` [PATCH 2/5] arm64: perf: Simplify registration boilerplate Robin Murphy
2021-12-14 13:38 ` Mark Rutland
2021-12-07 18:20 ` [PATCH 3/5] arm64: perf: Support new DT compatibles Robin Murphy
2021-12-07 18:44 ` Mark Rutland
2021-12-07 19:14 ` Robin Murphy
2021-12-14 13:36 ` Mark Rutland
2021-12-07 18:20 ` [PATCH 4/5] dt-bindings: perf: Convert Arm DSU to schema Robin Murphy
2021-12-08 13:44 ` Rob Herring
2021-12-08 18:16 ` Rob Herring
2021-12-07 18:20 ` [PATCH 5/5] dt-bindings: perf: Add compatible for Arm DSU-110 Robin Murphy
2021-12-08 18:21 ` Rob Herring
2021-12-08 21:01 ` Robin Murphy
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=a36014d06d308c73d3fa1ed55e8967fb8adadf0d.1638900542.git.robin.murphy@arm.com \
--to=robin.murphy@arm.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=suzuki.poulose@arm.com \
--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).