[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<172444383104.3074025.5017578776237520440.git-patchwork-notify@kernel.org>
Date: Fri, 23 Aug 2024 20:10:31 +0000
From: patchwork-bot+bluetooth@...nel.org
To: Doug Anderson <dianders@...omium.org>
Cc: marcel@...tmann.org, luiz.dentz@...il.com, groeck@...omium.org,
swboyd@...omium.org, johan+linaro@...nel.org, bartosz.golaszewski@...aro.org,
quic_saluvala@...cinc.com, linux-bluetooth@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [REPOST PATCH] Bluetooth: qca: If memdump doesn't work, re-enable IBS
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@...el.com>:
On Wed, 21 Aug 2024 15:43:40 -0700 you wrote:
> On systems in the field, we are seeing this sometimes in the kernel logs:
> Bluetooth: qca_controller_memdump() hci0: hci_devcd_init Return:-95
>
> This means that _something_ decided that it wanted to get a memdump
> but then hci_devcd_init() returned -EOPNOTSUPP (AKA -95).
>
> The cleanup code in qca_controller_memdump() when we get back an error
> from hci_devcd_init() undoes most things but forgets to clear
> QCA_IBS_DISABLED. One side effect of this is that, during the next
> suspend, qca_suspend() will always get a timeout.
>
> [...]
Here is the summary with links:
- [REPOST] Bluetooth: qca: If memdump doesn't work, re-enable IBS
https://git.kernel.org/bluetooth/bluetooth-next/c/61bea6923172
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists