[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <66ef3bf4-9550-94c7-f8ad-ee53d6c75025@huawei.com>
Date: Mon, 2 Apr 2018 22:24:41 +0800
From: Hanjun Guo <guohanjun@...wei.com>
To: Yisheng Xie <xieyisheng1@...wei.com>,
Neil Leeder <neil.m.leeder@...il.com>,
Will Deacon <will.deacon@....com>,
Mark Rutland <mark.rutland@....com>
CC: <linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
Mark Langsdorf <mlangsdo@...hat.com>,
Mark Salter <msalter@...hat.com>,
"Jon Masters" <jcm@...hat.com>, Timur Tabi <timur@...eaurora.org>,
Mark Brown <broonie@...nel.org>,
Agustin Vega-Frias <agustinv@...eaurora.org>
Subject: Re: [PATCH 2/2] perf: add arm64 smmuv3 pmu driver
On 2018/4/2 14:37, Yisheng Xie wrote:
> Hi Neil,
>
> On 2018/4/1 13:44, Neil Leeder wrote:
>> Hi Yisheng Xie,
>>
>> On 3/29/2018 03:03 AM, Yisheng Xie wrote:
>>>
>>> Hi Neil,
>>>
>>> On 2017/8/5 3:59, Neil Leeder wrote:
>>>> + mem_resource_0 = platform_get_resource(pdev, IORESOURCE_MEM, 0);
>>>> + mem_map_0 = devm_ioremap_resource(&pdev->dev, mem_resource_0);
>>>> +
>>> Can we use devm_ioremap instead? for the reg_base of smmu_pmu is
>>> IMPLEMENTATION DEFINED. If the reg of smmu_pmu is inside smmu,
>>> devm_ioremap_resource will failed and return -EBUSY, eg.:
>>>
>>> smmu reg ranges: 0x180000000 ~ 0x1801fffff
>>> its smmu_pmu reg ranges: 0x180001000 ~ 0x180001fff
>>>
>> Just to let you know that I no longer work at Qualcomm and I won't be able to provide updates to this patchset. I expect that others from my former team at Qualcomm will pick up ownership.
>
> Thanks for this infomation.
>
> hi Agustin and Timur,
>
> Is there any new status about this patchset?
I think we need to wait for the new version of IORT spec,
which includes the fix for the two base address for SMMUv3
PMCG (now just represent one).
Thanks
Hanjun
Powered by blists - more mailing lists