[PATCH v2 2/2] Bluetooth: mediatek: fix the conflict between mtk and msft vendor event
Marcel Holtmann
marcel at holtmann.org
Thu Feb 17 05:07:22 PST 2022
Hi Sean,
> There is a conflict between MediaTek wmt event and msft vendor extension
> logic in the core layer since 145373cb1b1f ("Bluetooth: Add framework for
> Microsoft vendor extension") was introduced because we changed the type of
> mediatek wmt event to the type of msft vendor event in the driver.
>
> But the purpose we reported mediatek event to the core layer is for the
> diagnostic purpose with that we are able to see the full packet trace via
> monitoring socket with btmon. Thus, it is harmless we keep the original
> type of mediatek vendor event here to avoid breaking the msft extension
> function especially they can be supported by Mediatek chipset like MT7921
> , MT7922 devices and future devices.
>
> Signed-off-by: Sean Wang <sean.wang at mediatek.com>
> ---
> v2: fix the warning: variable 'hdr' set but not used
> ---
> drivers/bluetooth/btmtk.h | 1 +
> drivers/bluetooth/btmtksdio.c | 9 +--------
> drivers/bluetooth/btusb.c | 8 --------
> 3 files changed, 2 insertions(+), 16 deletions(-)
patch has been applied to bluetooth-next tree.
Regards
Marcel
More information about the Linux-mediatek
mailing list