From: leo.yan@linaro.org (Leo Yan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC 2/4] coresight: tmc: set read pointer before dump RAM
Date: Tue, 11 Apr 2017 17:10:27 +0800 [thread overview]
Message-ID: <1491901829-18477-3-git-send-email-leo.yan@linaro.org> (raw)
In-Reply-To: <1491901829-18477-1-git-send-email-leo.yan@linaro.org>
When dump RAM, we need set read pointer so can make sure every time read
the consistent content. If the RAM is full by checking status register
(STS), so set the read pointer to same value with write pointer,
otherwise set read point to 0 so can read from the start of RAM.
Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: Mike Leach <mike.leach@linaro.org>
Cc: Suzuki K Poulose <suzuki.poulose@arm.com>
Signed-off-by: Leo Yan <leo.yan@linaro.org>
---
drivers/hwtracing/coresight/coresight-tmc-etf.c | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/drivers/hwtracing/coresight/coresight-tmc-etf.c b/drivers/hwtracing/coresight/coresight-tmc-etf.c
index 6150dac..43cfeaa 100644
--- a/drivers/hwtracing/coresight/coresight-tmc-etf.c
+++ b/drivers/hwtracing/coresight/coresight-tmc-etf.c
@@ -43,10 +43,28 @@ static void tmc_etb_enable_hw(struct tmc_drvdata *drvdata)
static void tmc_etb_dump_hw(struct tmc_drvdata *drvdata)
{
+ u32 write_ptr, status;
char *bufp;
u32 read_data;
int i;
+ write_ptr = readl_relaxed(drvdata->base + TMC_RWP);
+
+ /*
+ * Get a hold of the status register and see if a wrap around
+ * has occurred. If so adjust things accordingly.
+ */
+ status = readl_relaxed(drvdata->base + TMC_STS);
+ if (status & TMC_STS_FULL)
+ /* Tell the HW the reading start point */
+ writel_relaxed(write_ptr, drvdata->base + TMC_RRP);
+ else
+ /*
+ * In case this is not first time to read ETB RAM,
+ * always write 0 for reading pointer.
+ */
+ writel_relaxed(0x0, drvdata->base + TMC_RRP);
+
bufp = drvdata->buf;
drvdata->len = 0;
while (1) {
--
2.7.4
next prev parent reply other threads:[~2017-04-11 9:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 9:10 [PATCH RFC 0/4] coresight: support dump ETB RAM Leo Yan
2017-04-11 9:10 ` [PATCH RFC 1/4] coresight: tmc: check dump buffer is overflow Leo Yan
2017-04-11 9:10 ` Leo Yan [this message]
2017-04-11 11:25 ` [PATCH RFC 2/4] coresight: tmc: set read pointer before dump RAM Chunyan Zhang
2017-04-11 13:46 ` Leo Yan
2017-04-11 9:10 ` [PATCH RFC 3/4] coresight: tmc: dump RAM when device is disabled Leo Yan
2017-04-11 9:10 ` [PATCH RFC 4/4] coresight: tmc: dump RAM for panic Leo Yan
2017-04-20 17:45 ` [PATCH RFC 0/4] coresight: support dump ETB RAM Mathieu Poirier
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=1491901829-18477-3-git-send-email-leo.yan@linaro.org \
--to=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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).