From: Enric Balletbo i Serra <enric.balletbo@collabora.com>
To: Raul E Rangel <rrangel@chromium.org>, linux-trace-devel@vger.kernel.org
Cc: zwisler@chromium.org, djkurtz@chromium.org,
Ross Zwisler <zwisler@google.com>,
Steven Rostedt <rostedt@goodmis.org>,
Guenter Roeck <groeck@chromium.org>,
linux-kernel@vger.kernel.org, Benson Leung <bleung@chromium.org>
Subject: Re: [PATCH v6] platform/chrome: cros_ec: Add trace event to trace EC commands
Date: Tue, 23 Apr 2019 12:02:20 +0200 [thread overview]
Message-ID: <a966c393-70ed-48e9-988e-a869c670e25c@collabora.com> (raw)
In-Reply-To: <20190416210328.204078-1-rrangel@chromium.org>
On 16/4/19 23:03, Raul E Rangel wrote:
> This is useful to see which EC commands are being executed and when.
>
> To enable:
>
> echo 1 > /sys/kernel/debug/tracing/events/cros_ec/enable
>
> Example:
>
> /* cros_ec_cmd: version: 0, command: EC_CMD_GET_VERSION */
> /* cros_ec_cmd: version: 0, command: EC_CMD_GET_PROTOCOL_INFO */
> /* cros_ec_cmd: version: 1, command: EC_CMD_GET_CMD_VERSIONS */
> /* cros_ec_cmd: version: 1, command: EC_CMD_USB_PD_CONTROL */
>
> Signed-off-by: Raul E Rangel <rrangel@chromium.org>
> Reviewed-by: Ross Zwisler <zwisler@google.com>
> Reviewed-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
> ---
> I did not add cros_ec_commands.h as an include to cros_ec_trace.c.
> It's not strictly required because the macro doesn't get evaluated until
> after cros_ec_trace.h has been included. That transitively brings in
> cros_ec_ommands.h. I did try it, but since cros_ec_commands.h doesn't
> include linux/types.h it fails to find uint32_t. I could have included
> both headers, but since they aren't required I just skipped it.
>
> My reasoning for not putting EC_CMDS in the cros_ec_trace.h was that I
> didn't want to clutter the file. I think it's visually easier to find
> all the trace events without having to parse through all the
> implementation details.
>
> Changes in v6:
> - Added script to generate the EC_CMDS trace symbols. They were
> originally sorted by value, now they are sorted by declaration order.
> There is one duplicate: EC_CMD_PORT80_LAST_BOOT and
> EC_CMD_PORT80_READ. They both resolve to the same value. Not sure if
> this is a bug in the cros_ec_commands.h file or not. Anyway it doesn't
> hurt anything.
> - Changed the example in the commit
>
> Changes in v5:
> - Rebased on upstream/master. It turns out upstream/master is missing a
> lot of changes to cros_ec_commands.h.
> - Replace SYM with SYMBOL in macro name.
>
> Changes in v4:
> - Use the full command name so go to definition continues to work in my
> editor.
>
> Changes in v3:
> - Use a macro to avoid duplicating the ec command names.
>
> Changes in v2:
> - Changed comment style to match other cros_ec files.
> - Fixed commit tag.
>
> drivers/platform/chrome/Makefile | 5 +-
> drivers/platform/chrome/cros_ec_proto.c | 4 +
> drivers/platform/chrome/cros_ec_trace.c | 124 ++++++++++++++++++++++++
> drivers/platform/chrome/cros_ec_trace.h | 51 ++++++++++
> 4 files changed, 183 insertions(+), 1 deletion(-)
> create mode 100644 drivers/platform/chrome/cros_ec_trace.c
> create mode 100644 drivers/platform/chrome/cros_ec_trace.h
>
Tweaked a bit the commit message and applied for 5.2
Thanks,
Enric
prev parent reply other threads:[~2019-04-23 10:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 21:03 [PATCH v6] platform/chrome: cros_ec: Add trace event to trace EC commands Raul E Rangel
2019-04-23 10:02 ` Enric Balletbo i Serra [this message]
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=a966c393-70ed-48e9-988e-a869c670e25c@collabora.com \
--to=enric.balletbo@collabora.com \
--cc=bleung@chromium.org \
--cc=djkurtz@chromium.org \
--cc=groeck@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=rrangel@chromium.org \
--cc=zwisler@chromium.org \
--cc=zwisler@google.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;
as well as URLs for NNTP newsgroup(s).