public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Sizhe Liu <liusizhe5@huawei.com>
To: Yicong Yang <yangyccccc@gmail.com>,
	"Pradhan, Sanman" <sanman.pradhan@hpe.com>,
	"jonathan.cameron@huawei.com" <jonathan.cameron@huawei.com>
Cc: "alexander.shishkin@linux.intel.com"
	<alexander.shishkin@linux.intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	Sanman Pradhan <psanman@juniper.net>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Jie Zhan <zhanjie9@hisilicon.com>
Subject: Re: [PATCH v2 1/2] hwtracing: hisi_ptt: Propagate DMA reset timeout in trace_start()
Date: Mon, 20 Apr 2026 15:32:44 +0800	[thread overview]
Message-ID: <d558a593-ca12-4237-a9b0-5f20441c9d52@huawei.com> (raw)
In-Reply-To: <166964d1-2d16-43e8-b4d7-27b4a5e6286d@gmail.com>


On 2026/4/17 1:25, Yicong Yang wrote:
> +cc Suzuki and Sizhe..
>
> On 2026/4/15 01:25, Pradhan, Sanman wrote:
>> From: Sanman Pradhan <psanman@juniper.net>
>>
>> hisi_ptt_wait_dma_reset_done() discards the return value of
>> readl_poll_timeout_atomic(). If the DMA engine does not complete its
>> reset within the timeout, hisi_ptt_trace_start() proceeds to start
>> tracing regardless.
>>
>> Return a bool from hisi_ptt_wait_dma_reset_done(), consistent with the
>> other wait helpers in this driver. On timeout, log an error, de-assert
>> the reset bit, and return -ETIMEDOUT. Move ctrl->started to the
>> successful path so a failed start does not leave the trace marked as
>> active.
>>
>> Fixes: ff0de066b463 ("hwtracing: hisi_ptt: Add trace function support for HiSilicon PCIe Tune and Trace device")
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Sanman Pradhan <psanman@juniper.net>
> looks good to me.
>
> Reviewed-by: Yicong Yang <yangyccccc@gmail.com>
>
> I see the Suzuki has sent out the PR for 7.1, so this may wait after the merge window...
>
> thanks.

Looks good to me, thanks.

Reviewed-by: Sizhe Liu <liusizhe5@huawei.com>

>> ---
>> v2:
>>    - Return bool for consistency with other wait helpers
>>    - Add pci_err() on timeout
>>    - De-assert RST before returning on timeout
>>    - Move ctrl->started to the successful path
>>
>>   drivers/hwtracing/ptt/hisi_ptt.c | 20 +++++++++++++-------
>>   1 file changed, 13 insertions(+), 7 deletions(-)
>>
>> diff --git a/drivers/hwtracing/ptt/hisi_ptt.c b/drivers/hwtracing/ptt/hisi_ptt.c
>> index 94c371c491357..b5d851281fbf0 100644
>> --- a/drivers/hwtracing/ptt/hisi_ptt.c
>> +++ b/drivers/hwtracing/ptt/hisi_ptt.c
>> @@ -171,13 +171,13 @@ static bool hisi_ptt_wait_trace_hw_idle(struct hisi_ptt *hisi_ptt)
>>   					  HISI_PTT_WAIT_TRACE_TIMEOUT_US);
>>   }
>>   
>> -static void hisi_ptt_wait_dma_reset_done(struct hisi_ptt *hisi_ptt)
>> +static bool hisi_ptt_wait_dma_reset_done(struct hisi_ptt *hisi_ptt)
>>   {
>>   	u32 val;
>>   
>> -	readl_poll_timeout_atomic(hisi_ptt->iobase + HISI_PTT_TRACE_WR_STS,
>> -				  val, !val, HISI_PTT_RESET_POLL_INTERVAL_US,
>> -				  HISI_PTT_RESET_TIMEOUT_US);
>> +	return !readl_poll_timeout_atomic(hisi_ptt->iobase + HISI_PTT_TRACE_WR_STS,
>> +					  val, !val, HISI_PTT_RESET_POLL_INTERVAL_US,
>> +					  HISI_PTT_RESET_TIMEOUT_US);
>>   }
>>   
>>   static void hisi_ptt_trace_end(struct hisi_ptt *hisi_ptt)
>> @@ -202,14 +202,18 @@ static int hisi_ptt_trace_start(struct hisi_ptt *hisi_ptt)
>>   		return -EBUSY;
>>   	}
>>   
>> -	ctrl->started = true;
>> -
>>   	/* Reset the DMA before start tracing */
>>   	val = readl(hisi_ptt->iobase + HISI_PTT_TRACE_CTRL);
>>   	val |= HISI_PTT_TRACE_CTRL_RST;
>>   	writel(val, hisi_ptt->iobase + HISI_PTT_TRACE_CTRL);
>>   
>> -	hisi_ptt_wait_dma_reset_done(hisi_ptt);
>> +	if (!hisi_ptt_wait_dma_reset_done(hisi_ptt)) {
>> +		pci_err(hisi_ptt->pdev, "timed out waiting for DMA reset\n");
>> +		val = readl(hisi_ptt->iobase + HISI_PTT_TRACE_CTRL);
>> +		val &= ~HISI_PTT_TRACE_CTRL_RST;
>> +		writel(val, hisi_ptt->iobase + HISI_PTT_TRACE_CTRL);
>> +		return -ETIMEDOUT;
>> +	}
>>   
>>   	val = readl(hisi_ptt->iobase + HISI_PTT_TRACE_CTRL);
>>   	val &= ~HISI_PTT_TRACE_CTRL_RST;
>> @@ -234,6 +238,8 @@ static int hisi_ptt_trace_start(struct hisi_ptt *hisi_ptt)
>>   	if (!hisi_ptt->trace_ctrl.is_port)
>>   		val |= HISI_PTT_TRACE_CTRL_FILTER_MODE;
>>   
>> +	ctrl->started = true;
>> +
>>   	/* Start the Trace */
>>   	val |= HISI_PTT_TRACE_CTRL_EN;
>>   	writel(val, hisi_ptt->iobase + HISI_PTT_TRACE_CTRL);

  reply	other threads:[~2026-04-20  7:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-14 17:25 [PATCH v2 0/2] hwtracing: hisi_ptt: Fix reset timeout handling and clean up trace start Pradhan, Sanman
2026-04-14 17:25 ` [PATCH v2 1/2] hwtracing: hisi_ptt: Propagate DMA reset timeout in trace_start() Pradhan, Sanman
2026-04-16 17:25   ` Yicong Yang
2026-04-20  7:32     ` Sizhe Liu [this message]
2026-04-14 17:25 ` [PATCH v2 2/2] hwtracing: hisi_ptt: Remove unnecessary trace buffer zeroing " Pradhan, Sanman
2026-04-17 12:45 ` [PATCH v2 0/2] hwtracing: hisi_ptt: Fix reset timeout handling and clean up trace start Jonathan Cameron

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=d558a593-ca12-4237-a9b0-5f20441c9d52@huawei.com \
    --to=liusizhe5@huawei.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=psanman@juniper.net \
    --cc=sanman.pradhan@hpe.com \
    --cc=stable@vger.kernel.org \
    --cc=suzuki.poulose@arm.com \
    --cc=yangyccccc@gmail.com \
    --cc=zhanjie9@hisilicon.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