From: patchwork-bot+bluetooth@kernel.org
To: Stephan Gerhold <stephan.gerhold@kernkonzept.com>
Cc: luiz.dentz@gmail.com, marcel@holtmann.org,
johan.hedberg@gmail.com, agross@kernel.org, andersson@kernel.org,
konrad.dybcio@linaro.org, linux-arm-msm@vger.kernel.org,
linux-bluetooth@vger.kernel.org, stephan@gerhold.net,
pmenzel@molgen.mpg.de
Subject: Re: [PATCH v2 RESEND] Bluetooth: btqcomsmd: Fix command timeout after setting BD address
Date: Fri, 10 Mar 2023 00:20:17 +0000 [thread overview]
Message-ID: <167840761794.25154.15476663413483482390.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230308133155.165537-1-stephan.gerhold@kernkonzept.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 8 Mar 2023 14:31:55 +0100 you wrote:
> On most devices using the btqcomsmd driver (e.g. the DragonBoard 410c
> and other devices based on the Qualcomm MSM8916/MSM8909/... SoCs)
> the Bluetooth firmware seems to become unresponsive for a while after
> setting the BD address. On recent kernel versions (at least 5.17+)
> this often causes timeouts for subsequent commands, e.g. the HCI reset
> sent by the Bluetooth core during initialization:
>
> [...]
Here is the summary with links:
- [v2,RESEND] Bluetooth: btqcomsmd: Fix command timeout after setting BD address
https://git.kernel.org/bluetooth/bluetooth-next/c/048379740637
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-03-10 0:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 13:31 [PATCH v2 RESEND] Bluetooth: btqcomsmd: Fix command timeout after setting BD address Stephan Gerhold
2023-03-10 0:20 ` patchwork-bot+bluetooth [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=167840761794.25154.15476663413483482390.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=johan.hedberg@gmail.com \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=pmenzel@molgen.mpg.de \
--cc=stephan.gerhold@kernkonzept.com \
--cc=stephan@gerhold.net \
/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