public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Tanmay Vilas Kumar Jagdale <tanmay@marvell.com>
Cc: Tomasz Nowicki <tnowicki@marvell.com>,
	Jayachandran Chandrasekharan Nair <jnair@marvell.com>,
	Ganapatrao Kulkarni <gkulkarni@marvell.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"suzuki.poulose@arm.com" <suzuki.poulose@arm.com>
Subject: Re: coresight: Add ETM4.1 support for ThunderX2
Date: Mon, 19 Aug 2019 14:33:25 -0600	[thread overview]
Message-ID: <20190819203325.GB8268@xps15> (raw)
In-Reply-To: <1565877215-1331-1-git-send-email-tanmay@marvell.com>

Same comment as the previous patch along with the following...

On Thu, Aug 15, 2019 at 01:53:46PM +0000, Tanmay Vilas Kumar Jagdale wrote:
> Add ETM4.1 periperhal ID for Marvell's ThunderX2 chip.
> 
> Signed-off-by: Tanmay Jagdale <tanmay@marvell.com>
> ---
>  drivers/hwtracing/coresight/coresight-etm4x.c | 2 ++
>  drivers/hwtracing/coresight/coresight-etm4x.h | 1 +
>  2 files changed, 3 insertions(+)
> 
> diff --git a/drivers/hwtracing/coresight/coresight-etm4x.c b/drivers/hwtracing/coresight/coresight-etm4x.c
> index 7bcac8896fc1..ac3bd617907b 100644
> --- a/drivers/hwtracing/coresight/coresight-etm4x.c
> +++ b/drivers/hwtracing/coresight/coresight-etm4x.c
> @@ -58,6 +58,7 @@ static bool etm4_arch_supported(u8 arch)
>  	/* Mask out the minor version number */
>  	switch (arch & 0xf0) {
>  	case ETM_ARCH_V4:
> +	case ETM_ARCH_V4_1:

Why add ETM_ARCH_V4_1 when the switch statement strips off the first byte?

Look at[1], someone already added support for 4.2.

[1]. 5666dfd1d8a4 coresight: etm4x: Add support to enable ETMv4.2


>  		break;
>  	default:
>  		return false;
> @@ -1196,6 +1197,7 @@ static const struct amba_id etm4_ids[] = {
>  	CS_AMBA_ID(0x000bb95e),		/* Cortex-A57 */
>  	CS_AMBA_ID(0x000bb95a),		/* Cortex-A72 */
>  	CS_AMBA_ID(0x000bb959),		/* Cortex-A73 */
> +	CS_AMBA_ID(0x000cc0af),		/* Marvell ThunderX2 */

I suspect this processor also has "coresight-cpu-debug" IPs.  If that is the
case it is very possible they both have the same CID and a UCI (see next line)
is required.

>  	CS_AMBA_UCI_ID(0x000bb9da, uci_id_etm4),	/* Cortex-A35 */
>  	{},
>  };

Thanks,
Mathieu

> diff --git a/drivers/hwtracing/coresight/coresight-etm4x.h b/drivers/hwtracing/coresight/coresight-etm4x.h
> index 4523f10ddd0f..03369e56b2eb 100644
> --- a/drivers/hwtracing/coresight/coresight-etm4x.h
> +++ b/drivers/hwtracing/coresight/coresight-etm4x.h
> @@ -137,6 +137,7 @@
>  #define ETM_MAX_SS_CMP			8
>  
>  #define ETM_ARCH_V4			0x40
> +#define ETM_ARCH_V4_1			0x41
>  #define ETMv4_SYNC_MASK			0x1F
>  #define ETM_CYC_THRESHOLD_MASK		0xFFF
>  #define ETM_CYC_THRESHOLD_DEFAULT       0x100
> -- 
> 2.17.1
> 

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-08-19 20:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-15 13:53 coresight: Add ETM4.1 support for ThunderX2 Tanmay Vilas Kumar Jagdale
2019-08-19 20:33 ` Mathieu Poirier [this message]
2019-09-05 10:59   ` [EXT] " Tanmay Vilas Kumar Jagdale

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=20190819203325.GB8268@xps15 \
    --to=mathieu.poirier@linaro.org \
    --cc=gkulkarni@marvell.com \
    --cc=jnair@marvell.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=suzuki.poulose@arm.com \
    --cc=tanmay@marvell.com \
    --cc=tnowicki@marvell.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