From: Bjorn Helgaas <helgaas@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
Subject: Re: [PATCH v7 0/2] PCI: Enable runtime pm of the host bridge
Date: Tue, 12 Nov 2024 17:44:32 -0600 [thread overview]
Message-ID: <20241112234432.GA1868852@bhelgaas> (raw)
In-Reply-To: <20241111-runtime_pm-v7-0-9c164eefcd87@quicinc.com>
On Mon, Nov 11, 2024 at 02:11:51PM +0530, Krishna chaitanya chundru wrote:
> It is a property of the runtime PM framework that it can only
> follow continuous dependency chains. That is, if there is a device
> with runtime PM disabled in a dependency chain, runtime PM cannot be
> enabled for devices below it and above it in that chain both at the
> same time.
>
> Since runtime PM is disabled for host bridge, the state of the child
> devices under the host bridge is not taken into account by PM framework
> for the top level parent, PCIe controller. So PM framework, allows
> the controller driver to enter runtime PM irrespective of the state
> of the devices under the host bridge.
>
> So enable runtime pm of the host bridge device, so that dependency
> chain in maintained between endpoint devices and the controller driver.
>
> PM framework expectes parent runtime pm enabled before enabling runtime
> pm of the child. As PCIe starfive device is enabling runtime pm after
> the pci_host_probe which enables runtime pm of the child device i.e for
> the bridge device a warning is shown saying "pcie-starfive 940000000.pcie:
> Enabling runtime PM for inactive device with active children" and also
> shows possible circular locking dependency detected message.
>
> As it is must to enable parent device's runtime PM before enabling child's
> runtime pm as the pcie-starfive device runtime pm is enabled after child
> runtime starfive device is seeing the warning.
>
> In the first patch fix the pcie-starfive driver by enabling runtime
> pm before calling pci_host_probe().
>
> All other PCIe controller drivers are enabling runtime pm before
> calling pci_host_probe() which is as expected so don't require any
> fix like pcie-starfive driver.
>
> Signed-off-by: Krishna chaitanya chundru <quic_krichai@quicinc.com>
Provisionally applied to pci/pm for v6.13. I see a typo or two, so
the commit logs will likely be updated, but I pushed the branch to get
build testing started.
> ---
> Changes in v7:
> - Bring the cover letter details to commit message as suggested by bjorn.
> - Add a comment in the driver to ensure pm_runtime_enable is called
> before host bridge pm_runtime_enable().
> - Link to v6: https://lore.kernel.org/r/20241017-runtime_pm-v6-0-55eab5c2c940@quicinc.com
> Changes in v6:
> - include the patch by mayank which fixes runtime pm enable order for
> pcie starfive driver.
> Changes in v5:
> - call pm_runtime_no_callbacks() as suggested by Rafael.
> - include the commit texts as suggested by Rafael.
> - Link to v4: https://lore.kernel.org/linux-pci/20240708-runtime_pm-v4-1-c02a3663243b@quicinc.com/
> Changes in v4:
> - Changed pm_runtime_enable() to devm_pm_runtime_enable() (suggested by mayank)
> - Link to v3: https://lore.kernel.org/lkml/20240609-runtime_pm-v3-1-3d0460b49d60@quicinc.com/
> Changes in v3:
> - Moved the runtime API call's from the dwc driver to PCI framework
> as it is applicable for all (suggested by mani)
> - Updated the commit message.
> - Link to v2: https://lore.kernel.org/all/20240305-runtime_pm_enable-v2-1-a849b74091d1@quicinc.com
> Changes in v2:
> - Updated commit message as suggested by mani.
> - Link to v1: https://lore.kernel.org/r/20240219-runtime_pm_enable-v1-1-d39660310504@quicinc.com
>
> ---
> Krishna chaitanya chundru (1):
> PCI: Enable runtime pm of the host bridge
>
> Mayank Rana (1):
> PCI: starfive: Enable PCIe controller's runtime PM before probing host bridge
>
> drivers/pci/controller/plda/pcie-starfive.c | 10 +++++++---
> drivers/pci/probe.c | 11 +++++++++++
> 2 files changed, 18 insertions(+), 3 deletions(-)
> ---
> base-commit: 2f87d0916ce0d2925cedbc9e8f5d6291ba2ac7b2
> change-id: 20241016-runtime_pm-d3dbf41736b6
>
> Best regards,
> --
> Krishna chaitanya chundru <quic_krichai@quicinc.com>
>
prev parent reply other threads:[~2024-11-12 23:44 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
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 ` Bjorn Helgaas [this message]
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=20241112234432.GA1868852@bhelgaas \
--to=helgaas@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=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