From: Sinan Kaya <okaya@codeaurora.org>
To: linux-pci@vger.kernel.org, timur@codeaurora.org
Cc: mayurkumar.patel@intel.com, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Sinan Kaya <okaya@codeaurora.org>
Subject: [PATCH V8 0/5] PCI/ASPM: reconfigure ASPM following hotplug for POLICY_DEFAULT
Date: Sat, 8 Apr 2017 00:55:46 -0400 [thread overview]
Message-ID: <1491627351-1111-1-git-send-email-okaya@codeaurora.org> (raw)
When the operating system is booted with the default ASPM policy
(POLICY_DEFAULT), current code is querying the enable/disable
states from ASPM registers to determine the policy.
For example, a BIOS could set the power saving state to performance
and clear all ASPM control registers. A balanced ASPM policy could
enable L0s and disable L1. A power conscious BIOS could enable both
L0s and L1 to trade off latency and performance vs. power.
After hotplug removal, pcie_aspm_exit_link_state() function clears
the ASPM registers. An insertion following hotplug removal reads
incorrect policy as ASPM disabled even though ASPM was enabled
during boot.
This is caused by the fact that same function is used for reconfiguring
ASPM regardless of the power on state.
------------------------
Changes from v7 (https://www.spinics.net/lists/arm-kernel/msg573034.html)
------------------------
- enable LTSSM as a best effort if the endpoint is not connected during
boot
Sinan Kaya (5):
PCI/ASPM: introduce pci_aspm_init() and add to pci_init_capabilities()
PCI/ASPM: split pci_aspm_init() into two
PCI/ASPM: add init hook to device_add
PCI/ASPM: save power on values during bridge init
PCI/ASPM: move link_state cleanup to bridge remove
drivers/pci/pcie/aspm.c | 149 +++++++++++++++++++++++++++++++++---------------
drivers/pci/probe.c | 3 +
drivers/pci/remove.c | 3 +-
include/linux/pci.h | 2 +
4 files changed, 110 insertions(+), 47 deletions(-)
--
1.9.1
WARNING: multiple messages have this Message-ID (diff)
From: Sinan Kaya <okaya@codeaurora.org>
To: linux-pci@vger.kernel.org, timur@codeaurora.org
Cc: Sinan Kaya <okaya@codeaurora.org>,
linux-arm-msm@vger.kernel.org, mayurkumar.patel@intel.com,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH V8 0/5] PCI/ASPM: reconfigure ASPM following hotplug for POLICY_DEFAULT
Date: Sat, 8 Apr 2017 00:55:46 -0400 [thread overview]
Message-ID: <1491627351-1111-1-git-send-email-okaya@codeaurora.org> (raw)
When the operating system is booted with the default ASPM policy
(POLICY_DEFAULT), current code is querying the enable/disable
states from ASPM registers to determine the policy.
For example, a BIOS could set the power saving state to performance
and clear all ASPM control registers. A balanced ASPM policy could
enable L0s and disable L1. A power conscious BIOS could enable both
L0s and L1 to trade off latency and performance vs. power.
After hotplug removal, pcie_aspm_exit_link_state() function clears
the ASPM registers. An insertion following hotplug removal reads
incorrect policy as ASPM disabled even though ASPM was enabled
during boot.
This is caused by the fact that same function is used for reconfiguring
ASPM regardless of the power on state.
------------------------
Changes from v7 (https://www.spinics.net/lists/arm-kernel/msg573034.html)
------------------------
- enable LTSSM as a best effort if the endpoint is not connected during
boot
Sinan Kaya (5):
PCI/ASPM: introduce pci_aspm_init() and add to pci_init_capabilities()
PCI/ASPM: split pci_aspm_init() into two
PCI/ASPM: add init hook to device_add
PCI/ASPM: save power on values during bridge init
PCI/ASPM: move link_state cleanup to bridge remove
drivers/pci/pcie/aspm.c | 149 +++++++++++++++++++++++++++++++++---------------
drivers/pci/probe.c | 3 +
drivers/pci/remove.c | 3 +-
include/linux/pci.h | 2 +
4 files changed, 110 insertions(+), 47 deletions(-)
--
1.9.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: okaya@codeaurora.org (Sinan Kaya)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V8 0/5] PCI/ASPM: reconfigure ASPM following hotplug for POLICY_DEFAULT
Date: Sat, 8 Apr 2017 00:55:46 -0400 [thread overview]
Message-ID: <1491627351-1111-1-git-send-email-okaya@codeaurora.org> (raw)
When the operating system is booted with the default ASPM policy
(POLICY_DEFAULT), current code is querying the enable/disable
states from ASPM registers to determine the policy.
For example, a BIOS could set the power saving state to performance
and clear all ASPM control registers. A balanced ASPM policy could
enable L0s and disable L1. A power conscious BIOS could enable both
L0s and L1 to trade off latency and performance vs. power.
After hotplug removal, pcie_aspm_exit_link_state() function clears
the ASPM registers. An insertion following hotplug removal reads
incorrect policy as ASPM disabled even though ASPM was enabled
during boot.
This is caused by the fact that same function is used for reconfiguring
ASPM regardless of the power on state.
------------------------
Changes from v7 (https://www.spinics.net/lists/arm-kernel/msg573034.html)
------------------------
- enable LTSSM as a best effort if the endpoint is not connected during
boot
Sinan Kaya (5):
PCI/ASPM: introduce pci_aspm_init() and add to pci_init_capabilities()
PCI/ASPM: split pci_aspm_init() into two
PCI/ASPM: add init hook to device_add
PCI/ASPM: save power on values during bridge init
PCI/ASPM: move link_state cleanup to bridge remove
drivers/pci/pcie/aspm.c | 149 +++++++++++++++++++++++++++++++++---------------
drivers/pci/probe.c | 3 +
drivers/pci/remove.c | 3 +-
include/linux/pci.h | 2 +
4 files changed, 110 insertions(+), 47 deletions(-)
--
1.9.1
next reply other threads:[~2017-04-08 4:55 UTC|newest]
Thread overview: 94+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-08 4:55 Sinan Kaya [this message]
2017-04-08 4:55 ` [PATCH V8 0/5] PCI/ASPM: reconfigure ASPM following hotplug for POLICY_DEFAULT Sinan Kaya
2017-04-08 4:55 ` Sinan Kaya
2017-04-08 4:55 ` [PATCH V8 1/5] PCI/ASPM: introduce pci_aspm_init() and add to pci_init_capabilities() Sinan Kaya
2017-04-08 4:55 ` Sinan Kaya
2017-04-08 4:55 ` Sinan Kaya
2017-04-13 20:51 ` Bjorn Helgaas
2017-04-13 20:51 ` Bjorn Helgaas
2017-04-14 19:10 ` Sinan Kaya
2017-04-14 19:10 ` Sinan Kaya
2017-04-08 4:55 ` [PATCH V8 2/5] PCI/ASPM: split pci_aspm_init() into two Sinan Kaya
2017-04-08 4:55 ` Sinan Kaya
2017-04-08 4:55 ` Sinan Kaya
2017-04-12 19:16 ` Rajat Jain
2017-04-12 19:16 ` Rajat Jain
2017-04-13 18:25 ` Bjorn Helgaas
2017-04-13 18:25 ` Bjorn Helgaas
2017-04-13 18:25 ` Bjorn Helgaas
2017-04-14 19:10 ` Sinan Kaya
2017-04-14 19:10 ` Sinan Kaya
2017-04-14 19:10 ` Sinan Kaya
2017-04-08 4:55 ` [PATCH V8 3/5] PCI/ASPM: add init hook to device_add Sinan Kaya
2017-04-08 4:55 ` Sinan Kaya
2017-04-08 4:55 ` Sinan Kaya
2017-04-13 20:48 ` Bjorn Helgaas
2017-04-13 20:48 ` Bjorn Helgaas
2017-04-13 20:48 ` Bjorn Helgaas
2017-04-13 21:02 ` Bjorn Helgaas
2017-04-13 21:02 ` Bjorn Helgaas
2017-04-13 21:02 ` Bjorn Helgaas
2017-04-14 1:19 ` Sinan Kaya
2017-04-14 1:19 ` Sinan Kaya
2017-04-14 1:30 ` Bjorn Helgaas
2017-04-14 1:30 ` Bjorn Helgaas
2017-04-08 4:55 ` [PATCH V8 4/5] PCI/ASPM: save power on values during bridge init Sinan Kaya
2017-04-08 4:55 ` Sinan Kaya
2017-04-08 4:55 ` Sinan Kaya
2017-04-12 19:19 ` Rajat Jain
2017-04-12 19:19 ` Rajat Jain
2017-04-12 19:19 ` Rajat Jain
2017-04-14 19:12 ` Sinan Kaya
2017-04-14 19:12 ` Sinan Kaya
2017-04-14 19:12 ` Sinan Kaya
2017-04-14 21:44 ` Bjorn Helgaas
2017-04-14 21:44 ` Bjorn Helgaas
2017-04-14 21:44 ` Bjorn Helgaas
2017-04-14 22:17 ` Sinan Kaya
2017-04-14 22:17 ` Sinan Kaya
2017-04-17 16:38 ` Bjorn Helgaas
2017-04-17 16:38 ` Bjorn Helgaas
2017-04-17 17:50 ` Sinan Kaya
2017-04-17 17:50 ` Sinan Kaya
2017-04-21 7:46 ` Patel, Mayurkumar
2017-04-21 7:46 ` Patel, Mayurkumar
2017-04-21 7:46 ` Patel, Mayurkumar
2017-04-21 7:46 ` Patel, Mayurkumar
2017-04-21 13:50 ` Sinan Kaya
2017-04-21 13:50 ` Sinan Kaya
2017-04-21 14:13 ` Patel, Mayurkumar
2017-04-21 14:13 ` Patel, Mayurkumar
2017-04-21 14:13 ` Patel, Mayurkumar
2017-04-21 14:13 ` Patel, Mayurkumar
2017-04-25 18:45 ` Bjorn Helgaas
2017-04-25 18:45 ` Bjorn Helgaas
2017-05-02 12:02 ` Patel, Mayurkumar
2017-05-02 12:02 ` Patel, Mayurkumar
2017-05-02 12:02 ` Patel, Mayurkumar
2017-05-03 21:10 ` Bjorn Helgaas
2017-05-03 21:10 ` Bjorn Helgaas
2017-05-03 21:10 ` Bjorn Helgaas
2017-05-15 9:10 ` Patel, Mayurkumar
2017-05-15 9:10 ` Patel, Mayurkumar
2017-05-15 9:10 ` Patel, Mayurkumar
2017-05-15 9:10 ` Patel, Mayurkumar
2017-04-08 4:55 ` [PATCH V8 5/5] PCI/ASPM: move link_state cleanup to bridge remove Sinan Kaya
2017-04-08 4:55 ` Sinan Kaya
2017-04-08 4:55 ` Sinan Kaya
2017-04-10 11:37 ` [PATCH V8 0/5] PCI/ASPM: reconfigure ASPM following hotplug for POLICY_DEFAULT Patel, Mayurkumar
2017-04-10 11:37 ` Patel, Mayurkumar
2017-04-10 11:37 ` Patel, Mayurkumar
2017-04-10 13:07 ` Sinan Kaya
2017-04-10 13:07 ` Sinan Kaya
2017-04-10 13:07 ` Sinan Kaya
2017-04-10 13:11 ` Patel, Mayurkumar
2017-04-10 13:11 ` Patel, Mayurkumar
2017-04-10 13:11 ` Patel, Mayurkumar
2017-04-11 21:19 ` Bjorn Helgaas
2017-04-11 21:19 ` Bjorn Helgaas
2017-04-11 21:19 ` Bjorn Helgaas
2017-04-11 21:27 ` Sinan Kaya
2017-04-11 21:27 ` Sinan Kaya
2017-04-11 22:41 ` Bjorn Helgaas
2017-04-11 22:41 ` Bjorn Helgaas
2017-04-11 22:41 ` 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=1491627351-1111-1-git-send-email-okaya@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mayurkumar.patel@intel.com \
--cc=timur@codeaurora.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.