From: Robin Murphy <robin.murphy@arm.com>
To: will@kernel.org, catalin.marinas@arm.com, mark.rutland@arm.com
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] arm64 CPU DT binding updates
Date: Fri, 21 Feb 2020 16:04:55 +0000 [thread overview]
Message-ID: <cover.1582300927.git.robin.murphy@arm.com> (raw)
Hi all,
Since A55 and others are now starting to show up in upstream
DT postings, it seems high time to get these updated.
I haven't yet found the chance to sit down and go through the
time-consuming part of cross-referencing TRMs to fill out the
event maps, but it seems worth getting the fundamental definitions
in sooner rather than later to at least un-block DT authors.
Thanks,
Robin.
Robin Murphy (3):
dt-bindings: ARM: Add recent Cortex/Neoverse CPUs
dt-bindings: ARM: Add recent Cortex/Neoverse PMUs
arm64: perf: Support new DT compatibles
Documentation/devicetree/bindings/arm/cpus.yaml | 9 +++++++++
Documentation/devicetree/bindings/arm/pmu.yaml | 9 +++++++++
arch/arm64/kernel/perf_event.c | 8 ++++++++
3 files changed, 26 insertions(+)
--
2.23.0.dirty
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-02-21 16:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 16:04 Robin Murphy [this message]
2020-02-21 16:04 ` [PATCH 1/3] dt-bindings: ARM: Add recent Cortex/Neoverse CPUs Robin Murphy
2020-02-21 16:04 ` [PATCH 2/3] dt-bindings: ARM: Add recent Cortex/Neoverse PMUs Robin Murphy
2020-02-21 16:26 ` Rob Herring
2020-02-21 16:30 ` Robin Murphy
2020-02-21 16:04 ` [PATCH 3/3] arm64: perf: Support new DT compatibles Robin Murphy
2020-02-21 17:15 ` Mark Rutland
2020-02-21 17:49 ` Mark Rutland
2020-02-21 17:38 ` Andre Przywara
2020-02-21 17:51 ` Mark Rutland
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=cover.1582300927.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=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).