mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Kris Karas (Bug Reporting)" <bugs-a21@moonlit-rail.com>
To: Oleksandr Natalenko <oleksandr@natalenko.name>,
	Linux Bluetooth <linux-bluetooth@vger.kernel.org>,
	Linux Regressions <regressions@lists.linux.dev>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Basavaraj Natikar <Basavaraj.Natikar@amd.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
	Johan Hedberg <johan.hedberg@gmail.com>,
	Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
	Zach <zacheryvig@outlook.com>,
	Paul Menzel <pmenzel@molgen.mpg.de>,
	Bagas Sanjaya <bagasdotme@gmail.com>,
	Greg KH <gregkh@linuxfoundation.org>
Subject: Re: Regression: Inoperative bluetooth, Intel chipset, mainline kernel 6.6.2+
Date: Sun, 3 Dec 2023 13:46:36 -0500	[thread overview]
Message-ID: <808556e5-46b9-41fe-9aeb-2c4782fd5a66@moonlit-rail.com> (raw)
In-Reply-To: <2709774.mvXUDI8C0e@natalenko.name>

[ 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

      reply	other threads:[~2023-12-03 18:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ee109942-ef8e-45b9-8cb9-a98a787fe094@moonlit-rail.com>
2023-12-01  6:27 ` Bagas Sanjaya
2023-12-01  8:19   ` Kris Karas (Bug Reporting)
2023-12-01  8:27     ` Paul Menzel
2023-12-03 12:17     ` Oleksandr Natalenko
2023-12-03 18:46       ` Kris Karas (Bug Reporting) [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=808556e5-46b9-41fe-9aeb-2c4782fd5a66@moonlit-rail.com \
    --to=bugs-a21@moonlit-rail.com \
    --cc=Basavaraj.Natikar@amd.com \
    --cc=bagasdotme@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=oleksandr@natalenko.name \
    --cc=pmenzel@molgen.mpg.de \
    --cc=regressions@lists.linux.dev \
    --cc=zacheryvig@outlook.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®