Linux PCI subsystem development
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>
Cc: bhelgaas@google.com, linux-pci@vger.kernel.org,
	 LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] PCI/ASPM: Fix a typo in ASPM restoring logic
Date: Mon, 6 May 2024 17:44:57 +0300 (EEST)	[thread overview]
Message-ID: <c74f0256-1453-3b91-d5a7-d797a0c2da90@linux.intel.com> (raw)
In-Reply-To: <20240506051602.1990743-1-kai.heng.feng@canonical.com>

[-- Attachment #1: Type: text/plain, Size: 1226 bytes --]

On Mon, 6 May 2024, Kai-Heng Feng wrote:

> There's a typo that makes parent device uses child LNKCTL value and vice
> versa. This causes Micron NVMe to trigger a reboot upon system resume.
> 
> Correct the typo to fix the issue.
> 
> Fixes: 64dbb2d70744 ("PCI/ASPM: Disable L1 before configuring L1 Substates")
> Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
> ---
>  drivers/pci/pcie/aspm.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/pci/pcie/aspm.c b/drivers/pci/pcie/aspm.c
> index 2428d278e015..47761c7ef267 100644
> --- a/drivers/pci/pcie/aspm.c
> +++ b/drivers/pci/pcie/aspm.c
> @@ -177,8 +177,8 @@ void pci_restore_aspm_l1ss_state(struct pci_dev *pdev)
>  	/* Restore L0s/L1 if they were enabled */
>  	if (FIELD_GET(PCI_EXP_LNKCTL_ASPMC, clnkctl) ||
>  	    FIELD_GET(PCI_EXP_LNKCTL_ASPMC, plnkctl)) {
> -		pcie_capability_write_word(parent, PCI_EXP_LNKCTL, clnkctl);
> -		pcie_capability_write_word(pdev, PCI_EXP_LNKCTL, plnkctl);
> +		pcie_capability_write_word(parent, PCI_EXP_LNKCTL, plnkctl);
> +		pcie_capability_write_word(pdev, PCI_EXP_LNKCTL, clnkctl);

Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>

-- 
 i.

  reply	other threads:[~2024-05-06 14:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06  5:16 [PATCH] PCI/ASPM: Fix a typo in ASPM restoring logic Kai-Heng Feng
2024-05-06 14:44 ` Ilpo Järvinen [this message]
2024-05-06 19:24 ` 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=c74f0256-1453-3b91-d5a7-d797a0c2da90@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=bhelgaas@google.com \
    --cc=kai.heng.feng@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.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