From: Zijun Hu <zijun.hu@oss.qualcomm.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
Zijun Hu <zijun_hu@icloud.com>,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] Bluetooth: btusb: Preparation for upcoming Qualcomm QCC2072 support
Date: Mon, 13 Jul 2026 18:23:39 +0800 [thread overview]
Message-ID: <a26a0640-2d2f-4bd7-9793-c20aeb6aaca8@oss.qualcomm.com> (raw)
In-Reply-To: <CABBYNZLYXEAqXrVfCxFtgYEU-gCZariPYiGbk3zES0tQ+4qSAQ@mail.gmail.com>
On 7/9/2026 9:46 PM, Luiz Augusto von Dentz wrote:
>> This series collects the btusb and devcoredump changes required by the
>> upcoming Qualcomm QCC2072 Bluetooth driver. None of them are QCC2072-
>> specific: they refactor btusb into a shape that can host vendor-specific
>> source files, and make a few coredump helpers reusable.
> I really this not a 'lets redesign btusb because our driver is not
> standard Bluetooth Class' kind of thing, we already have hdev->setup
> and other callbacks for vendor specific functionality, if you want
> more than that perhaps it needs to be become it own driver.
Sorry, the cover letter was misleading — this isn't a redesign, and the
QCC2072 driver does use the existing callbacks (hdev->setup, hdev->send, and
the recv hooks). The change to btusb_main.c is small (+67/-2):
https://lore.kernel.org/all/20260713-btusb_qcom-v1-1-39cabc0dd601@oss.qualcomm.com
The only reason for the file split is size: the Qualcomm code is ~3700 lines,
which I'd rather not add to btusb_main.c.
Please take a look — if you still think it warrants a standalone driver after
seeing it, I'm happy to discuss that.
prev parent reply other threads:[~2026-07-13 10:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 6:14 [PATCH 0/6] Bluetooth: btusb: Preparation for upcoming Qualcomm QCC2072 support Zijun Hu
2026-07-09 6:14 ` [PATCH 1/6] Bluetooth: coredump: Introduce and apply hci_devcd_state_name() Zijun Hu
2026-07-09 9:29 ` Bluetooth: btusb: Preparation for upcoming Qualcomm QCC2072 support bluez.test.bot
2026-07-09 6:14 ` [PATCH 2/6] Bluetooth: coredump: Allow drivers to pad dump header to fixed size Zijun Hu
2026-07-09 6:15 ` [PATCH 3/6] Bluetooth: btusb: Add an indirect recv_intr() hook to btusb_data Zijun Hu
2026-07-09 6:15 ` [PATCH 4/6] Bluetooth: btusb: Add wrappers btusb_recv_{event,acl}_hdev() Zijun Hu
2026-07-09 6:15 ` [PATCH 5/6] Bluetooth: btusb: Add a simple static btusb_prepare_reset() Zijun Hu
2026-07-09 6:15 ` [PATCH 6/6] Bluetooth: btusb: Build the driver from multiple source files Zijun Hu
2026-07-09 13:40 ` Luiz Augusto von Dentz
2026-07-13 10:06 ` Zijun Hu
2026-07-09 13:46 ` [PATCH 0/6] Bluetooth: btusb: Preparation for upcoming Qualcomm QCC2072 support Luiz Augusto von Dentz
2026-07-13 10:23 ` Zijun Hu [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=a26a0640-2d2f-4bd7-9793-c20aeb6aaca8@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