From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Basavaraj Natikar <bnatikar@amd.com>, gregkh@linuxfoundation.org
Cc: linux-usb@vger.kernel.org, linux-bluetooth@vger.kernel.org,
mario.limonciello@amd.com, regressions@lists.linux.dev,
regressions@leemhuis.info, Basavaraj.Natikar@amd.com,
pmenzel@molgen.mpg.de, bugs-a21@moonlit-rail.com,
stable@vger.kernel.org
Subject: Re: [PATCH 1/2] Revert "xhci: Enable RPM on controllers that support low-power states"
Date: Mon, 4 Dec 2023 16:22:33 +0200 [thread overview]
Message-ID: <db579656-5700-d99b-f1eb-c1e27749eb7b@linux.intel.com> (raw)
In-Reply-To: <070b3ce1-815c-4f3d-af09-e02cda8f9bf0@amd.com>
On 4.12.2023 12.49, Basavaraj Natikar wrote:
>
> On 12/4/2023 3:38 PM, Mathias Nyman wrote:
>> This reverts commit a5d6264b638efeca35eff72177fd28d149e0764b.
>>
>> This patch was an attempt to solve issues seen when enabling runtime PM
>> as default for all AMD 1.1 xHC hosts. see commit 4baf12181509
>> ("xhci: Loosen RPM as default policy to cover for AMD xHC 1.1")
>
> AFAK, only 4baf12181509 commit has regression on AMD xHc 1.1 below is not regression
> patch and its unrelated to AMD xHC 1.1.
>
> Only [PATCH 2/2] Revert "xhci: Loosen RPM as default policy to cover for AMD xHC 1.1"
> alone in this series solves regression issues.
>
Patch a5d6264b638e ("xhci: Enable RPM on controllers that support low-power states")
was originally not supposed to go to stable. It was added later as it solved some
cases triggered by 4baf12181509 ("xhci: Loosen RPM as default policy to cover for AMD xHC 1.1")
see:
https://lore.kernel.org/linux-usb/5993222.lOV4Wx5bFT@natalenko.name/
Turns out it wasn't enough.
If we now revert 4baf12181509 "xhci: Loosen RPM as default policy to cover for AMD xHC 1.1"
I still think it makes sense to also revert a5d6264b638e.
Especially from the stable kernels.
This way we roll back this whole issue to a known working state.
Thanks
Mathias
next prev parent reply other threads:[~2023-12-04 14:21 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 1:54 Regression: Inoperative bluetooth, Intel chipset, mainline kernel 6.6.2+ Kris Karas (Bug Reporting)
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)
2023-12-01 6:33 ` Thorsten Leemhuis
2023-12-01 8:15 ` Greg KH
2023-12-02 6:43 ` Kris Karas (Bug Reporting)
2023-12-02 7:23 ` Paul Menzel
2023-12-02 7:50 ` Greg KH
2023-12-02 7:58 ` Kris Karas (Bug Reporting)
2023-12-02 8:15 ` Greg KH
2023-12-03 8:32 ` Kris Karas (Bug Reporting)
2023-12-03 8:38 ` Greg KH
2023-12-03 16:16 ` Basavaraj Natikar
2023-12-03 16:24 ` Basavaraj Natikar
2023-12-03 19:52 ` Oleksandr Natalenko
2023-12-04 9:12 ` Mathias Nyman
2023-12-04 10:08 ` [PATCH 1/2] Revert "xhci: Enable RPM on controllers that support low-power states" Mathias Nyman
2023-12-04 10:08 ` [PATCH 2/2] Revert "xhci: Loosen RPM as default policy to cover for AMD xHC 1.1" Mathias Nyman
2023-12-04 10:14 ` [1/2] Revert "xhci: Enable RPM on controllers that support low-power states" bluez.test.bot
2023-12-04 10:49 ` [PATCH 1/2] " Basavaraj Natikar
2023-12-04 14:22 ` Mathias Nyman [this message]
2023-12-04 14:49 ` Basavaraj Natikar
2023-12-04 15:06 ` Mathias Nyman
2023-12-04 15:29 ` Basavaraj Natikar
2023-12-04 23:55 ` Greg KH
2023-12-05 9:05 ` [PATCH v2] Revert "xhci: Loosen RPM as default policy to cover for AMD xHC 1.1" Mathias Nyman
2023-12-05 9:13 ` [v2] " bluez.test.bot
2023-12-05 18:36 ` [PATCH v2] " Mario Limonciello
2023-12-15 16:53 ` patchwork-bot+bluetooth
2023-12-15 16:53 ` [PATCH 1/2] Revert "xhci: Enable RPM on controllers that support low-power states" patchwork-bot+bluetooth
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=db579656-5700-d99b-f1eb-c1e27749eb7b@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=Basavaraj.Natikar@amd.com \
--cc=bnatikar@amd.com \
--cc=bugs-a21@moonlit-rail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=pmenzel@molgen.mpg.de \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).