From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Suzuki Kuruppassery Poulose <suzuki.poulose@arm.com>
Cc: Xiongfeng Wang <wangxiongfeng2@huawei.com>,
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>,
Anshuman Khandual <Anshuman.Khandual@arm.com>
Subject: Re: [Question] Question about supporting sysreg only CoreSight ETMv4.4 on ACPI machines
Date: Wed, 19 Oct 2022 09:46:40 +0100 [thread overview]
Message-ID: <Y0+5cESVK1LVXROj@shell.armlinux.org.uk> (raw)
In-Reply-To: <9fc5ab20-c7f0-a917-4938-403e3661109f@arm.com>
On Tue, Oct 18, 2022 at 10:18:08AM +0100, Suzuki Kuruppassery Poulose wrote:
> That is true. Unfortunately, supporting this requires us to move away from
> the AMBA framework (at least) for ETM4x devices. This is currently
> developed by Anshuman. We can share it as soon as this is complete.
Can we not find a way to create AMBA devices from ACPI?
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
_______________________________________________
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:[~2022-10-19 8:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 2:04 [Question] Question about supporting sysreg only CoreSight ETMv4.4 on ACPI machines Xiongfeng Wang
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) [this message]
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=Y0+5cESVK1LVXROj@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=Anshuman.Khandual@arm.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=wangxiongfeng2@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;
as well as URLs for NNTP newsgroup(s).