From: Zijun Hu <zijun.hu@oss.qualcomm.com>
To: Marcel Holtmann <marcel@holtmann.org>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Zijun Hu <zijun_hu@icloud.com>,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
Zijun Hu <zijun.hu@oss.qualcomm.com>
Subject: [PATCH v5 0/4] Bluetooth: btusb: Support Qualcomm multi-subsystem QCC2072
Date: Fri, 11 Sep 2026 01:00:00 -0700 [thread overview]
Message-ID: <20260911-btusb_qcc2072-v5-0-422754f4e938@oss.qualcomm.com> (raw)
Hi Luiz,
Thanks for the several rounds of review.
This revision has one minor fix plus a few inline comments addressing
false positives from the latest Sashiko review [1].
[1] https://sashiko.dev/#/patchset/20260910-btusb_qcc2072-v4-0-e78f04b7675e%40oss.qualcomm.com
Could you take a look at this new revision when you get a chance, and
let me know if you have any further comments?
Signed-off-by: Zijun Hu <zijun.hu@oss.qualcomm.com>
---
Changes in v5:
- Fix status masking in qperi_get_subsys_build_info()
- Add inline comments addressing Sashiko false positives
- Link to v4: https://patch.msgid.link/20260910-btusb_qcc2072-v4-0-e78f04b7675e@oss.qualcomm.com
Changes in v4:
- Fix memdump timeout blocking btusb_qcom_reset()
- Fix missing build information on driver rebind or resume
- Link to v3: https://patch.msgid.link/20260907-btusb_qcc2072-v3-0-1f65350b03b8@oss.qualcomm.com
Changes in v3:
- Remove socket option BT_RECV_VENDOR_PKT
- Fix heap overflow in hci_send_vendor_frame()
- Fix a stray NUL byte in the memdump file header
- Fix PM reference leak in btusb_do_reset_work()
- Don't mix goto with scoped_guard() in __qperi_tx_sync_evt()
- Don't mix goto with scoped_guard() in qperi_handle_evt()
- Prepare btusb_qcom for bulk serialization mode support.
- Link to v2: https://patch.msgid.link/20260830-btusb_qcc2072-v2-0-5c0e0c9dd98b@oss.qualcomm.com
---
Zijun Hu (4):
Bluetooth: btusb: Add recv_intr() hook to btusb_data
Bluetooth: Add generic support for vendor packets
Bluetooth: btusb: Build the driver from multiple source files
Bluetooth: btusb: Add support for Qualcomm multi-subsystem QCC2072
drivers/bluetooth/Kconfig | 14 +
drivers/bluetooth/Makefile | 3 +
drivers/bluetooth/{btusb.c => btusb_main.c} | 127 +-
drivers/bluetooth/btusb_qcom.c | 4556 +++++++++++++++++++++++++++
drivers/bluetooth/btusb_qcom.h | 99 +
include/net/bluetooth/hci_core.h | 5 +
include/net/bluetooth/hci_mon.h | 2 +
net/bluetooth/hci_core.c | 45 +
net/bluetooth/hci_sock.c | 8 +
9 files changed, 4857 insertions(+), 2 deletions(-)
---
base-commit: e40edfa049b967f0b9379bf549c59431302ad181
change-id: 20260910-btusb_qcc2072-7ad665e4560a
Best regards,
--
Zijun Hu <zijun.hu@oss.qualcomm.com>
next reply other threads:[~2026-09-11 8:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 8:00 Zijun Hu [this message]
2026-09-11 8:00 ` [PATCH v5 1/4] Bluetooth: btusb: Add recv_intr() hook to btusb_data Zijun Hu
2026-09-11 8:00 ` [PATCH v5 2/4] Bluetooth: Add generic support for vendor packets Zijun Hu
2026-09-11 8:00 ` [PATCH v5 3/4] Bluetooth: btusb: Build the driver from multiple source files Zijun Hu
2026-09-11 8:00 ` [PATCH v5 4/4] Bluetooth: btusb: Add support for Qualcomm multi-subsystem QCC2072 Zijun Hu
2026-09-11 19:56 ` Pauli Virtanen
2026-09-14 2:53 ` Zijun Hu
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=20260911-btusb_qcc2072-v5-0-422754f4e938@oss.qualcomm.com \
--to=zijun.hu@oss.qualcomm.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=zijun_hu@icloud.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®