From: Paul Menzel <pmenzel@molgen.mpg.de>
To: 15013537245@163.com
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, zhongjun.yu@quectel.com,
Clancy Shang <clancy.shang@quectel.com>
Subject: Re: [PATCH] Bluetooth: hci_sync: fix hogp device suspend bug
Date: Thu, 21 Dec 2023 10:05:18 +0100 [thread overview]
Message-ID: <f7bf2cbf-0ff4-4d97-8d50-024ad1c9efec@molgen.mpg.de> (raw)
In-Reply-To: <20231221071621.1154462-1-15013537245@163.com>
Dear Clancy,
Thank you for your patch.
Am 21.12.23 um 08:16 schrieb 15013537245@163.com:
> From: clancy shang <clancy.shang@quectel.com>
Not important, but you might want to start your name with a capital letter.
> when Bluetooth enter suspend, and disconnect everything with the diconnect
1. enter*s*
2. disconnect*s*
3. … the di*s*connect …
> reason code of 0x15,the hogp device could not into sleep and continued
Please add a space after the comma.
> advertizing. when use the diconnect reason code of 0x13, the hogp device
1. adverti*s*ing
2. di*s*connect
> into sleep succeeded.
going into
What device is it exactly?
> Signed-off-by: clancy shang <clancy.shang@quectel.com>
> ---
> net/bluetooth/hci_sync.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/bluetooth/hci_sync.c b/net/bluetooth/hci_sync.c
> index d85a7091a116..16b5420c32d0 100644
> --- a/net/bluetooth/hci_sync.c
> +++ b/net/bluetooth/hci_sync.c
> @@ -5927,7 +5927,7 @@ int hci_suspend_sync(struct hci_dev *hdev)
>
> if (hci_conn_count(hdev)) {
> /* Soft disconnect everything (power off) */
> - err = hci_disconnect_all_sync(hdev, HCI_ERROR_REMOTE_POWER_OFF);
> + err = hci_disconnect_all_sync(hdev, HCI_ERROR_REMOTE_USER_TERM);
> if (err) {
> /* Set state to BT_RUNNING so resume doesn't notify */
> hdev->suspend_state = BT_RUNNING;
Kind regards,
Paul
next prev parent reply other threads:[~2023-12-21 9:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 7:16 15013537245
2023-12-21 9:05 ` Paul Menzel [this message]
2023-12-26 6:08 clancy_shang
2023-12-26 15:40 ` Luiz Augusto von Dentz
2024-01-03 10:12 clancy_shang
2024-01-03 15:55 ` Luiz Augusto von Dentz
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=f7bf2cbf-0ff4-4d97-8d50-024ad1c9efec@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=15013537245@163.com \
--cc=clancy.shang@quectel.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=zhongjun.yu@quectel.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®