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>,
Jennifer Dahm <jennifer.dahm@ni.com>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org,
Shawn Lin <shawn.lin@rock-chips.com>,
Kyle Roeschley <kyle.roeschley@ni.com>,
Avri Altman <avri.altman@wdc.com>,
Simon Horman <horms+renesas@verge.net.au>,
Ulf Hansson <ulf.hansson@linaro.org>
Subject: [PATCH v2 0/4] Add trace events for SD registers.
Date: Tue, 16 Apr 2019 12:32:53 -0600 [thread overview]
Message-ID: <20190416183257.247902-1-rrangel@chromium.org> (raw)
I am not able to make a single event class for all these registers. They
all have different struct sizes and different printf formats.
Thanks for the reviews!
Changes in v2:
- Made trace_sd_scr print out flags.
- Add BUILD_BUG_ON to make sure tracing stays in sync with structs.
- memcpy using sizeof(__entry->raw)
Raul E Rangel (4):
mmc: core: Add trace event for SD SCR response
mmc: core: Add trace event for SD SSR response
mmc: core: Add trace event for SD OCR response
mmc: core: Add trace event for CSD response
drivers/mmc/core/mmc.c | 4 +
drivers/mmc/core/sd.c | 10 ++
drivers/mmc/core/sd_ops.c | 6 ++
include/trace/events/mmc.h | 204 +++++++++++++++++++++++++++++++++++++
4 files changed, 224 insertions(+)
--
2.21.0.392.gf8f6787159e-goog
next 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 Raul E Rangel [this message]
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 ` [PATCH v2 2/4] mmc: core: Add trace event for SD SSR response Raul E Rangel
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-1-rrangel@chromium.org \
--to=rrangel@chromium.org \
--cc=avri.altman@wdc.com \
--cc=djkurtz@chromium.org \
--cc=hongjiefang@asrmicro.com \
--cc=horms+renesas@verge.net.au \
--cc=jennifer.dahm@ni.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=shawn.lin@rock-chips.com \
--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).