From: Gokul krishna Krishnakumar <quic_gokukris@quicinc.com>
To: <linux-remoteproc@vger.kernel.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
<linux-kernel@vger.kernel.org>,
Trilok Soni <quic_tsoni@quicinc.com>,
Satya Durga Srinivasu Prabhala <quic_satyap@quicinc.com>,
Rajendra Nayak <quic_rjendra@quicinc.com>,
"Elliot Berman" <quic_eberman@quicinc.com>,
Guru Das Srinagesh <quic_gurus@quicinc.com>,
Sibi Sankar <quic_sibis@quicinc.com>,
Melody Olvera <quic_molvera@quicinc.com>,
Gokul krishna Krishnakumar <quic_gokukris@quicinc.com>
Subject: [PATCH v3 0/2] Add trace events for remoteproc
Date: Wed, 10 May 2023 11:05:02 -0700 [thread overview]
Message-ID: <cover.1683741283.git.quic_gokukris@quicinc.com> (raw)
Patches for introducing traces in remoteproc.
V3: Split the Patch to 2 as per suggestion from Mukesh, fixed format
error from v2.
V2: Moved the traces to common code from the qcom_pas driver as per
Bjorns review, fixed text as per Triloks suggestion, Updated QuiC
copyright to 2023.
[1]: https://lore.kernel.org/all/20230224165142.17745-2-quic_gokukris@quicinc.com/
Gokul krishna Krishnakumar (2):
remoteproc: Introduce traces for remoteproc events
remoteproc: qcom: Add remoteproc tracing
drivers/remoteproc/Makefile | 1 +
drivers/remoteproc/qcom_common.c | 37 ++++++++
drivers/remoteproc/qcom_q6v5.c | 9 ++
drivers/remoteproc/qcom_tracepoints.c | 12 +++
drivers/remoteproc/remoteproc_core.c | 8 ++
include/trace/events/rproc_qcom.h | 128 ++++++++++++++++++++++++++
6 files changed, 195 insertions(+)
create mode 100644 drivers/remoteproc/qcom_tracepoints.c
create mode 100644 include/trace/events/rproc_qcom.h
base-commit: 47f64e7ef95a58e5c56f2ec62cbadbe868661149
--
2.40.1
next reply other threads:[~2023-05-10 18:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 18:05 Gokul krishna Krishnakumar [this message]
2023-05-10 18:05 ` [PATCH v3 1/2] remoteproc: Introduce traces for remoteproc events Gokul krishna Krishnakumar
2023-05-22 14:35 ` Mukesh Ojha
2023-05-22 15:32 ` Mukesh Ojha
2023-07-15 21:33 ` Bjorn Andersson
2023-05-10 18:05 ` [PATCH v3 2/2] remoteproc: qcom: Add remoteproc tracing Gokul krishna Krishnakumar
2023-07-15 21:12 ` Bjorn Andersson
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=cover.1683741283.git.quic_gokukris@quicinc.com \
--to=quic_gokukris@quicinc.com \
--cc=andersson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=quic_eberman@quicinc.com \
--cc=quic_gurus@quicinc.com \
--cc=quic_molvera@quicinc.com \
--cc=quic_rjendra@quicinc.com \
--cc=quic_satyap@quicinc.com \
--cc=quic_sibis@quicinc.com \
--cc=quic_tsoni@quicinc.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
all inboxes | Powered by JetHome®