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>,
Lukas Wunner <lukas@wunner.de>,
Kai-Heng Feng <kai.heng.feng@canonical.com>,
Mario Limonciello <mario.limonciello@amd.com>
Subject: [RFC v1 3/4] PCI: Check for changes in pci_bridge_d3_possible() when updating D3
Date: Mon, 9 Oct 2023 17:56:52 -0500 [thread overview]
Message-ID: <20231009225653.36030-4-mario.limonciello@amd.com> (raw)
In-Reply-To: <20231009225653.36030-1-mario.limonciello@amd.com>
As drivers can report an optin or veto for a given PCI device it's
possible that pci_bridge_d3_possible() reports different values while
calling pci_bridge_d3_update(). Take these values into account while
updating the ability for a bridge to go into D3.
Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
---
drivers/pci/pci.c | 29 +++++++++++++++++++----------
1 file changed, 19 insertions(+), 10 deletions(-)
diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
index 3b8e7b936908..77af444fcf1b 100644
--- a/drivers/pci/pci.c
+++ b/drivers/pci/pci.c
@@ -3094,6 +3094,14 @@ static int pci_dev_check_d3cold(struct pci_dev *dev, void *data)
return !*d3cold_ok;
}
+static void pci_bridge_d3_propagate(struct pci_dev *bridge, bool d3_ok)
+{
+ if (bridge->bridge_d3 != d3_ok) {
+ bridge->bridge_d3 = d3_ok;
+ pci_bridge_d3_propagate(bridge, d3_ok);
+ }
+}
+
/*
* pci_bridge_d3_update - Update bridge D3 capabilities
* @dev: PCI device which is changed
@@ -3106,12 +3114,16 @@ void pci_bridge_d3_update(struct pci_dev *dev)
{
bool remove = !device_is_registered(&dev->dev);
struct pci_dev *bridge;
- bool d3cold_ok = true;
+ bool d3_ok = true;
bridge = pci_upstream_bridge(dev);
- if (!bridge || !pci_bridge_d3_possible(bridge))
+ if (!bridge)
return;
+ /* Propagate change to upstream bridges */
+ d3_ok = pci_bridge_d3_possible(bridge);
+ pci_bridge_d3_propagate(bridge, d3_ok);
+
/*
* If D3 is currently allowed for the bridge, removing one of its
* children won't change that.
@@ -3128,7 +3140,7 @@ void pci_bridge_d3_update(struct pci_dev *dev)
* first may allow us to skip checking its siblings.
*/
if (!remove)
- pci_dev_check_d3cold(dev, &d3cold_ok);
+ pci_dev_check_d3cold(dev, &d3_ok);
/*
* If D3 is currently not allowed for the bridge, this may be caused
@@ -3136,15 +3148,12 @@ void pci_bridge_d3_update(struct pci_dev *dev)
* so we need to go through all children to find out if one of them
* continues to block D3.
*/
- if (d3cold_ok && !bridge->bridge_d3)
+ if (d3_ok && !bridge->bridge_d3)
pci_walk_bus(bridge->subordinate, pci_dev_check_d3cold,
- &d3cold_ok);
+ &d3_ok);
- if (bridge->bridge_d3 != d3cold_ok) {
- bridge->bridge_d3 = d3cold_ok;
- /* Propagate change to upstream bridges */
- pci_bridge_d3_update(bridge);
- }
+ /* Propagate change to upstream bridges */
+ pci_bridge_d3_propagate(bridge, d3_ok);
}
/**
--
2.34.1
next prev parent reply other threads:[~2023-10-09 22:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 22:56 [RFC v1 0/4] Add support for drivers to decide bridge D3 policy Mario Limonciello
2023-10-09 22:56 ` [RFC v1 1/4] ACPI: x86: s2idle: Export symbol for fetching constraints for module use Mario Limonciello
2023-10-09 22:56 ` [RFC v1 2/4] PCI: Add support for drivers to decide bridge D3 policy Mario Limonciello
2023-10-14 10:53 ` Lukas Wunner
2023-10-15 18:55 ` Mario Limonciello
2023-10-09 22:56 ` Mario Limonciello [this message]
2023-10-09 22:56 ` [RFC v1 4/4] platform/x86/amd: pmc: Add support for using constraints to decide " Mario Limonciello
2023-10-16 2:11 ` Kai-Heng Feng
2023-10-16 21:34 ` Mario Limonciello
2023-10-24 7:05 ` Kai-Heng Feng
2023-10-24 19:45 ` Mario Limonciello
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=20231009225653.36030-4-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=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