From: Bjorn Helgaas <helgaas@kernel.org>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>
Cc: Vidya Sagar <vidyas@nvidia.com>,
Lukasz Majczak <lma@semihalf.com>,
Rajat Jain <rajatja@google.com>,
Ben Chuang <benchuanggli@gmail.com>,
bhelgaas@google.com, lorenzo.pieralisi@arm.com,
refactormyself@gmail.com, kw@linux.com, kenny@panix.com,
treding@nvidia.com, jonathanh@nvidia.com, abhsahu@nvidia.com,
sagupta@nvidia.com, linux-pci@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kthota@nvidia.com, mmaddireddy@nvidia.com, sagar.tv@gmail.com
Subject: Re: [PATCH V2] PCI/ASPM: Save/restore L1SS Capability for suspend/resume
Date: Thu, 25 Aug 2022 18:01:21 -0500 [thread overview]
Message-ID: <20220825230121.GA2879965@bhelgaas> (raw)
In-Reply-To: <CAAd53p7WWxyvvB54ADkFSZE1oJweaoNK25g6YNcNxCqkeWiVKg@mail.gmail.com>
On Tue, Aug 23, 2022 at 10:55:01PM +0800, Kai-Heng Feng wrote:
> On Tue, Aug 9, 2022 at 12:17 AM Vidya Sagar <vidyas@nvidia.com> wrote:
> >
> > Thanks Lukasz for the update.
> > I think confirms that there is no issue with the patch as such.
> > Bjorn, could you please define the next step for this patch?
>
> I think the L1SS cap went away _after_ L1SS registers are restored,
> since your patch already check the cap before doing any write:
> + aspm_l1ss = pci_find_ext_capability(dev, PCI_EXT_CAP_ID_L1SS);
> + if (!aspm_l1ss)
> + return;
>
> That means it's more likely to be caused by the following change:
> + pci_write_config_dword(dev, aspm_l1ss + PCI_L1SS_CTL2, *cap++);
> + pci_write_config_dword(dev, aspm_l1ss + PCI_L1SS_CTL1, *cap++);
>
> So is it possible to clear PCI_L1SS_CTL1 before setting PCI_L1SS_CTL2,
> like what aspm_calc_l1ss_info() does?
Sorry, I've totally lost track of where we are with this. I guess the
object is to save/restore L1SS state.
And there are two problems that aren't understood yet?
1) Lukasz's 01:00.0 wifi device didn't work immediately after
resume, but seemed to be hot-added later? [1]
2) The 00:14.0 Root Port L1SS capability was present before
suspend/resume but not after? [2,3]
I thought Lukasz's latest emails [4,5] indicated that problem 1) still
happened and presumably only happens with Vidya's patch, and 2) also
still happens, but happens even *without* Vidya's patch. Do I have
that right?
If adding the patch causes 1), obviously we would need to fix that.
It would certainly be good to understand 2) as well, but I guess if
that's a pre-existing problem, ...
Bjorn
[1] https://gist.github.com/semihalf-majczak-lukasz/fb36dfa2eff22911109dfb91ab0fc0e3#file-dmesg-L1762
[2] https://gist.github.com/semihalf-majczak-lukasz/fb36dfa2eff22911109dfb91ab0fc0e3#file-lspci-before-suspend-log-L136
[3] https://gist.github.com/semihalf-majczak-lukasz/fb36dfa2eff22911109dfb91ab0fc0e3#file-lspci-after-suspend-log-L136
[4] https://lore.kernel.org/r/CAFJ_xbr5NjoV1jC3P93N4UgooUuNdCRnrX7HuK=xLtPM5y7EjA@mail.gmail.com
[5] https://lore.kernel.org/r/CAFJ_xboyQyEaDeQ+pZH_YqN52-ALGNqzmmzeyNt6X_Cz-c1w9Q@mail.gmail.com
next prev parent reply other threads:[~2022-08-25 23:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 6:00 [PATCH V2] PCI/ASPM: Save/restore L1SS Capability for suspend/resume Vidya Sagar
2022-07-13 17:59 ` Vidya Sagar
2022-07-13 18:16 ` Bjorn Helgaas
2022-07-14 4:20 ` Kai-Heng Feng
2022-07-15 10:38 ` Ben Chuang
2022-07-22 7:31 ` Kai-Heng Feng
2022-07-22 9:41 ` Lukasz Majczak
2022-07-22 17:42 ` Bjorn Helgaas
2022-07-23 17:03 ` Vidya Sagar
2022-07-25 22:50 ` Rajat Jain
2022-07-26 7:20 ` Lukasz Majczak
2022-07-29 9:39 ` Lukasz Majczak
2022-07-29 14:35 ` Vidya Sagar
2022-08-03 12:04 ` Lukasz Majczak
2022-08-03 12:55 ` Vidya Sagar
2022-08-08 14:07 ` Lukasz Majczak
2022-08-08 16:16 ` Vidya Sagar
2022-08-23 14:55 ` Kai-Heng Feng
2022-08-25 23:01 ` Bjorn Helgaas [this message]
2022-08-26 3:13 ` Kai-Heng Feng
2022-08-26 13:00 ` Vidya Sagar
2022-08-30 11:15 ` Lukasz Majczak
2022-08-30 14:02 ` Vidya Sagar
2022-09-02 5:49 ` Lukasz Majczak
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=20220825230121.GA2879965@bhelgaas \
--to=helgaas@kernel.org \
--cc=abhsahu@nvidia.com \
--cc=benchuanggli@gmail.com \
--cc=bhelgaas@google.com \
--cc=jonathanh@nvidia.com \
--cc=kai.heng.feng@canonical.com \
--cc=kenny@panix.com \
--cc=kthota@nvidia.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lma@semihalf.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=mmaddireddy@nvidia.com \
--cc=rajatja@google.com \
--cc=refactormyself@gmail.com \
--cc=sagar.tv@gmail.com \
--cc=sagupta@nvidia.com \
--cc=treding@nvidia.com \
--cc=vidyas@nvidia.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;
as well as URLs for NNTP newsgroup(s).