Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Jeffrey Hugo <quic_jhugo@quicinc.com>
To: Gokul Sriram P <quic_gokulsri@quicinc.com>,
	<manivannan.sadhasivam@linaro.org>, <mhi@lists.linux.dev>,
	<linux-arm-msm@vger.kernel.org>
Cc: <quic_srichara@quicinc.com>, <quic_viswanat@quicinc.com>,
	<quic_gokulsri@quiconc.com>
Subject: Re: [PATCH 4/6] bus: mhi: dump debug registers in critical sections
Date: Mon, 29 Jul 2024 08:13:38 -0600	[thread overview]
Message-ID: <ca8c093a-15ee-08aa-453f-225ecfb01844@quicinc.com> (raw)
In-Reply-To: <b5903003-3b3f-4a00-a01c-916c91caea62@quicinc.com>

On 7/28/2024 11:47 PM, Gokul Sriram P wrote:
> 
> On 7/18/2024 9:55 PM, Jeffrey Hugo wrote:
>> On 7/18/2024 12:13 AM, Gokul Sriram Palanisamy wrote:
>>> --- a/include/linux/mhi.h
>>> +++ b/include/linux/mhi.h
>>> @@ -834,4 +834,9 @@ bool mhi_queue_is_full(struct mhi_device 
>>> *mhi_dev, enum dma_data_direction dir);
>>>    */
>>>   int mhi_get_channel_doorbell_offset(struct mhi_controller 
>>> *mhi_cntrl, u32 *chdb_offset);
>>>   +/**
>>> + * mhi_debug_reg_dump - dump MHI registers for debug purpose
>>> + * @mhi_cntrl: MHI controller
>>> + */
>>> +void mhi_debug_reg_dump(struct mhi_controller *mhi_cntrl);
>>>   #endif /* _MHI_H_ */
>>
>> NACK.  This is not used.
> mhi_debug_reg_dump - this is added in 3 places, mhi_fw_load_bhi( ), 
> mhi_fw_load_bhie( ) and mhi_download_rddm_image( ) to print error codes 
> on failure scenarios.

You add this to the MHI API and export it as a symbol.  Nothing outside 
MHI uses this.

  reply	other threads:[~2024-07-29 14:13 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-18  6:13 [PATCH 0/6] add improvements to mhi driver Gokul Sriram Palanisamy
2024-07-18  6:13 ` [PATCH 1/6] drivers: bus: mhi: Added shared-dma-pool support for mhi_dev Gokul Sriram Palanisamy
2024-07-18 16:17   ` Jeffrey Hugo
2024-07-28 13:41     ` Gokul Sriram P
2024-07-18  6:13 ` [PATCH 2/6] bus: mhi: add support to allocate rddm memory during crash time Gokul Sriram Palanisamy
2024-07-18 16:22   ` Jeffrey Hugo
2024-07-28 13:40     ` Gokul Sriram P
2024-07-28 20:21       ` Jeffrey Hugo
2024-07-18  6:13 ` [PATCH 3/6] bus: mhi: increase RDDM timeout Gokul Sriram Palanisamy
2024-07-18 16:23   ` Jeffrey Hugo
2024-07-28 13:41     ` Gokul Sriram P
2024-07-28 20:24       ` Jeffrey Hugo
2024-07-18  6:13 ` [PATCH 4/6] bus: mhi: dump debug registers in critical sections Gokul Sriram Palanisamy
2024-07-18 16:25   ` Jeffrey Hugo
2024-07-29  5:47     ` Gokul Sriram P
2024-07-29 14:13       ` Jeffrey Hugo [this message]
2024-07-18  6:13 ` [PATCH 5/6] bus: mhi: check for RDDM cookie set by device to indicate readiness Gokul Sriram Palanisamy
2024-07-18 16:25   ` Jeffrey Hugo
2024-07-28 13:41     ` Gokul Sriram P
2024-07-28 20:27       ` Jeffrey Hugo
2024-07-18  6:13 ` [PATCH 6/6] bus: mhi: change IRQ_HANDLED to IRQ_NONE in mhi_irq_handler Gokul Sriram Palanisamy
2024-07-18 16:29   ` Jeffrey Hugo
2024-07-28 13:41     ` Gokul Sriram P
2024-07-28 20:29       ` Jeffrey Hugo
2024-07-18 16:30 ` [PATCH 0/6] add improvements to mhi driver Jeffrey Hugo

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=ca8c093a-15ee-08aa-453f-225ecfb01844@quicinc.com \
    --to=quic_jhugo@quicinc.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=mhi@lists.linux.dev \
    --cc=quic_gokulsri@quicinc.com \
    --cc=quic_gokulsri@quiconc.com \
    --cc=quic_srichara@quicinc.com \
    --cc=quic_viswanat@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