From: Mario Limonciello <mario.limonciello@amd.com>
To: "Bjorn Helgaas" <bhelgaas@google.com>,
"Hans de Goede" <hdegoede@redhat.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
Shyam Sundar S K <Shyam-sundar.S-k@amd.com>,
"open list:PCI SUBSYSTEM" <linux-pci@vger.kernel.org>,
"open list:X86 PLATFORM DRIVERS"
<platform-driver-x86@vger.kernel.org>,
Lukas Wunner <lukas@wunner.de>,
Kai-Heng Feng <kai.heng.feng@canonical.com>,
Mario Limonciello <mario.limonciello@amd.com>
Subject: [PATCH 0/4] Add support for drivers to decide bridge D3 policy
Date: Tue, 24 Oct 2023 21:05:42 -0500 [thread overview]
Message-ID: <20231025020546.504-1-mario.limonciello@amd.com> (raw)
The policy for whether PCI bridges are allowed to select D3 is dictated
by empirical results that are enumerated into pci_bridge_d3_possible().
In Windows this behaves differently in that Windows internal policy is
not used for devices when a power engine plugin driver provided by the
SOC vendor is installed. This driver is used to decide the policy in
those cases.
This series implements a system that lets drivers register such a policy
control as well. It isn't activated for any SOCs by default.
This is heavily leveraged from the work in [1]
[1] https://lore.kernel.org/platform-driver-x86/20230906184354.45846-1-mario.limonciello@amd.com/
RFC v1->PATCH v1
* Simplify the logic, use pci_d3cold_enable()/pci_d3cold_disable() functions
* Roll https://lore.kernel.org/linux-pci/20231004144731.158342-1-mario.limonciello@amd.com/ into series
* Updates for some typos
* Re-order series. Patches 1 and 2 can potentially apply to PCI tree, 3 and 4 to platform-x86 tree.
Mario Limonciello (4):
PCI: Make d3cold_allowed sysfs attribute read only
PCI: Refresh root ports in pci_bridge_d3_update()
ACPI: x86: s2idle: Export symbol for fetching constraints for module
use
platform/x86/amd: pmc: Add support for using constraints to decide D3
policy
Documentation/ABI/testing/sysfs-bus-pci | 4 +-
drivers/acpi/x86/s2idle.c | 1 +
drivers/pci/pci-acpi.c | 2 +-
drivers/pci/pci-sysfs.c | 14 +-----
drivers/pci/pci.c | 12 ++++--
drivers/platform/x86/amd/pmc/pmc.c | 57 +++++++++++++++++++++++++
include/linux/pci.h | 1 -
7 files changed, 72 insertions(+), 19 deletions(-)
--
2.34.1
next reply other threads:[~2023-10-25 2:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 2:05 Mario Limonciello [this message]
2023-10-25 2:05 ` [PATCH 1/4] PCI: Make d3cold_allowed sysfs attribute read only Mario Limonciello
2023-10-26 17:03 ` Rafael J. Wysocki
2023-10-25 2:05 ` [PATCH 2/4] PCI: Refresh root ports in pci_bridge_d3_update() Mario Limonciello
2023-10-25 2:05 ` [PATCH 3/4] ACPI: x86: s2idle: Export symbol for fetching constraints for module use Mario Limonciello
2023-10-25 2:05 ` [PATCH 4/4] platform/x86/amd: pmc: Add support for using constraints to decide D3 policy Mario Limonciello
2023-10-26 17:04 ` [PATCH 0/4] Add support for drivers to decide bridge " Rafael J. Wysocki
2023-10-26 17:06 ` Mario Limonciello
2023-10-26 17:10 ` Rafael J. Wysocki
2023-11-20 10:13 ` Hans de Goede
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=20231025020546.504-1-mario.limonciello@amd.com \
--to=mario.limonciello@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=bhelgaas@google.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=kai.heng.feng@canonical.com \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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