From: Bjorn Helgaas <helgaas@kernel.org>
To: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
Cc: Bartosz Golaszewski <brgl@kernel.org>,
Manivannan Sadhasivam <mani@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI/pwrctrl: lock device when calling device_is_bound()
Date: Mon, 18 May 2026 17:32:57 -0500 [thread overview]
Message-ID: <20260518223257.GA649247@bhelgaas> (raw)
In-Reply-To: <20260518100700.47581-1-bartosz.golaszewski@oss.qualcomm.com>
On Mon, May 18, 2026 at 12:07:00PM +0200, Bartosz Golaszewski wrote:
> The kerneldoc for device_is_bound() states that it must be called with
> the device lock taken. Synchronize the two calls in pwrctrl core.
>
> Fixes: b35cf3b6aa1e ("PCI/pwrctrl: Add APIs to power on/off pwrctrl devices")
> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
Applied to pci/pwrctrl for v7.2, thanks!
> ---
> drivers/pci/pwrctrl/core.c | 26 +++++++++++++++-----------
> 1 file changed, 15 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/pci/pwrctrl/core.c b/drivers/pci/pwrctrl/core.c
> index 97cff5b8ca88..cd08d590483b 100644
> --- a/drivers/pci/pwrctrl/core.c
> +++ b/drivers/pci/pwrctrl/core.c
> @@ -161,10 +161,12 @@ static void pci_pwrctrl_power_off_device(struct device_node *np)
> if (!pdev)
> return;
>
> - if (device_is_bound(&pdev->dev)) {
> - ret = __pci_pwrctrl_power_off_device(&pdev->dev);
> - if (ret)
> - dev_err(&pdev->dev, "Failed to power off device: %d", ret);
> + scoped_guard(device, &pdev->dev) {
> + if (device_is_bound(&pdev->dev)) {
> + ret = __pci_pwrctrl_power_off_device(&pdev->dev);
> + if (ret)
> + dev_err(&pdev->dev, "Failed to power off device: %d", ret);
> + }
> }
>
> platform_device_put(pdev);
> @@ -205,7 +207,7 @@ static int __pci_pwrctrl_power_on_device(struct device *dev)
> static int pci_pwrctrl_power_on_device(struct device_node *np)
> {
> struct platform_device *pdev;
> - int ret;
> + int ret = 0;
>
> for_each_available_child_of_node_scoped(np, child) {
> ret = pci_pwrctrl_power_on_device(child);
> @@ -217,12 +219,14 @@ static int pci_pwrctrl_power_on_device(struct device_node *np)
> if (!pdev)
> return 0;
>
> - if (device_is_bound(&pdev->dev)) {
> - ret = __pci_pwrctrl_power_on_device(&pdev->dev);
> - } else {
> - /* FIXME: Use blocking wait instead of probe deferral */
> - dev_dbg(&pdev->dev, "driver is not bound\n");
> - ret = -EPROBE_DEFER;
> + scoped_guard(device, &pdev->dev) {
> + if (device_is_bound(&pdev->dev)) {
> + ret = __pci_pwrctrl_power_on_device(&pdev->dev);
> + } else {
> + /* FIXME: Use blocking wait instead of probe deferral */
> + dev_dbg(&pdev->dev, "driver is not bound\n");
> + ret = -EPROBE_DEFER;
> + }
> }
>
> platform_device_put(pdev);
> --
> 2.47.3
>
prev parent reply other threads:[~2026-05-18 22:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 10:07 [PATCH] PCI/pwrctrl: lock device when calling device_is_bound() Bartosz Golaszewski
2026-05-18 10:29 ` Manivannan Sadhasivam
2026-05-18 10:45 ` sashiko-bot
2026-05-18 22:32 ` 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=20260518223257.GA649247@bhelgaas \
--to=helgaas@kernel.org \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=bhelgaas@google.com \
--cc=brgl@kernel.org \
--cc=krishna.chundru@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mani@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.