From: Will Deacon <will@kernel.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: mark.rutland@arm.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, jialong.yang@shingroup.cn
Subject: Re: [PATCH 0/3] perf: Add Arm Network-on-Chip PMU driver
Date: Mon, 1 Jul 2024 14:36:12 +0100 [thread overview]
Message-ID: <20240701133611.GC2250@willie-the-truck> (raw)
In-Reply-To: <cover.1713972897.git.robin.murphy@arm.com>
Hi Robin,
On Thu, Apr 25, 2024 at 01:29:51PM +0100, Robin Murphy wrote:
>
> Somewhat later than hoped (sorry!), now that it's finally had the chance
> for enough testing to flush out all the silly bugs, here's the NI-700
> driver I've had kicking around in various forms for the last 18 months.
> I squashed in NI-710AE support since that appeared in the meantime and
> the differences are minimal, however I have not felt compelled to go
> back and genericise all the original NI-700 references. I don't think
> I'm giving too much away to say that there will be further new product
> support to add in future, so I will be back with more soon enough.
>
> Note that the driver patch depends on the the cpumask_any_and_but()
> addition queued in arm64/for-next/perf.
I left some minor comments on the driver code, but I think this probably
needs a respin anyway as the binding is still pending an Ack from the
DT folks.
Will
prev parent reply other threads:[~2024-07-01 13:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 12:29 [PATCH 0/3] perf: Add Arm Network-on-Chip PMU driver Robin Murphy
2024-04-25 12:29 ` [PATCH 1/3] dt-bindings/perf: Add Arm NI-700 PMU Robin Murphy
2024-04-25 12:34 ` Robin Murphy
2024-04-25 12:29 ` [PATCH 2/3] perf: Add driver for Arm NI-700 interconnect PMU Robin Murphy
2024-07-01 13:35 ` Will Deacon
2024-07-02 14:47 ` Robin Murphy
2024-04-25 12:29 ` [PATCH 3/3] MAINTAINERS: List Arm interconnect PMUs as supported Robin Murphy
2024-04-29 6:49 ` Ilkka Koskinen
2024-07-01 13:36 ` Will Deacon [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=20240701133611.GC2250@willie-the-truck \
--to=will@kernel.org \
--cc=jialong.yang@shingroup.cn \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox