From: Bjorn Helgaas <helgaas@kernel.org>
To: Feiyang Chen <chenfeiyang@loongson.cn>
Cc: bhelgaas@google.com, rafael.j.wysocki@intel.com,
mika.westerberg@linux.intel.com, anders.roxell@linaro.org,
linux-pci@vger.kernel.org, linux-pm@vger.kernel.org,
guyinggang@loongson.cn, siyanteng@loongson.cn,
chenhuacai@loongson.cn, loongson-kernel@lists.loongnix.cn,
chris.chenfeiyang@gmail.com,
"Rafael J . Wysocki" <rafael@kernel.org>
Subject: Re: [PATCH v3] PCI/PM: Only read PCI_PM_CTRL register when available
Date: Thu, 24 Aug 2023 16:59:04 -0500 [thread overview]
Message-ID: <20230824215904.GA604126@bhelgaas> (raw)
In-Reply-To: <20230824013738.1894965-1-chenfeiyang@loongson.cn>
On Thu, Aug 24, 2023 at 09:37:38AM +0800, Feiyang Chen wrote:
> When the current state is already PCI_D0, pci_power_up() will return
> 0 even though dev->pm_cap is not set. In that case, we should not
> read the PCI_PM_CTRL register in pci_set_full_power_state().
>
> There is nothing more needs to be done below in that case.
> Additionally, pci_power_up() has two callers only and the other one
> ignores the return value, so we can safely move the current state
> check from pci_power_up() to pci_set_full_power_state().
Does this fix a bug? I guess it does, because previously
pci_set_full_power_state() did a config read at 0 + PCI_PM_CTRL, i.e.,
offset 4, which is actually PCI_COMMAND, and set dev->current_state
based on that. So dev->current_state is now junk, right?
This might account for some "Refused to change power state from %s to D0"
messages.
How did you find this? It's nice if we can mention a symptom so
people can connect the problem with this fix.
This sounds like something that probably should have a stable tag?
> Fixes: e200904b275c ("PCI/PM: Split pci_power_up()")
> Signed-off-by: Feiyang Chen <chenfeiyang@loongson.cn>
> Reviewed-by: Rafael J. Wysocki <rafael@kernel.org>
> ---
> drivers/pci/pci.c | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
> index 60230da957e0..7e90ab7b47a1 100644
> --- a/drivers/pci/pci.c
> +++ b/drivers/pci/pci.c
> @@ -1242,9 +1242,6 @@ int pci_power_up(struct pci_dev *dev)
> else
> dev->current_state = state;
>
> - if (state == PCI_D0)
> - return 0;
> -
> return -EIO;
> }
>
> @@ -1302,8 +1299,12 @@ static int pci_set_full_power_state(struct pci_dev *dev)
> int ret;
>
> ret = pci_power_up(dev);
> - if (ret < 0)
> + if (ret < 0) {
> + if (dev->current_state == PCI_D0)
> + return 0;
> +
> return ret;
> + }
>
> pci_read_config_word(dev, dev->pm_cap + PCI_PM_CTRL, &pmcsr);
> dev->current_state = pmcsr & PCI_PM_CTRL_STATE_MASK;
> --
> 2.39.3
>
next prev parent reply other threads:[~2023-08-24 21:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 1:37 [PATCH v3] PCI/PM: Only read PCI_PM_CTRL register when available Feiyang Chen
2023-08-24 21:59 ` Bjorn Helgaas [this message]
2023-08-25 3:57 ` Feiyang Chen
2023-08-25 21:25 ` Bjorn Helgaas
2023-08-28 12:44 ` Yanteng Si
2023-08-29 16:52 ` 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=20230824215904.GA604126@bhelgaas \
--to=helgaas@kernel.org \
--cc=anders.roxell@linaro.org \
--cc=bhelgaas@google.com \
--cc=chenfeiyang@loongson.cn \
--cc=chenhuacai@loongson.cn \
--cc=chris.chenfeiyang@gmail.com \
--cc=guyinggang@loongson.cn \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=loongson-kernel@lists.loongnix.cn \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=siyanteng@loongson.cn \
/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).