From: Johan Hovold <johan@kernel.org>
To: Krishna Chaitanya Chundru <quic_krichai@quicinc.com>
Cc: "Kevin Xie" <kevin.xie@starfivetech.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
Markus.Elfring@web.de, quic_mrana@quicinc.com, rafael@kernel.org,
m.szyprowski@samsung.com, linux-pm@vger.kernel.org,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
regressions@lists.linux.dev
Subject: Re: [PATCH v7 2/2] PCI: Enable runtime pm of the host bridge
Date: Tue, 7 Jan 2025 15:27:59 +0100 [thread overview]
Message-ID: <Z3057yuNjnn0NPqk@hovoldconsulting.com> (raw)
In-Reply-To: <7882105f-93a3-fab9-70a2-2dc55d6becfc@quicinc.com>
On Tue, Jan 07, 2025 at 07:40:39PM +0530, Krishna Chaitanya Chundru wrote:
> On 1/7/2025 6:49 PM, Johan Hovold wrote:
> >> @@ -3106,6 +3106,17 @@ int pci_host_probe(struct pci_host_bridge *bridge)
> >> pcie_bus_configure_settings(child);
> >>
> >> pci_bus_add_devices(bus);
> >> +
> >> + /*
> >> + * Ensure pm_runtime_enable() is called for the controller drivers,
> >> + * before calling pci_host_probe() as pm frameworks expects if the
> >> + * parent device supports runtime pm then it needs to enabled before
> >> + * child runtime pm.
> >> + */
> >> + pm_runtime_set_active(&bridge->dev);
> >> + pm_runtime_no_callbacks(&bridge->dev);
> >> + devm_pm_runtime_enable(&bridge->dev);
> >> +
> >> return 0;
> >> }
> >> EXPORT_SYMBOL_GPL(pci_host_probe);
> >
> > I just noticed that this change in 6.13-rc1 is causing the following
> > warning on resume from suspend on machines like the Lenovo ThinkPad
> > X13s:
> Can you confirm if you are seeing this issue is seen in the boot-up
> case also. As this part of the code executes only at the boot time and
> will not have effect in resume from suspend.
No, I only see it during resume. And enabling runtime PM can (and in
this case, obviously does) impact system suspend as well.
> > pci0004:00: pcie4: Enabling runtime PM for inactive device with active children
> I believe this is not causing any functional issues.
It still needs to be fixed.
> > which may have unpopulated ports (this laptop SKU does not have a modem).
> Can you confirm if this warning goes away if there is some endpoint
> connected to it.
I don't have anything to connect to the slot in this machine, but this
seems to be the case as I do not see this warning for the populated
slots, nor on the CRD reference design which has a modem on PCIe4.
Johan
next prev parent reply other threads:[~2025-01-07 14:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 8:41 [PATCH v7 0/2] PCI: Enable runtime pm of the host bridge Krishna chaitanya chundru
2024-11-11 8:41 ` [PATCH v7 1/2] PCI: starfive: Enable PCIe controller's runtime PM before probing " Krishna chaitanya chundru
2024-11-11 8:41 ` [PATCH v7 2/2] PCI: Enable runtime pm of the " Krishna chaitanya chundru
2024-11-11 16:46 ` Markus Elfring
2024-11-13 5:24 ` Krishna Chaitanya Chundru
2025-01-07 13:19 ` Johan Hovold
2025-01-07 14:10 ` Krishna Chaitanya Chundru
2025-01-07 14:27 ` Johan Hovold [this message]
2025-01-13 16:25 ` Manivannan Sadhasivam
2025-01-14 21:16 ` Bjorn Helgaas
2025-01-19 15:29 ` Manivannan Sadhasivam
2025-01-20 10:29 ` Johan Hovold
2025-01-20 15:28 ` Manivannan Sadhasivam
2025-01-21 13:18 ` Johan Hovold
2025-01-21 13:34 ` Johan Hovold
2025-01-24 5:15 ` Manivannan Sadhasivam
2025-01-27 14:31 ` Ulf Hansson
2025-01-27 19:57 ` Rafael J. Wysocki
2025-01-28 11:47 ` Rafael J. Wysocki
2025-01-28 15:58 ` Manivannan Sadhasivam
2025-01-28 16:07 ` Rafael J. Wysocki
2024-11-12 23:44 ` [PATCH v7 0/2] " 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=Z3057yuNjnn0NPqk@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=Markus.Elfring@web.de \
--cc=bhelgaas@google.com \
--cc=kevin.xie@starfivetech.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=manivannan.sadhasivam@linaro.org \
--cc=quic_krichai@quicinc.com \
--cc=quic_mrana@quicinc.com \
--cc=rafael@kernel.org \
--cc=regressions@lists.linux.dev \
--cc=robh@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