Hi Zijun,
On Wed, Jul 20, 2022 at 7:07 AM Zijun Hu <[email protected]> wrote:
>
> Fake CSR BT controllers do not enable feature "Erroneous Data Reporting"
> currently, BT core driver will check the feature bit instead of the quirk
> to decide if HCI command HCI_Read|Write_Default_Erroneous_Data_Reporting
> work fine, so remove HCI_QUIRK_BROKEN_ERR_DATA_REPORTING for fake CSR.
>
> Signed-off-by: Zijun Hu <[email protected]>
> ---
> drivers/bluetooth/btusb.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
> index f0f86c5c3b37..f2b3d31d56cf 100644
> --- a/drivers/bluetooth/btusb.c
> +++ b/drivers/bluetooth/btusb.c
> @@ -2072,7 +2072,6 @@ static int btusb_setup_csr(struct hci_dev *hdev)
> * without these the controller will lock up.
> */
> set_bit(HCI_QUIRK_BROKEN_STORED_LINK_KEY, &hdev->quirks);
> - set_bit(HCI_QUIRK_BROKEN_ERR_DATA_REPORTING, &hdev->quirks);
> set_bit(HCI_QUIRK_BROKEN_FILTER_CLEAR_ALL, &hdev->quirks);
> set_bit(HCI_QUIRK_NO_SUSPEND_NOTIFIER, &hdev->quirks);
You will probably need to remove HCI_QUIRK_BROKEN_ERR_DATA_REPORTING
last otherwise it breaks the build in between patches, and please
double check if there are no other instances of driver using it or
perhaps leave it defined in case the feature is broken for some reason
but then we need a macro that checks both the quirk and the feature
bit.
> --
> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project
>
--
Luiz Augusto von Dentz
On 7/20/2022 11:38 PM, Luiz Augusto von Dentz wrote:
> Hi Zijun,
>
> On Wed, Jul 20, 2022 at 7:07 AM Zijun Hu <[email protected]> wrote:
>>
>> Fake CSR BT controllers do not enable feature "Erroneous Data Reporting"
>> currently, BT core driver will check the feature bit instead of the quirk
>> to decide if HCI command HCI_Read|Write_Default_Erroneous_Data_Reporting
>> work fine, so remove HCI_QUIRK_BROKEN_ERR_DATA_REPORTING for fake CSR.
>>
>> Signed-off-by: Zijun Hu <[email protected]>
>> ---
>> drivers/bluetooth/btusb.c | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
>> index f0f86c5c3b37..f2b3d31d56cf 100644
>> --- a/drivers/bluetooth/btusb.c
>> +++ b/drivers/bluetooth/btusb.c
>> @@ -2072,7 +2072,6 @@ static int btusb_setup_csr(struct hci_dev *hdev)
>> * without these the controller will lock up.
>> */
>> set_bit(HCI_QUIRK_BROKEN_STORED_LINK_KEY, &hdev->quirks);
>> - set_bit(HCI_QUIRK_BROKEN_ERR_DATA_REPORTING, &hdev->quirks);
>> set_bit(HCI_QUIRK_BROKEN_FILTER_CLEAR_ALL, &hdev->quirks);
>> set_bit(HCI_QUIRK_NO_SUSPEND_NOTIFIER, &hdev->quirks);
>
> You will probably need to remove HCI_QUIRK_BROKEN_ERR_DATA_REPORTING
> last otherwise it breaks the build in between patches, and please
> double check if there are no other instances of driver using it or
> perhaps leave it defined in case the feature is broken for some reason
> but then we need a macro that checks both the quirk and the feature
> bit.
>
okay, i will split this change to solve build error between patches.
yes. only QCA and CSR device with USB I/F use it. no other driver use it
the quirk was introduced to mark HCI_Read|Write_Default_Erroneous_Data_Reporting
broken, but the reason why these two HCI commands don't work fine is that the feature
"Erroneous Data Reporting" is not enabled by firmware.
so we need to check the feature bit instead of the quirk and don't also need the quirk.
>> --
>> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project
>>
>
>