[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <6e85db13-a65f-d4c6-1b6b-660a94cb7060@huawei.com>
Date: Tue, 18 Oct 2022 10:04:16 +0800
From: Xiongfeng Wang <wangxiongfeng2@...wei.com>
To: <suzuki.poulose@....com>
CC: <yehaiyang2@...ilicon.com>, wanghuiqiang <wanghuiqiang@...wei.com>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>, <mark.rutland@....com>,
"Catalin Marinas" <catalin.marinas@....com>
Subject: [Question] Question about supporting sysreg only CoreSight ETMv4.4 on
ACPI machines
Hi, Suzuki
We are testing CoreSight ETMv4.4 and TRBE recently. ETMv4.4 obsoletes memory
mapped access to ETM and mandates the system registers. The following commit add
driver for sysreg only devices, but it only support device tree.
commit 5214b563588e8414193bd7a174c52350256942a6
coresight: etm4x: Add support for sysreg only devices
ACPI machine can use 'ARMHC500' to report a ETM4x device. But the corresponding
driver is etm4x_amba_driver. It needs memory resouces and doesn't support sysreg
only device.
Do we have some other way to use CoreSight ETMv4.4 on ACPI machines. Thanks a lot.
Thanks,
Xiongfeng
Powered by blists - more mailing lists