Hi Marcel, Thank you for your review and suggestions. The MSFT extension has a HCI_VS_MSFT_Read_Supported_Features command. The AOSP extension has a read capability cmd too. https://docs.microsoft.com/en-us/windows-hardware/drivers/bluetooth/microsoft-defined-bluetooth-hci-commands-and-events#hci_vs_msft_read_supported_features https://source.android.com/devices/bluetooth/hci_requirements#vendor-specific-capabilities If commands did not support, the controller should feedback event status as Unknown HCI Command (0x01). We can go on this way. Regards, Hilda -----Original Message----- From: Marcel Holtmann <marcel@xxxxxxxxxxxx> Sent: Friday, October 1, 2021 5:42 PM To: Hilda Wu <hildawu@xxxxxxxxxxx> Cc: Johan Hedberg <johan.hedberg@xxxxxxxxx>; Luiz Augusto von Dentz <luiz.dentz@xxxxxxxxx>; linux-bluetooth@xxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; kai.heng.feng@xxxxxxxxxxxxx; apusaka@xxxxxxxxxxxx; Max Chou <max.chou@xxxxxxxxxxx>; alex_lu@xxxxxxxxxxxxxx; KidmanLee <kidman@xxxxxxxxxxx> Subject: Re: [PATCH] Bluetooth: btrtl: Ask ic_info to drop firmware Hi Hilda, > Some un-support wakeup platforms keep USB power and suspend signal is > coming late, this makes Realtek some chip keep its firmware, and make > it never load new firmware. > > So use vendor specific HCI command to ask them drop its firmware after > system shutdown or resume. > > Signed-off-by: Hilda Wu <hildawu@xxxxxxxxxxx> > --- > drivers/bluetooth/btrtl.c | 12 +++++++----- > 1 file changed, 7 insertions(+), 5 deletions(-) patch has been applied to bluetooth-next tree. Btw. is there a simple way (via vendor HCI commands or similar) to tell which RTL device supports the MSFT or AOSP extensions. I rather have this done once and not keep hacking it over and over again. Regards Marcel ------Please consider the environment before printing this e-mail.
