mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shuai Zhang <quic_shuaz@quicinc.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Bartosz Golaszewski <brgl@bgdev.pl>,
	Marcel Holtmann <marcel@holtmann.org>,
	Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
	<linux-arm-msm@vger.kernel.org>,
	<linux-bluetooth@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<stable@vger.kernel.org>, <quic_chejiang@quicinc.com>,
	<quic_jiaymao@quicinc.com>, <quic_chezhou@quicinc.com>
Subject: Re: [PATCH v1] Bluetooth: hci_qca: Fix SSR unable to wake up bug
Date: Wed, 5 Nov 2025 10:26:29 +0800	[thread overview]
Message-ID: <e9facb3e-1f35-46e4-a1d4-a377ecdb6d4a@quicinc.com> (raw)
In-Reply-To: <0c54ccc4-0526-4d7a-9ce3-42dde5539c7b@molgen.mpg.de>

Hi Paul

Thanks for the feedback!

On 11/4/2025 7:43 PM, Paul Menzel wrote:
> Dear Shuai,
> 
> 
> Thank you for your patch.
> 
> Am 04.11.25 um 12:26 schrieb Shuai Zhang:
>> During SSR data collection period, the processing of hw_error events
>> must wait until SSR data Collected or the timeout before it can proceed.
> 
> Collected → collected
> 
>> The wake_up_bit function has been added to address the issue
> 
> has been added → is added
> 
>> where hw_error events could only be processed after the timeout.
> 
> The problem is not totally clear to me. What is the current situation? Maybe start the commit message with that?
> 
>> The timeout unit has been changed from jiffies to milliseconds (ms).
> 
> Please give the numbers, and also document effect of this change. Is the timeout the same, or different?
> 
> Also, why not make that a separate commit?
> 
> Please document a test case.
> 

I’ll fix the grammar, add a commit message to describe the issue, 
include a test case, and use clear_and_wake_up_bit for atomicity.

Additionally, I will submit a new patch to explain the timeout unit issue.

>> Cc: stable@vger.kernel.org
>> Signed-off-by: Shuai Zhang <quic_shuaz@quicinc.com>
>> ---
>>   drivers/bluetooth/hci_qca.c | 4 +++-
>>   1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/bluetooth/hci_qca.c b/drivers/bluetooth/hci_qca.c
>> index 888176b0f..a2e3c97a8 100644
>> --- a/drivers/bluetooth/hci_qca.c
>> +++ b/drivers/bluetooth/hci_qca.c
>> @@ -1105,6 +1105,7 @@ static void qca_controller_memdump(struct work_struct *work)
>>                   cancel_delayed_work(&qca->ctrl_memdump_timeout);
>>                   clear_bit(QCA_MEMDUMP_COLLECTION, &qca->flags);
>>                   clear_bit(QCA_IBS_DISABLED, &qca->flags);
>> +                wake_up_bit(&qca->flags, QCA_MEMDUMP_COLLECTION);
>>                   mutex_unlock(&qca->hci_memdump_lock);
>>                   return;
>>               }
>> @@ -1182,6 +1183,7 @@ static void qca_controller_memdump(struct work_struct *work)
>>               qca->qca_memdump = NULL;
>>               qca->memdump_state = QCA_MEMDUMP_COLLECTED;
>>               clear_bit(QCA_MEMDUMP_COLLECTION, &qca->flags);
>> +            wake_up_bit(&qca->flags, QCA_MEMDUMP_COLLECTION);
> 
> `include/linux/wait_bit.h` also contains `clear_and_wake_up_bit()`.
> 
>>           }
>>             mutex_unlock(&qca->hci_memdump_lock);
>> @@ -1602,7 +1604,7 @@ static void qca_wait_for_dump_collection(struct hci_dev *hdev)
>>       struct qca_data *qca = hu->priv;
>>         wait_on_bit_timeout(&qca->flags, QCA_MEMDUMP_COLLECTION,
>> -                TASK_UNINTERRUPTIBLE, MEMDUMP_TIMEOUT_MS);
>> +                TASK_UNINTERRUPTIBLE, msecs_to_jiffies(MEMDUMP_TIMEOUT_MS));
>>         clear_bit(QCA_MEMDUMP_COLLECTION, &qca->flags);
>>   }
> 
> 
> Kind regards,
> 
> Paul

Kind regards,

Shuai



  reply	other threads:[~2025-11-05  2:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-04 11:26 Shuai Zhang
2025-11-04 11:43 ` Paul Menzel
2025-11-05  2:26   ` Shuai Zhang [this message]
2025-11-09 21:20 ` Dmitry Baryshkov

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=e9facb3e-1f35-46e4-a1d4-a377ecdb6d4a@quicinc.com \
    --to=quic_shuaz@quicinc.com \
    --cc=brgl@bgdev.pl \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=pmenzel@molgen.mpg.de \
    --cc=quic_chejiang@quicinc.com \
    --cc=quic_chezhou@quicinc.com \
    --cc=quic_jiaymao@quicinc.com \
    --cc=stable@vger.kernel.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®