From: Abhishek Sahu <abhsahu@nvidia.com>
To: Vidya Sagar <vidyas@nvidia.com>,
bhelgaas@google.com, lorenzo.pieralisi@arm.com,
refactormyself@gmail.com, kw@linux.com, rajatja@google.com,
kenny@panix.com, kai.heng.feng@canonical.com, treding@nvidia.com,
jonathanh@nvidia.com, sagupta@nvidia.com
Cc: benchuanggli@gmail.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, kthota@nvidia.com,
mmaddireddy@nvidia.com, sagar.tv@gmail.com
Subject: Re: [PATCH V3] PCI/ASPM: Save/restore L1SS Capability for suspend/resume
Date: Wed, 7 Sep 2022 17:25:07 +0530 [thread overview]
Message-ID: <2bd71555-ad5e-601c-412e-851cf53b2716@nvidia.com> (raw)
In-Reply-To: <20220826125526.28859-1-vidyas@nvidia.com>
On 8/26/2022 6:25 PM, Vidya Sagar wrote:
> Previously ASPM L1 Substates control registers (CTL1 and CTL2) weren't
> saved and restored during suspend/resume leading to L1 Substates
> configuration being lost post-resume.
>
> Save the L1 Substates control registers so that the configuration is
> retained post-resume.
>
Tested-by: Abhishek Sahu <abhsahu@nvidia.com>
> Signed-off-by: Vidya Sagar <vidyas@nvidia.com>
> ---
> V3:
> * Disabled L1.2 enable fields while restoring Control-1 register
>
Thanks Vidya.
I have applied your v3 patch in 6.0-rc3 kernel and tested again.
I did 100 cycles of suspend/resume in a Alder lake based notebook
which has NVIDIA discrete GPU and it is working fine.
# lspci -d "0x10de:" -vvv|grep "L1SubCtl" -A 2
After Boot:
L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+
T_CommonMode=0us LTR1.2_Threshold=753664ns
L1SubCtl2: T_PwrOn=500us
After Suspend/resume without this patch:
L1SubCtl1: PCI-PM_L1.2- PCI-PM_L1.1- ASPM_L1.2- ASPM_L1.1-
T_CommonMode=0us LTR1.2_Threshold=0ns
L1SubCtl2: T_PwrOn=10us
After Suspend/resume with this patch:
L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+
T_CommonMode=0us LTR1.2_Threshold=753664ns
L1SubCtl2: T_PwrOn=500us
So with this patch, the L1SubCtl1 and L1SubCtl2 settings are being
restored back correctly.
Regards,
Abhishek
next prev parent reply other threads:[~2022-09-07 11:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 12:55 [PATCH V3] PCI/ASPM: Save/restore L1SS Capability for suspend/resume Vidya Sagar
2022-09-07 11:55 ` Abhishek Sahu [this message]
2022-09-07 21:05 ` Bjorn Helgaas
2022-09-13 13:15 ` Vidya Sagar
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=2bd71555-ad5e-601c-412e-851cf53b2716@nvidia.com \
--to=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=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