From: guohanjun@huawei.com (Hanjun Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] arm64 SMMUv3 PMU driver with IORT support
Date: Thu, 12 Oct 2017 18:58:33 +0800 [thread overview]
Message-ID: <59DF4AD9.2060903@huawei.com> (raw)
In-Reply-To: <67a696ad-98e9-d505-1d73-7246d2efc398@codeaurora.org>
On 2017/8/11 11:28, Leeder, Neil wrote:
> On 8/9/2017 9:26 PM, Hanjun Guo wrote:
>> > On 2017/8/9 23:48, Leeder, Neil wrote:
>>>>> >>>> drivers/perf/Kconfig | 9 +
>>>>> >>>> drivers/perf/Makefile | 1 +
>>>>> >>>> drivers/perf/arm_smmuv3_pmu.c | 823 ++++++++++++++++++++++++++++++++++++++++++
>>>>> >>>> include/acpi/actbl2.h | 9 +-
>>>> >>> Do you have the acpica support code? I'm currently
>>>> >>> working on SMMUv3 MSI support and I would like to test
>>>> >>> it with MSI support for PMCG as well.
>>> >> I don't have any code other than what was posted here.
>>> >> What additional ACPICA support code is needed?
>> >
>> > Sorry for not clear, I mean the acpica code for iASL and
>> > other tool: github.com/acpica/acpica.git
>> >
>> > With that code, I can compile my IORT table with PMCG node.
> Unfortunately it looks like I'm the first person from Qualcomm Datacenter
> Technologies to try to add something to ACPICA, which means I'll have to
> kick off an internal legal process which may take some time. Unless someone
> else wants to take a crack at it - and really, there's nothing more than is
> in the ARM IORT spec - it could be a while before I can do that.
Just a update, I sent a pull request to Bob for ACPICA changes,
please take a look:
https://github.com/acpica/acpica/pull/327
Thanks
Hanjun
next prev parent reply other threads:[~2017-10-12 10:58 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 19:59 [PATCH 0/2] arm64 SMMUv3 PMU driver with IORT support Neil Leeder
2017-08-04 19:59 ` [PATCH 1/2] acpi: arm64: add iort support for PMCG Neil Leeder
2017-08-07 11:17 ` Robin Murphy
2017-08-07 20:52 ` Leeder, Neil
2017-08-07 16:44 ` Lorenzo Pieralisi
2017-08-07 21:00 ` Leeder, Neil
2018-01-30 10:39 ` Shameerali Kolothum Thodi
2018-01-30 18:00 ` Lorenzo Pieralisi
2018-01-31 12:10 ` Shameerali Kolothum Thodi
2018-01-31 12:34 ` Lorenzo Pieralisi
2017-08-04 19:59 ` [PATCH 2/2] perf: add arm64 smmuv3 pmu driver Neil Leeder
2017-08-07 14:31 ` Robin Murphy
2017-08-07 21:18 ` Leeder, Neil
2017-12-05 5:01 ` Linu Cherian
2018-03-29 7:03 ` Yisheng Xie
[not found] ` <e55ab4404143ea0b3cc4795a93e37480@codeaurora.org>
2018-04-01 5:44 ` Neil Leeder
2018-04-02 6:37 ` Yisheng Xie
2018-04-02 14:24 ` Hanjun Guo
2018-04-02 17:59 ` Neil Leeder
2018-04-03 1:15 ` Hanjun Guo
2018-04-04 11:35 ` Lorenzo Pieralisi
2018-05-02 14:20 ` Agustin Vega-Frias
2018-05-03 9:22 ` Shameerali Kolothum Thodi
2018-04-18 11:05 ` Shameerali Kolothum Thodi
2018-04-19 1:17 ` Yisheng Xie
2017-08-09 7:56 ` [PATCH 0/2] arm64 SMMUv3 PMU driver with IORT support Hanjun Guo
2017-08-09 15:48 ` Leeder, Neil
2017-08-10 1:26 ` Hanjun Guo
2017-08-11 3:28 ` Leeder, Neil
2017-10-12 10:58 ` Hanjun Guo [this message]
2017-10-12 11:05 ` Lorenzo Pieralisi
2017-10-12 11:11 ` Hanjun Guo
2017-10-31 23:33 ` Yury Norov
2017-11-02 20:38 ` Leeder, Neil
2017-12-10 2:35 ` Linu Cherian
2017-12-18 14:48 ` Robin Murphy
2017-12-18 15:39 ` Marc Zyngier
2017-12-19 6:55 ` Linu Cherian
2017-12-19 12:11 ` Marc Zyngier
2017-12-19 6:36 ` Linu Cherian
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=59DF4AD9.2060903@huawei.com \
--to=guohanjun@huawei.com \
--cc=linux-arm-kernel@lists.infradead.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).