From: John Garry <john.garry@huawei.com>
To: Will Deacon <will@kernel.org>
Cc: mark.rutland@arm.com, linuxarm@huawei.com,
linux-kernel@vger.kernel.org, qiangqing.zhang@nxp.com,
zhangshaokun@hisilicon.com, jolsa@redhat.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] drivers/perf: hisi: Add identifier sysfs file
Date: Wed, 15 Jul 2020 09:23:19 +0100 [thread overview]
Message-ID: <67db3c30-5aaf-ac17-0256-950494f5ba88@huawei.com> (raw)
In-Reply-To: <20200714083216.GD4516@willie-the-truck>
Hi Will,
>
> On Wed, Jun 17, 2020 at 09:05:11PM +0800, John Garry wrote:
>> To allow userspace to identify the specific implementation of the device,
>> add an "identifier" sysfs file.
>>
>> Encoding is as follows:
>> hi1620: 0x0 (aka hip08)
>> hi1630: 0x30
>>
>> Signed-off-by: John Garry <john.garry@huawei.com>
>
> I'm struggling a bit to track this. If you still think it's worth pursuing,
> please could you post a series with a cover-letter describing what this is
> for, a link to the userspace changes and then patches for all the PMU
> drivers that need updating?
There is no hi1630 userspace support yet.
So what I can do is post updated userspace support (including hi1630),
and then post kernel parts together for all drivers we could initially
support.
@Joakim, I'll pick your imx driver changes here, if you don't mind.
There was an RFC from you for the SMMUv3 PMU as
> well, and also some other "arm64" changes.
>
I hope to drop that RFC if an updated SMMUv3 spec helps us out.
Cheers,
John
_______________________________________________
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-07-15 8:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 13:05 [PATCH] drivers/perf: hisi: Add identifier sysfs file John Garry
2020-06-18 1:39 ` Joakim Zhang
2020-06-18 1:40 ` Shaokun Zhang
2020-06-18 9:18 ` John Garry
2020-07-14 8:32 ` Will Deacon
2020-07-15 8:23 ` John Garry [this message]
2020-07-15 8:28 ` Joakim Zhang
2020-07-15 8:30 ` Will Deacon
2020-10-01 8:34 ` John Garry
2020-09-01 10:18 ` Joakim Zhang
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=67db3c30-5aaf-ac17-0256-950494f5ba88@huawei.com \
--to=john.garry@huawei.com \
--cc=jolsa@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=qiangqing.zhang@nxp.com \
--cc=will@kernel.org \
--cc=zhangshaokun@hisilicon.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