From: patchwork-bot+bluetooth@kernel.org
To: Shuai Zhang <shuai.zhang@oss.qualcomm.com>
Cc: brgl@kernel.org, marcel@holtmann.org, luiz.dentz@gmail.com,
linux-arm-msm@vger.kernel.org, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, cheng.jiang@oss.qualcomm.com,
xiuzhuo.shang@oss.qualcomm.com, wei.deng@oss.qualcomm.com,
jinwang.li@oss.qualcomm.com
Subject: Re: [PATCH v4 0/2] Bluetooth: hci_qca: Reopen the UART after enabling QCA2066
Date: Tue, 10 Nov 2026 16:10:08 +0000 [thread overview]
Message-ID: <179432700817.4062787.1917987587860059113.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261110092929.234617-1-shuai.zhang@oss.qualcomm.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 10 Nov 2026 17:29:27 +0800 you wrote:
> QCA2066 does not reopen the UART after the controller is enabled, which
> causes RX/TX out-of-sync errors. The UART has to be reopened once the
> controller is powered on.
>
> qca_regulator_init() already enables the controller and then reopens the
> UART, but QCA2066 does not go through it. QCA2066 was added with its own
> SoC type and handled in the default case.
>
> [...]
Here is the summary with links:
- [v4,1/2] Bluetooth: hci_qca: Reopen the UART after enabling QCA2066
https://git.kernel.org/bluetooth/bluetooth-next/c/a57a255ce204
- [v4,2/2] Bluetooth: hci_qca: Don't use the serdev port after a failed reopen
https://git.kernel.org/bluetooth/bluetooth-next/c/45e28b01e4d0
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:[~2026-11-10 16:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 9:29 [PATCH v4 0/2] Bluetooth: hci_qca: Reopen the UART after enabling QCA2066 Shuai Zhang
2026-11-10 9:29 ` [PATCH v4 1/2] " Shuai Zhang
2026-11-10 11:21 ` bluez.test.bot
2026-11-10 13:52 ` [PATCH v4 1/2] " Bartosz Golaszewski
2026-11-10 9:29 ` [PATCH v4 2/2] Bluetooth: hci_qca: Don't use the serdev port after a failed reopen Shuai Zhang
2026-11-10 13:51 ` [PATCH v4 0/2] Bluetooth: hci_qca: Reopen the UART after enabling QCA2066 Bartosz Golaszewski
2026-11-10 16:10 ` 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=179432700817.4062787.1917987587860059113.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=brgl@kernel.org \
--cc=cheng.jiang@oss.qualcomm.com \
--cc=jinwang.li@oss.qualcomm.com \
--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=shuai.zhang@oss.qualcomm.com \
--cc=wei.deng@oss.qualcomm.com \
--cc=xiuzhuo.shang@oss.qualcomm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.