[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20231018070506.65320-1-tianruidong@linux.alibaba.com>
Date: Wed, 18 Oct 2023 15:05:06 +0800
From: Ruidong Tian <tianruidong@...ux.alibaba.com>
To: linux-kernel@...r.kernel.org
Cc: james.clark@....com, coresight@...ts.linaro.org,
suzuki.poulose@....com, mike.leach@...aro.org,
alexander.shishkin@...ux.intel.com,
linux-arm-kernel@...ts.infradead.org,
Ruidong Tian <tianruidong@...ux.alibaba.com>
Subject: [PATCH] coresight: etm4x: Enable ETE device accessed via MMIO
The ETM4X driver now assume that all ETE as CPU system instructions
accessed device, in fact the ETE device on some machines also accessed
via MMIO.
Signed-off-by: Ruidong Tian <tianruidong@...ux.alibaba.com>
---
drivers/hwtracing/coresight/coresight-etm4x-core.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/hwtracing/coresight/coresight-etm4x-core.c b/drivers/hwtracing/coresight/coresight-etm4x-core.c
index 285539104bcc..ad298c9cc87e 100644
--- a/drivers/hwtracing/coresight/coresight-etm4x-core.c
+++ b/drivers/hwtracing/coresight/coresight-etm4x-core.c
@@ -1103,8 +1103,9 @@ static bool etm4_init_iomem_access(struct etmv4_drvdata *drvdata,
* with MMIO. But we cannot touch the OSLK until we are
* sure this is an ETM. So rely only on the TRCDEVARCH.
*/
- if ((devarch & ETM_DEVARCH_ID_MASK) != ETM_DEVARCH_ETMv4x_ARCH) {
- pr_warn_once("TRCDEVARCH doesn't match ETMv4 architecture\n");
+ if ((devarch & ETM_DEVARCH_ID_MASK) != ETM_DEVARCH_ETMv4x_ARCH &&
+ (devarch & ETM_DEVARCH_ID_MASK) != ETM_DEVARCH_ETE_ARCH) {
+ pr_warn_once("TRCDEVARCH doesn't match ETMv4/ETE architecture\n");
return false;
}
--
2.33.1
Powered by blists - more mailing lists