From: "Saheed O. Bolarinwa" <refactormyself@gmail.com>
To: helgaas@kernel.org
Cc: "Bolarinwa O. Saheed" <refactormyself@gmail.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
kw@linux.com
Subject: [RFC PATCH 0/3 v2] PCI/ASPM: Remove struct aspm_latency
Date: Thu, 16 Sep 2021 10:49:23 +0200 [thread overview]
Message-ID: <20210916084926.32614-1-refactormyself@gmail.com> (raw)
From: "Bolarinwa O. Saheed" <refactormyself@gmail.com>
To validate and set link latency capability, `struct aspm_latency` and
related members defined within `struct pcie_link_state` are used.
However, since there are not many access to theses values, it is possible
to directly access and compute these values.
Doing this will also reduce the dependency on `struct pcie_link_state`.
The series removes `struct aspm_latency` and related members within
`struct pcie_link_state`. All latencies are now calculated when needed.
Changes in this version:
- directly access downstream by calling `pci_function_0()` instead of
used the `struct pcie_link_state`
Saheed O. Bolarinwa (3):
PCI/ASPM: Remove link latencies cached within struct pcie_link_state
PCI/ASPM: Remove struct pcie_link_state.acceptable
PCI/ASPM: Remove struct aspm_latency
drivers/pci/pcie/aspm.c | 89 ++++++++++++++++++-----------------------
1 file changed, 38 insertions(+), 51 deletions(-)
--
2.20.1
next reply other threads:[~2021-09-16 8:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 8:49 Saheed O. Bolarinwa [this message]
2021-09-16 8:49 ` [RFC PATCH 1/3 v1] PCI/ASPM: Remove cached latencies in struct pcie_link_state Saheed O. Bolarinwa
2021-09-16 8:49 ` [RFC PATCH 2/3 v2] PCI/ASPM: Remove struct pcie_link_state.acceptable Saheed O. Bolarinwa
2021-09-30 23:52 ` Bjorn Helgaas
2021-09-16 8:49 ` [RFC PATCH 3/3 v1] PCI/ASPM: Remove struct aspm_latency Saheed O. Bolarinwa
2021-09-26 20:31 ` [RFC PATCH 0/3 v2] " 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=20210916084926.32614-1-refactormyself@gmail.com \
--to=refactormyself@gmail.com \
--cc=helgaas@kernel.org \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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).