From: Ben Dooks <ben.dooks@codethink.co.uk>
To: thierry.reding@gmail.com, jonathanh@nvidia.com,
rostedt@goodmis.org, mhiramat@kernel.org,
linux-tegra@vger.kernel.org
Cc: linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: two tegra drier tracing patches
Date: Mon, 16 Jun 2025 17:01:01 +0100 [thread overview]
Message-ID: <20250616160103.2105041-1-ben.dooks@codethink.co.uk> (raw)
I added some tracing to the tegra-mc and the bpmp driver which
the tegra-mc uses. This might be useful to other people so
sending these for review.
[PATCH 1/2] memory: tegra-mc: add tracepoints for tegra mc tracing
[PATCH 2/2] drivers/firware/tegra: add tracing to bpmp code
next reply other threads:[~2025-06-16 16:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 16:01 Ben Dooks [this message]
2025-06-16 16:01 ` [PATCH 1/2] memory: tegra-mc: add tracepoints for tegra mc tracing Ben Dooks
2025-06-16 16:01 ` [PATCH 2/2] drivers/firware/tegra: add tracing to bpmp code Ben Dooks
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=20250616160103.2105041-1-ben.dooks@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=thierry.reding@gmail.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