From: Mark Brown <broonie@kernel.org>
To: Praveen Talari <praveen.talari@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
Mukesh Kumar Savaliya <mukesh.savaliya@oss.qualcomm.com>,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: Re: [PATCH v2 2/2] spi: qcom-geni: add GENI SE registers trace event on error paths
Date: Mon, 13 Jul 2026 11:46:37 +0100 [thread overview]
Message-ID: <72cb70b0-d89d-405b-b2b9-807e028d6fd3@sirena.org.uk> (raw)
In-Reply-To: <4bcaa245-2127-45aa-bf05-48e275c0129c@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 1240 bytes --]
On Sat, Jul 11, 2026 at 08:21:02AM +0530, Praveen Talari wrote:
> On 11-07-2026 02:56, Mark Brown wrote:
> > On Sat, Jul 11, 2026 at 12:18:42AM +0530, Praveen Talari wrote:
> > > +#include <trace/events/qcom_geni_se.h>
> > Should this be in rivers/soc/qcom/qcom-geni-se.c (and the first patch?)
> > - that way if another driver starts using them we won't multiply define
> > the tracepoints.
> Yes, you are correct but
> If this header in drivers/soc/qcom/qcom-geni-se.c, how it will be access
> trace API in other drivers like i2c, spi and uart?
The header needs to be in the users but the CREATE_ define that you cut
needs to be in only one place to actually create the tracepoints.
> > > @@ -986,10 +997,13 @@ static irqreturn_t geni_spi_isr(int irq, void *data)
> > > writel(0, se->base + SE_GENI_TX_WATERMARK_REG);
> > > dev_err(mas->dev, "Premature done. tx_rem = %d bpw%d\n",
> > > mas->tx_rem_bytes, mas->cur_bits_per_word);
> > > + trace_geni_se_regs(se);
> > SE_GENI_TX_WATERMARK_REG is one of the registers in the tracepoint,
> > perhaps trace before we write to clear it?
> it will be captured in m_irq register so it is not required to capture.
Are you sure that won't lead to user confusion?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-07-13 10:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 18:48 [PATCH v2 0/2] Add trace event support for GENI SE registers dump Praveen Talari
2026-07-10 18:48 ` [PATCH v2 1/2] soc: qcom: geni-se: trace: " Praveen Talari
2026-07-11 15:54 ` Bjorn Andersson
2026-07-10 18:48 ` [PATCH v2 2/2] spi: qcom-geni: add GENI SE registers trace event on error paths Praveen Talari
2026-07-10 21:26 ` Mark Brown
2026-07-11 2:54 ` Praveen Talari
[not found] ` <4bcaa245-2127-45aa-bf05-48e275c0129c@oss.qualcomm.com>
2026-07-13 10:46 ` Mark Brown [this message]
2026-07-14 5:21 ` Praveen Talari
2026-07-14 10:24 ` Mark Brown
2026-07-14 15:34 ` Praveen Talari
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=72cb70b0-d89d-405b-b2b9-807e028d6fd3@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andersson@kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=mukesh.savaliya@oss.qualcomm.com \
--cc=praveen.talari@oss.qualcomm.com \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®