[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <c38fe636-f3c3-5465-ebc4-70decca84675@gmail.com>
Date: Sun, 27 Nov 2022 00:26:46 +0100
From: Ismael Ferreras Morezuelas <swyterzone@...il.com>
To: Luiz Augusto von Dentz <luiz.dentz@...il.com>
Cc: marcel@...tmann.org, johan.hedberg@...il.com, davem@...emloft.net,
edumazet@...gle.com, kuba@...nel.org, luiz.von.dentz@...el.com,
quic_zijuhu@...cinc.com, hdegoede@...hat.com,
linux-kernel@...r.kernel.org, linux-bluetooth@...r.kernel.org,
netdev@...r.kernel.org, Jack <ostroffjh@...rs.sourceforge.net>,
Paul Menzel <pmenzel@...gen.mpg.de>, swyterzone@...il.com
Subject: Re: [PATCH 3/3] Bluetooth: btusb: Add a parameter to let users
disable the fake CSR force-suspend hack
On 09/11/2022 23:39, Luiz Augusto von Dentz wrote:
> I see, but for suspend in particular, can't we actually handle it
> somehow? I mean if we can detect the controller is getting stuck and
> print some information and flip the quirk? Otherwise Im afraid this
> parameter will end up always being set by distros to avoid suspend
> problems.
Hi, Luiz. I haven't seen any movement about the [3/3] patch since a few weeks ago.
Given what Hans clarified in his reply, I wondered if you or any of the other
Bluetooth maintainers have changed opinions about including this in some form.
I'm a kernel development newbie, so I'm not good at this. I don't know if I should
do anything else, wait a bit more, or just drop this. Thanks in advance. :)
Powered by blists - more mailing lists