All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Stefan Roese" <stefan.roese@mailbox.org>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH v2 2/2] PCI: Set RCB only when the Root Port has it set
Date: Fri, 02 Oct 2026 09:18:55 +0000	[thread overview]
Message-ID: <20261002091856.55CD51F00898@smtp.kernel.org> (raw)
In-Reply-To: <20261002091029.2225203-3-stefan.roese@mailbox.org>

> pci_configure_rcb() read-modify-writes Link Control of every endpoint
> at enumeration, also when RCB is clear in the Root Port and there is
> nothing to set. Not writing a register that has nothing to change is
> justified on its own, but the write-back of the other Link Control bits
> also has side effects on some devices: the Renesas uPD720201 xHCI
> (1912:0014) comes out of reset with ASPM L0s and L1 enabled and stops
> clearing them itself once Link Control has been written. On a link
> whose Root Port supports no ASPM, the previous patch clears them, but
> it does not run with pcie_aspm=off or CONFIG_PCIEASPM=n. There the
> first access to the xHCI BAR runs into completion timeouts that hang
> the system.
> 
> RCB may only be set in an endpoint if it is set in the Root Port, so
> there is no need to ever clear it here; an endpoint with RCB set
> below a Root Port without it is a firmware configuration error. Only
> set RCB, and only when the Root Port has it set.
> 
> Fixes: 1a6845aaa6de ("PCI: Initialize RCB from pci_configure_device()")
> Cc: stable@vger.kernel.org
> Suggested-by: Bjorn Helgaas <bhelgaas@google.com>
> Assisted-by: Claude:claude-opus-5-5
> Signed-off-by: Stefan Roese <stefan.roese@mailbox.org>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261002091029.2225203-1-stefan.roese@mailbox.org?part=2


      reply	other threads:[~2026-10-02  9:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02  9:10 [PATCH v2 0/2] PCI: Fix Renesas uPD720201 hang after the RCB Link Control write Stefan Roese
2026-10-02  9:10 ` [PATCH v2 1/2] PCI/ASPM: Clear ASPM Control on links without common ASPM support Stefan Roese
2026-10-02  9:21   ` sashiko-bot
2026-10-02  9:10 ` [PATCH v2 2/2] PCI: Set RCB only when the Root Port has it set Stefan Roese
2026-10-02  9:18   ` sashiko-bot [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=20261002091856.55CD51F00898@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=stefan.roese@mailbox.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.