From: Raul E Rangel <rrangel@chromium.org>
To: linux-mmc@vger.kernel.org, linux-trace-devel@vger.kernel.org
Cc: djkurtz@chromium.org, zwisler@chromium.org,
Raul E Rangel <rrangel@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
hongjiefang <hongjiefang@asrmicro.com>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org,
Kyle Roeschley <kyle.roeschley@ni.com>,
Avri Altman <avri.altman@wdc.com>,
Ulf Hansson <ulf.hansson@linaro.org>
Subject: [PATCH v2 2/4] mmc: core: Add trace event for SD SSR response
Date: Tue, 16 Apr 2019 12:32:55 -0600 [thread overview]
Message-ID: <20190416183257.247902-3-rrangel@chromium.org> (raw)
In-Reply-To: <20190416183257.247902-1-rrangel@chromium.org>
Example:
sd_ssr: mmc0: au: 8192, erase time: 0, erase offset: 0x0, raw: {0x0,0x3000000,0x1019000,0x10000,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0}
Signed-off-by: Raul E Rangel <rrangel@chromium.org>
---
drivers/mmc/core/sd.c | 2 ++
include/trace/events/mmc.h | 32 ++++++++++++++++++++++++++++++++
2 files changed, 34 insertions(+)
diff --git a/drivers/mmc/core/sd.c b/drivers/mmc/core/sd.c
index f1772972d6a3..908c3087cdcd 100644
--- a/drivers/mmc/core/sd.c
+++ b/drivers/mmc/core/sd.c
@@ -292,6 +292,8 @@ static int mmc_read_ssr(struct mmc_card *card)
card->erase_arg = (card->scr.sda_specx && discard_support) ?
SD_DISCARD_ARG : SD_ERASE_ARG;
+ trace_sd_ssr(card);
+
return 0;
}
diff --git a/include/trace/events/mmc.h b/include/trace/events/mmc.h
index 9761d3db16db..463cf318d762 100644
--- a/include/trace/events/mmc.h
+++ b/include/trace/events/mmc.h
@@ -61,6 +61,38 @@ TRACE_EVENT(sd_scr,
)
);
+TRACE_EVENT(sd_ssr,
+
+ TP_PROTO(struct mmc_card *card),
+
+ TP_ARGS(card),
+
+ TP_STRUCT__entry(
+ __array(u32, raw, 16)
+ __field(unsigned int, au)
+ __field(unsigned int, erase_timeout)
+ __field(unsigned int, erase_offset)
+ __string(name, mmc_hostname(card->host))
+ ),
+
+ TP_fast_assign(
+ BUILD_BUG_ON(sizeof(card->raw_ssr) != sizeof(__entry->raw));
+ memcpy(__entry->raw, card->raw_ssr, sizeof(__entry->raw));
+ __entry->au = card->ssr.au;
+ __entry->erase_timeout = card->ssr.erase_timeout;
+ __entry->erase_offset = card->ssr.erase_offset;
+ __assign_str(name, mmc_hostname(card->host));
+ ),
+
+ TP_printk("%s: au: %d, erase time: %d, erase offset: %#x, raw: %s",
+ __get_str(name),
+ __entry->au,
+ __entry->erase_timeout,
+ __entry->erase_offset,
+ __print_array(__entry->raw, 16, sizeof(u32))
+ )
+);
+
TRACE_EVENT(mmc_request_start,
TP_PROTO(struct mmc_host *host, struct mmc_request *mrq),
--
2.21.0.392.gf8f6787159e-goog
next prev parent reply other threads:[~2019-04-16 18:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 18:32 [PATCH v2 0/4] Add trace events for SD registers Raul E Rangel
2019-04-16 18:32 ` [PATCH v2 1/4] mmc: core: Add trace event for SD SCR response Raul E Rangel
2019-04-16 18:32 ` Raul E Rangel [this message]
2019-04-16 18:32 ` [PATCH v2 3/4] mmc: core: Add trace event for SD OCR response Raul E Rangel
2019-04-16 18:32 ` [PATCH v2 4/4] mmc: core: Add trace event for CSD response Raul E Rangel
2019-04-23 6:29 ` [PATCH v2 0/4] Add trace events for SD registers Ulf Hansson
2019-04-24 15:31 ` Raul Rangel
2019-04-29 9:57 ` Ulf Hansson
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=20190416183257.247902-3-rrangel@chromium.org \
--to=rrangel@chromium.org \
--cc=avri.altman@wdc.com \
--cc=djkurtz@chromium.org \
--cc=hongjiefang@asrmicro.com \
--cc=kyle.roeschley@ni.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=ulf.hansson@linaro.org \
--cc=zwisler@chromium.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).