From: Will Deacon <will@kernel.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Robin Murphy <robin.murphy@arm.com>,
catalin.marinas@arm.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 5/5] arm64: perf: Support new DT compatibles
Date: Fri, 28 Feb 2020 12:24:53 +0000 [thread overview]
Message-ID: <20200228122453.GD3275@willie-the-truck> (raw)
In-Reply-To: <20200228121712.GF36089@lakrids.cambridge.arm.com>
On Fri, Feb 28, 2020 at 12:17:13PM +0000, Mark Rutland wrote:
> On Fri, Feb 21, 2020 at 07:35:32PM +0000, Robin Murphy wrote:
> > Add support for matching the new PMUs. For now, this just wires them up
> > as generic PMUv3 such that people writing DTs for new SoCs can do the
> > right thing, and at least have architectural and raw events be usable.
> > We can come back and fill in event maps for sysfs and/or perf tools at
> > a later date.
> >
> > Signed-off-by: Robin Murphy <robin.murphy@arm.com>
>
> Thanks for putting this together!
>
> Acked-by: Mark Rutland <mark.rutland@arm.com>
>
> Will, are you happy to queue this and the previous patch?
Sure thing. I haven't queued anything for 5.7 yet, but I'll flag these
two so I don't forget.
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: catalin.marinas@arm.com, Robin Murphy <robin.murphy@arm.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 5/5] arm64: perf: Support new DT compatibles
Date: Fri, 28 Feb 2020 12:24:53 +0000 [thread overview]
Message-ID: <20200228122453.GD3275@willie-the-truck> (raw)
In-Reply-To: <20200228121712.GF36089@lakrids.cambridge.arm.com>
On Fri, Feb 28, 2020 at 12:17:13PM +0000, Mark Rutland wrote:
> On Fri, Feb 21, 2020 at 07:35:32PM +0000, Robin Murphy wrote:
> > Add support for matching the new PMUs. For now, this just wires them up
> > as generic PMUv3 such that people writing DTs for new SoCs can do the
> > right thing, and at least have architectural and raw events be usable.
> > We can come back and fill in event maps for sysfs and/or perf tools at
> > a later date.
> >
> > Signed-off-by: Robin Murphy <robin.murphy@arm.com>
>
> Thanks for putting this together!
>
> Acked-by: Mark Rutland <mark.rutland@arm.com>
>
> Will, are you happy to queue this and the previous patch?
Sure thing. I haven't queued anything for 5.7 yet, but I'll flag these
two so I don't forget.
Will
_______________________________________________
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:[~2020-02-28 12:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 19:35 [PATCH v2 0/5] arm64 CPU DT binding updates Robin Murphy
2020-02-21 19:35 ` Robin Murphy
2020-02-21 19:35 ` [PATCH v2 1/5] dt-bindings: ARM: Add recent Cortex/Neoverse CPUs Robin Murphy
2020-02-21 19:35 ` Robin Murphy
2020-02-25 19:00 ` Rob Herring
2020-02-25 19:00 ` Rob Herring
2020-02-21 19:35 ` [PATCH v2 2/5] dt-bindings: ARM: Add recent Cortex/Neoverse PMUs Robin Murphy
2020-02-21 19:35 ` Robin Murphy
2020-02-25 19:00 ` Rob Herring
2020-02-25 19:00 ` Rob Herring
2020-02-21 19:35 ` [PATCH v2 3/5] dt-bindings: ARM: Clean up PMU compatible list Robin Murphy
2020-02-21 19:35 ` Robin Murphy
2020-02-25 19:01 ` Rob Herring
2020-02-25 19:01 ` Rob Herring
2020-02-21 19:35 ` [PATCH v2 4/5] arm64: perf: Refactor PMU init callbacks Robin Murphy
2020-02-21 19:35 ` Robin Murphy
2020-02-28 12:15 ` Mark Rutland
2020-02-28 12:15 ` Mark Rutland
2020-02-21 19:35 ` [PATCH v2 5/5] arm64: perf: Support new DT compatibles Robin Murphy
2020-02-21 19:35 ` Robin Murphy
2020-02-28 12:17 ` Mark Rutland
2020-02-28 12:17 ` Mark Rutland
2020-02-28 12:24 ` Will Deacon [this message]
2020-02-28 12:24 ` Will Deacon
2020-03-02 11:54 ` Will Deacon
2020-03-02 11:54 ` Will Deacon
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=20200228122453.GD3275@willie-the-truck \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robin.murphy@arm.com \
/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.