From: Mario Limonciello <mario.limonciello@amd.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Bjorn Helgaas" <bhelgaas@google.com>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
"Hans de Goede" <hdegoede@redhat.com>,
"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>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Lukas Wunner" <lukas@wunner.de>,
"Kai-Heng Feng" <kai.heng.feng@canonical.com>,
linux-acpi@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH v2 2/4] PCI: Refresh root ports in pci_bridge_d3_update()
Date: Tue, 12 Dec 2023 13:41:34 -0600 [thread overview]
Message-ID: <d61a0a3d-2adc-402f-be4c-2f99a65f5b04@amd.com> (raw)
In-Reply-To: <CAJZ5v0g_HWFnt0a5fDnb73Q14C84O+RPYVF104TDK7T_Ox3_EA@mail.gmail.com>
On 12/12/2023 13:25, Rafael J. Wysocki wrote:
> On Mon, Dec 4, 2023 at 7:07 AM Mario Limonciello
> <mario.limonciello@amd.com> wrote:
>>
>> If pci_d3cold_enable() or pci_d3cold_disable() is called on a root
>> port it is ignored because there is no upstream bridge.
>
> The kerneldoc comment of pci_bridge_d3_update() explains what that
> function is for which also covers why it does not take effect when
> called on root ports.
I'm sorry but can you clarify the intent of your comment?
Are you suggesting we should introduce a different function/logic for
root ports, kernel doc should be updated, or root ports should be
special cased in that function?
>
>> If called on a root port, use `no_d3cold` variable to decide policy
>
> It is unclear that this is about pci_bridge_d3_possible() which
> applies to both D3hot and D3cold, not just D3cold AFAICS. I don't
> think that no_d3cold should affect the D3hot behavior.
IMO the semantics are confusing depending upon what device you called
pci_d3cold_disable()/pci_d3cold_enable() with as an argument.
Both devices and root ports are used by existing driver in the kernel.
If you called pci_d3cold_disable() with a device, that actually prevents
the /bridge above it/ from going to D3hot as well (bridge_d3 is set to
the result)
>
>> and also immediately refresh whether D3 is possible.
>
> Which isn't correct AFAICS.
Why?
>
>> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
>> ---
>> drivers/pci/pci.c | 9 ++++++++-
>> 1 file changed, 8 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
>> index 72505794cc72..3d4aaecda457 100644
>> --- a/drivers/pci/pci.c
>> +++ b/drivers/pci/pci.c
>> @@ -3023,6 +3023,9 @@ bool pci_bridge_d3_possible(struct pci_dev *bridge)
>> if (pci_bridge_d3_disable)
>> return false;
>>
>> + if (bridge->no_d3cold)
>> + return false;
>> +
>> /*
>> * Hotplug ports handled by firmware in System Management Mode
>> * may not be put into D3 by the OS (Thunderbolt on non-Macs).
>> @@ -3098,7 +3101,11 @@ void pci_bridge_d3_update(struct pci_dev *dev)
>> bool d3cold_ok = true;
>>
>> bridge = pci_upstream_bridge(dev);
>> - if (!bridge || !pci_bridge_d3_possible(bridge))
>> + if (!bridge) {
>> + dev->bridge_d3 = pci_bridge_d3_possible(dev);
>> + return;
>> + }
>> + if (!pci_bridge_d3_possible(bridge))
>> return;
>>
>> /*
>> --
>> 2.34.1
>>
>>
next prev parent reply other threads:[~2023-12-12 19:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-03 4:10 [PATCH v2 0/4] Add support for drivers to decide bridge D3 policy Mario Limonciello
2023-12-03 4:10 ` [PATCH v2 1/4] PCI: Make d3cold_allowed sysfs attribute read only Mario Limonciello
2023-12-03 4:10 ` [PATCH v2 2/4] PCI: Refresh root ports in pci_bridge_d3_update() Mario Limonciello
2023-12-12 19:25 ` Rafael J. Wysocki
2023-12-12 19:41 ` Mario Limonciello [this message]
2023-12-12 19:53 ` Rafael J. Wysocki
2023-12-03 4:10 ` [PATCH v2 3/4] ACPI: x86: s2idle: Export symbol for fetching constraints for module use Mario Limonciello
2023-12-03 4:10 ` [PATCH v2 4/4] platform/x86/amd: pmc: Add support for using constraints to decide D3 policy Mario Limonciello
2023-12-04 14:08 ` [PATCH v2 0/4] Add support for drivers to decide bridge " 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=d61a0a3d-2adc-402f-be4c-2f99a65f5b04@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-acpi@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael@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;
as well as URLs for NNTP newsgroup(s).