From: Bjorn Andersson <andersson@kernel.org>
To: Konrad Dybcio <konradybcio@kernel.org>,
Yuvaraj Ranganathan <yuvaraj.ranganathan@oss.qualcomm.com>
Cc: kernel@oss.qualcomm.com, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: Re: [PATCH v2 0/2] firmware: qcom: scm: add tracepoints for the SMC call interface
Date: Sat, 11 Jul 2026 11:40:42 -0500 [thread overview]
Message-ID: <178378800438.138068.7175582268598977713.b4-ty@kernel.org> (raw)
In-Reply-To: <20260522-scm-tracepoints-v2-0-e27cdbe0c585@oss.qualcomm.com>
On Fri, 22 May 2026 12:08:58 +0530, Yuvaraj Ranganathan wrote:
> The Qualcomm SCM driver is the sole gateway between the kernel and
> TrustZone firmware. When firmware issues manifest — unexpected error
> codes, calls that never return, or WAITQ sleep/resume cycles that stall
> — there is currently no low-overhead way to observe what the driver is
> doing without inserting temporary printk statements and rebuilding the
> kernel.
>
> [...]
Applied, thanks!
[1/2] firmware: qcom: scm: add trace events for the SMC call interface
commit: f6bb2daa4584229af155c2488b83151999315293
[2/2] firmware: qcom: scm: instrument SMC call path with tracepoints
commit: 41329e72363c02facfeae063ef304aa7ced68c3b
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2026-07-11 16:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 6:38 Yuvaraj Ranganathan
2026-05-22 6:38 ` [PATCH v2 1/2] firmware: qcom: scm: add trace events " Yuvaraj Ranganathan
2026-05-22 6:39 ` [PATCH v2 2/2] firmware: qcom: scm: instrument SMC call path with tracepoints Yuvaraj Ranganathan
2026-07-11 16:40 ` Bjorn Andersson [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=178378800438.138068.7175582268598977713.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=kernel@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yuvaraj.ranganathan@oss.qualcomm.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®