Re: [PATCH 6/6] Bluetooth: btusb: Build the driver from multiple source files

[Zijun Hu]

On 7/9/2026 9:40 PM, Luiz Augusto von Dentz wrote:
> Hi Zijun,
> 
> On Thu, Jul 9, 2026 at 2:15 AM Zijun Hu <zijun.hu@xxxxxxxxxxxxxxxx> wrote:
>> Allow the driver to include vendor-specific source files by:
>> - renaming btusb.c to btusb_main.c
>> - making btusb.o a composite object
> There is already support for including vendor-specific code, see btintel.c.

Agreed, but there are two kinds of vendor code:

So the layering I have in mind is:
btusb_main.c  ->  btusb_<vendor>.c  ->  bt<vendor>.c
- btusb_<vendor>.c: vendor USB-specific code, compiled into btusb.
- bt<vendor>.c: vendor transport-independent code, its own module (btintel.c).

One of my goals is to move the qualcomm code in btusb.c into a new
btusb_qcom.c, linked into the btusb module to keep the migration low-risk.

Does this split make sense to you, or would you prefer a different approach?