[PATCH 1/2] Bluetooth: btmtk: Add MT6639 (MT7927) Bluetooth support

[Sean Wang]

Hi, Javier

On Wed, Mar 25, 2026 at 7:23 PM Javier Tia <floss at jetm.me> wrote:
>
> Hi Sean,
>
> On Fri, Mar 7, 2026 Sean Wang wrote:
> > BT and WiFi use separate firmware.
> > I'm not sure why those WiFi sections are included in the binary.
> > Another concern is whether it is appropriate to upload the firmware
> > used in Windows to the linux-firmware repository,
> > The firmware files are probably intended for dedicated OEMs.
>
> The section filtering remains in v2 since the binary from the ASUS
> driver package does contain mixed BT+WiFi sections. The firmware
> upload question is being tracked separately in linux-firmware
> MR !946.
>
> On that topic - would it be possible for MediaTek to provide a
> proper BT firmware binary for linux-firmware, or to sign off on
> the one extracted from the ASUS driver package? That would resolve
> the firmware provenance concern. If a formal submission from
> MediaTek is required, could you help coordinate that?
>

Yes, this has been under internal coordination for some time already.
I also hope we can have a Linux-dedicated firmware binary rather than
relying on one extracted from a Windows driver package, as that would
be a cleaner upstream path.
For now, the practical step is to make the driver-side handling robust
and consistent first, so it is ready once the proper firmware is
available.

> > This is common logic for the other mediatek chips. It only takes
> > longer on the first power-on.
>
> [...]
>
> > If the firmware download is properly handled in
> > btmtk_setup_firmware_79xx, we don't need the extra bit.
>
> Understood. The BTMTK_FIRMWARE_LOADED flag and skip logic are
> removed in v2. Firmware persistence is handled by the existing
> framework as you suggested.
>

Good, it looks better after removing BTMTK_FIRMWARE_LOADED flags

> v2 is sent with these changes addressed.
>
> Best,
> Javier