[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <808556e5-46b9-41fe-9aeb-2c4782fd5a66@moonlit-rail.com>
Date: Sun, 3 Dec 2023 13:46:36 -0500
From: "Kris Karas (Bug Reporting)" <bugs-a21@...nlit-rail.com>
To: Oleksandr Natalenko <oleksandr@...alenko.name>,
Linux Bluetooth <linux-bluetooth@...r.kernel.org>,
Linux Regressions <regressions@...ts.linux.dev>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Basavaraj Natikar <Basavaraj.Natikar@....com>
Cc: Marcel Holtmann <marcel@...tmann.org>,
Johan Hedberg <johan.hedberg@...il.com>,
Luiz Augusto von Dentz <luiz.dentz@...il.com>,
Zach <zacheryvig@...look.com>,
Paul Menzel <pmenzel@...gen.mpg.de>,
Bagas Sanjaya <bagasdotme@...il.com>,
Greg KH <gregkh@...uxfoundation.org>
Subject: Re: Regression: Inoperative bluetooth, Intel chipset, mainline kernel
6.6.2+
[ Replying to both Oleksandr and Basavaraj ]
Oleksandr Natalenko wrote:
> Does passing `btusb.enable_autosuspend=N` via a kernel cmdline help? [1]
Yes, this works around the problem. Should be a good short-term
solution for those folks who need to wait for distro kernels to catch
up. Thanks.
Basavaraj Natikar wrote:
>> Can we enable RPM on specific controllers for AMD xHC 1.1
>> instead to cover all AMD xHC 1.1?
>>
>> Please find below the proposed changes and let me know if it is OK?
>
> sorry its
> pdev->device == 0x43f7
Thanks, Basavaraj! Yes, this fixes the problem on my hardware (by
making application of PM more selective). Running successfully at the
moment using your (pdev->device amended) patch.
Kris
Powered by blists - more mailing lists