From: Vidya Sagar <vidyas@nvidia.com>
To: <bhelgaas@google.com>, <lorenzo.pieralisi@arm.com>,
<refactormyself@gmail.com>, <kw@linux.com>, <rajatja@google.com>,
<kenny@panix.com>, <kai.heng.feng@canonical.com>,
<abhsahu@nvidia.com>, <sagupta@nvidia.com>
Cc: <treding@nvidia.com>, <jonathanh@nvidia.com>,
<linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<kthota@nvidia.com>, <mmaddireddy@nvidia.com>,
<vidyas@nvidia.com>, <sagar.tv@gmail.com>
Subject: [PATCH V4 0/2] PCI/ASPM: Save/restore L1SS Capability for suspend/resume
Date: Tue, 13 Sep 2022 18:48:20 +0530 [thread overview]
Message-ID: <20220913131822.16557-1-vidyas@nvidia.com> (raw)
This patch series saves and restores the ASPM L1SS capability registers
during suspend/resume cycle of the system.
First patch refactors the existing L1SS register programming code to
take out the common code.
Second patch adds support to save and restore of the L1SS registers using
the common code extracted in the first patch to restore the registers.
This patch is verified on Tegra194 and Tegra234 platforms.
Vidya Sagar (2):
PCI/ASPM: Refactor ASPM L1SS control register programming
PCI/ASPM: Save/restore L1SS Capability for suspend/resume
drivers/pci/pci.c | 7 +++
drivers/pci/pci.h | 4 ++
drivers/pci/pcie/aspm.c | 106 +++++++++++++++++++++++++++-------------
3 files changed, 83 insertions(+), 34 deletions(-)
--
2.17.1
next reply other threads:[~2022-09-13 13:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 13:18 Vidya Sagar [this message]
2022-09-13 13:18 ` [PATCH V4 1/2] PCI/ASPM: Refactor ASPM L1SS control register programming Vidya Sagar
2022-09-29 22:00 ` Bjorn Helgaas
2022-10-03 6:42 ` Vidya Sagar
2022-10-05 2:35 ` Bjorn Helgaas
2022-10-09 5:44 ` Vidya Sagar
2022-09-13 13:18 ` [PATCH V4 2/2] PCI/ASPM: Save/restore L1SS Capability for suspend/resume Vidya Sagar
2022-09-13 17:17 ` [PATCH V4 0/2] " 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=20220913131822.16557-1-vidyas@nvidia.com \
--to=vidyas@nvidia.com \
--cc=abhsahu@nvidia.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 \
/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.