From: Greg KH <gregkh@linuxfoundation.org>
To: Mark Hasemeyer <markhas@chromium.org>
Cc: bhelgaas@google.com, kai.heng.feng@canonical.com, stable@vger.kernel.org
Subject: Re: [PATCH] PCI:ASPM: Remove pcie_aspm_pm_state_change()
Date: Tue, 25 Apr 2023 07:08:25 +0200 [thread overview]
Message-ID: <ZEdgSbX3AsaTNBLr@kroah.com> (raw)
In-Reply-To: <20230424183536.808003-1-markhas@chromium.org>
On Mon, Apr 24, 2023 at 12:35:36PM -0600, Mark Hasemeyer wrote:
> > Odd, it does not apply cleanly, so how was this tested? Can you please
> > send the tested backport that you have so we know to get it correct?
>
> Sorry about that. I had to apply a trivial backport as
> `pci_set_low_power_state` does not exist in v5.15. It was tested by using an
> RTC wake in combination with using the sysfs to trigger a suspend:
> ```
> echo +5 > /sys/class/rtc/rtc0/wakealarm && echo freeze > /sys/power/state
> ```
>
> Patch below.
> ------------------------------------
> >From 5ca368f6918710bf491feee54e09a060de835d3f Mon Sep 17 00:00:00 2001
> From: Kai-Heng Feng <kai.heng.feng@canonical.com>
> Date: Mon, 11 Jul 2022 18:07:01 -0500
> Subject: [PATCH] PCI/ASPM: Remove pcie_aspm_pm_state_change()
>
> pcie_aspm_pm_state_change() was introduced at the inception of PCIe ASPM
> code, but it can cause some issues. For instance, when ASPM config is
> changed via sysfs, those changes won't persist across power state change
> because pcie_aspm_pm_state_change() overwrites them.
>
> Also, if the driver restores L1SS [1] after system resume, the restored
> state will also be overwritten by pcie_aspm_pm_state_change().
>
> Remove pcie_aspm_pm_state_change(). If there's any hardware that really
> needs it to function, a quirk can be used instead.
>
> [1] https://lore.kernel.org/linux-pci/20220201123536.12962-1-vidyas@nvidia.com/
> Link: https://lore.kernel.org/r/20220509073639.2048236-1-kai.heng.feng@canonical.com
> [bhelgaas: remove additional pcie_aspm_pm_state_change() call in
> pci_set_low_power_state(), added by
> 10aa5377fc8a ("PCI/PM: Split pci_raw_set_power_state()") and moved by
> 7957d201456f ("PCI/PM: Relocate pci_set_low_power_state()")]
> Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
> Signed-off-by: Mark Hasemeyer <markhas@chromium.org>
> ---
> drivers/pci/pci.c | 3 ---
> drivers/pci/pci.h | 2 --
> drivers/pci/pcie/aspm.c | 19 -------------------
> 3 files changed, 24 deletions(-)
What is the git commit id of this change in Linus's tree?
And can you send it as a stand-alone patch, not one that I have to
hand-edit out of an email to use? Doing that does not scale at the rate
of change we currently deal with at all.
thanks,
greg k-h
next prev parent reply other threads:[~2023-04-25 5:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 18:42 [PATCH] PCI:ASPM: Remove pcie_aspm_pm_state_change() Mark Hasemeyer
2023-04-23 10:30 ` Greg KH
2023-04-24 18:35 ` Mark Hasemeyer
2023-04-25 5:08 ` Greg KH [this message]
2023-04-25 17:34 ` Mark Hasemeyer
-- strict thread matches above, loose matches on Subject: below --
2023-04-21 18:33 Mark Hasemeyer
2022-05-09 7:36 Kai-Heng Feng
2022-06-21 2:27 ` Kai-Heng Feng
2022-07-11 23:11 ` Bjorn Helgaas
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=ZEdgSbX3AsaTNBLr@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bhelgaas@google.com \
--cc=kai.heng.feng@canonical.com \
--cc=markhas@chromium.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.