mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Praveen Talari <praveen.talari@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jirislaby@kernel.org>
Cc: chandana.chiluveru@oss.qualcomm.com,
	mukesh.savaliya@oss.qualcomm.com, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH] serial: qcom-geni: Add tracepoints for SE reg dump
Date: Mon, 26 Oct 2026 12:36:41 +0530	[thread overview]
Message-ID: <57158d21-44ca-4776-8fcf-313d583b340a@oss.qualcomm.com> (raw)
In-Reply-To: <2876c850-e2d0-4ee4-9d8f-50710c371a49@oss.qualcomm.com>

Hi Konrad,

On 23-10-2026 17:32, Konrad Dybcio wrote:
> On 10/19/26 5:32 AM, Praveen Talari wrote:
>> The GENI serial driver reports various transfer failures such as
>> M_CMD abort/cancel timeouts, DMA TX/RX FSM reset timeouts, RX FIFO
>> write errors, illegal command interrupts, and DMA parity errors.
>> However, diagnosing the root cause of these failures is difficult as
>> the hardware state is not captured when the error occurs.
>>
>> Add trace_geni_se_regs() calls at critical serial error handling paths
>> to automatically capture GENI serial engine debug registers when
>> failures are detected. This includes:
>>
>> - M_CMD abort/cancel timeout
>> - DMA TX/RX FSM reset timeout
>> - Unexpected zero-byte RX DMA completion
>> - RX FIFO write error and illegal command interrupt status
>> - RX DMA parity error
>>
>> Dumping the SE debug registers at the time of failure provides
>> additional hardware context and significantly improves post-mortem
>> analysis of serial transfer issues without affecting normal
>> operation.
>>
>> Signed-off-by: Praveen Talari <praveen.talari@oss.qualcomm.com>
>> ---
> The commit message should mention the additional logging changes
> too
Sure, will update in next patch.
>
> [...]
>
>> -	if (WARN_ON(m_irq_status & M_ILLEGAL_CMD_EN))
>> +	if (m_irq_status & M_ILLEGAL_CMD_EN) {
> if (WARN_ON(m_irq...))
Sure, will update in next patch.
>
> Konrad
>
>> +		trace_geni_se_regs(&port->se);
>> +		WARN_ON(1);
>>   		goto handle_rx;
>> +	}
>>   
>>   	if (dma) {
>>   		if (dma_tx_status & TX_DMA_DONE) {
>> @@ -1270,6 +1285,7 @@ static irqreturn_t qcom_geni_serial_isr(int isr, void *dev)
>>   			if (dma_rx_status & RX_DMA_PARITY_ERR) {
>>   				uport->icount.parity++;
>>   				drop_rx = true;
>> +				trace_geni_se_regs(&port->se);
>>   			}
>>   
>>   			if (dma_rx_status & RX_DMA_BREAK)
>>
>> ---
>> base-commit: 2efb7a11f1aa4d2dc285fe2680cca22cb9f72f64
>> change-id: 20260927-add-tracepoints-for-se-reg-dump-uart-30d93639447a
>>
>> Best regards,
>> --
>> Praveen Talari <praveen.talari@oss.qualcomm.com>

      reply	other threads:[~2026-10-26  7:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19  3:32 Praveen Talari
2026-10-23 12:02 ` Konrad Dybcio
2026-10-26  7:06   ` Praveen Talari [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=57158d21-44ca-4776-8fcf-313d583b340a@oss.qualcomm.com \
    --to=praveen.talari@oss.qualcomm.com \
    --cc=chandana.chiluveru@oss.qualcomm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=mukesh.savaliya@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®