diff options
| author | Sean Wang <sean.wang@mediatek.com> | 2022-02-08 21:17:41 +0300 |
|---|---|---|
| committer | Marcel Holtmann <marcel@holtmann.org> | 2022-03-04 18:10:50 +0300 |
| commit | e4412654e260842e1a94ffe0d4026e8a6fd34246 (patch) | |
| tree | 2ccdf47b00e8287a588f7dcb7583a3367ba602e4 /drivers/bluetooth/btmtk.h | |
| parent | 8fafe702253d50bf90daf324ae86b5ad5ac8a5e1 (diff) | |
| download | linux-e4412654e260842e1a94ffe0d4026e8a6fd34246.tar.xz | |
Bluetooth: mediatek: fix the conflict between mtk and msft vendor event
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@mediatek.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Diffstat (limited to 'drivers/bluetooth/btmtk.h')
| -rw-r--r-- | drivers/bluetooth/btmtk.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/bluetooth/btmtk.h b/drivers/bluetooth/btmtk.h index 8960a5f89d48..013850fd2055 100644 --- a/drivers/bluetooth/btmtk.h +++ b/drivers/bluetooth/btmtk.h @@ -5,6 +5,7 @@ #define FIRMWARE_MT7668 "mediatek/mt7668pr2h.bin" #define FIRMWARE_MT7961 "mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin" +#define HCI_EV_WMT 0xe4 #define HCI_WMT_MAX_EVENT_SIZE 64 #define BTMTK_WMT_REG_WRITE 0x1 |