mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Xiongfeng Wang <wangxiongfeng2@huawei.com>
To: <suzuki.poulose@arm.com>
Cc: <yehaiyang2@hisilicon.com>,
	wanghuiqiang <wanghuiqiang@huawei.com>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>, <mark.rutland@arm.com>,
	"Catalin Marinas" <catalin.marinas@arm.com>
Subject: [Question] Question about supporting sysreg only CoreSight ETMv4.4 on ACPI machines
Date: Tue, 18 Oct 2022 10:04:16 +0800	[thread overview]
Message-ID: <6e85db13-a65f-d4c6-1b6b-660a94cb7060@huawei.com> (raw)

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

             reply	other threads:[~2022-10-18  2:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18  2:04 Xiongfeng Wang [this message]
2022-10-18  9:18 ` Suzuki Kuruppassery Poulose
2022-10-19  2:04   ` Xiongfeng Wang
2022-10-20 16:03     ` Suzuki K Poulose
2022-10-19  8:46   ` Russell King (Oracle)
2022-10-19  9:28     ` Suzuki K Poulose

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=6e85db13-a65f-d4c6-1b6b-660a94cb7060@huawei.com \
    --to=wangxiongfeng2@huawei.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=suzuki.poulose@arm.com \
    --cc=wanghuiqiang@huawei.com \
    --cc=yehaiyang2@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
all inboxes | Powered by JetHome®