[PATCH] Bluetooth: btmtk: Remove resetting mt7921 before downloading the fw

[Thorsten Leemhuis]

Hi, Thorsten here, the Linux kernel's regression tracker. Top-posting
for once, to make this easily accessible to everyone.

I'm a bit lost here, but maybe I'm missing something.

Luiz, can you help out here? Is there a reason why this patch is not
making any process?

Chris Lu and/or Hao Qin: Can you maybe help out as well as well and help
with resolving some open questions that might or might not be relevant
(see below).

>From Takashi reply, the bugzilla ticket he linked to, and the mail from
the MediaTek folks
(https://lore.kernel.org/lkml/12a344e25b31ec00fe8b57814d43fcb166e71be5.camel@mediatek.com/
) it from the outside looks like this patch should really be merged
rather sooner that later as it fixes regressions for some people.
Afaics it should get a "Fixes: ccfc8948d7e4d9 ("Bluetooth: btusb:
mediatek: reset the controller before downloading the fw")" tag, as it's
afaics that commit that causes the regression that is known since more
than three months now
(https://lore.kernel.org/all/ZsTh7Jyug7MbZsLE@mdpsys.co.uk/ ).

But note, it seems it does not fix the regression completely according
to Marc's testing.
https://lore.kernel.org/all/ZuCB98DSdtKCgxaL@mdpsys.co.uk/

Marc: Is that still how things are with current mainline?

Ciao, Thorsten


On 22.10.24 12:56, Takashi Iwai wrote:
> On Mon, 14 Oct 2024 11:29:40 +0200,
> Linux regression tracking (Thorsten Leemhuis) wrote:
>>
>> On 20.09.24 08:27, Chris Lu (陸稚泓) wrote:
>>> On Thu, 2024-09-19 at 23:25 +0100, marc.payne at mdpsys.co.uk wrote:
>>>>  	 
>>>> External email : Please do not click links or open attachments until
>>>> you have verified the sender or the content.
>>>>  Hi Chris and Luiz,
>>>>
>>>> What were your thoughts on the findings in my email dated 18th
>>>> September?
>>>
>>> Thanks for your suggestion.
>>>
>>> I've prepared the same environment (Kernel v6.11 + MT7921AUN dongle) to
>>> reproduce the issue, collected necessary logs locally and also
>>> initiated an internal discussion to clarify the root cause of this
>>> symptom. We'll review the changes between two firmware
>>> (20230526/20231109) if it's a bug or not.
>>>
>>> It may take some time to investigate. I'll let you know if there is any
>>> progress.
>>
>> Just wondering: Chris Lu, and Marc, what's the status here? From here it
>> looks like there was no progress to fix this regression for a while, but
>> it's easy to miss something, that's why I ask.
>>
>> Ciao, Thorsten
> 
> FWIW, the similar bug was reported for the recent 6.11.x kernel on
> openSUSE Tumbleweed, and this patch was confirmed to work around the
> crash at boot:
>   https://bugzilla.suse.com/show_bug.cgi?id=1231599
> 
> It'd be great if you can go ahead and merge the proper fix to the
> upstream.
> 
> Let me know if you have another patch to test.  Then I can create a
> test kernel package and ask the bug reporter for testing.
> 
> 
> thanks,
> 
> Takashi
>