From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: Ruidong Tian <tianruidong@linux.alibaba.com>,
linux-kernel@vger.kernel.org
Cc: james.clark@arm.com, coresight@lists.linaro.org,
mike.leach@linaro.org, alexander.shishkin@linux.intel.com,
linux-arm-kernel@lists.infradead.org,
Jay Chen <jkchen@linux.alibaba.com>
Subject: Re: [PATCH] coresight: etm4x: Add ACPI id for THEAD YiTian SOC
Date: Mon, 11 Sep 2023 10:21:17 +0100 [thread overview]
Message-ID: <3c326e7c-4f82-2f40-d92d-8928d8cf773b@arm.com> (raw)
In-Reply-To: <20230911072509.126063-1-tianruidong@linux.alibaba.com>
On 11/09/2023 08:25, Ruidong Tian wrote:
> From: Jay Chen <jkchen@linux.alibaba.com>
>
> Add support for detcting ETE device of THEAD YiTian SOC.
>
> Signed-off-by: Jay Chen <jkchen@linux.alibaba.com>
> Signed-off-by: Ruidong Tian <tianruidong@linux.alibaba.com>
> ---
> drivers/hwtracing/coresight/coresight-etm4x-core.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/hwtracing/coresight/coresight-etm4x-core.c b/drivers/hwtracing/coresight/coresight-etm4x-core.c
> index 77b0271ce6eb..329bb554b168 100644
> --- a/drivers/hwtracing/coresight/coresight-etm4x-core.c
> +++ b/drivers/hwtracing/coresight/coresight-etm4x-core.c
> @@ -2351,6 +2351,7 @@ static const struct of_device_id etm4_sysreg_match[] = {
> #ifdef CONFIG_ACPI
> static const struct acpi_device_id etm4x_acpi_ids[] = {
> {"ARMHC500", 0}, /* ARM CoreSight ETM4x */
> + {"BABA6000", 0 }, /* THEAD CoreSight ETE */
Why don't we use ARMHC500 for the ETE ? See :
https://developer.arm.com/documentation/den0067/latest/
Suzuki
> {}
> };
> MODULE_DEVICE_TABLE(acpi, etm4x_acpi_ids);
next prev parent reply other threads:[~2023-09-11 21:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 7:25 Ruidong Tian
2023-09-11 9:21 ` Suzuki K Poulose [this message]
2023-09-11 9:39 ` Sudeep Holla
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=3c326e7c-4f82-2f40-d92d-8928d8cf773b@arm.com \
--to=suzuki.poulose@arm.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=coresight@lists.linaro.org \
--cc=james.clark@arm.com \
--cc=jkchen@linux.alibaba.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.leach@linaro.org \
--cc=tianruidong@linux.alibaba.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®