From: Bjorn Helgaas <helgaas@kernel.org>
To: Haakon Bugge <haakon.bugge@oracle.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Johannes Thumshirn <morbidrsa@gmail.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] PCI: Initialize RCB from pci_configure_device
Date: Thu, 22 Jan 2026 04:22:57 -0600 [thread overview]
Message-ID: <20260122102257.GA1239174@bhelgaas> (raw)
In-Reply-To: <2C6ECE99-B9CD-4325-87D2-A2E212BDBDA3@oracle.com>
On Thu, Jan 22, 2026 at 09:42:46AM +0000, Haakon Bugge wrote:
> > On Wed, Jan 21, 2026 at 12:35:40PM +0100, Håkon Bugge wrote:
> > [snip]
>
> > RCB isn't meaningful for switches, so we'll read their LNKCTL
> > unnecessarily. I propose something like this, which also clears RCB
> > if it's set when it shouldn't be (I think this would indicate a
> > firmware defect):
> >
> > /*
> > * Per PCIe r7.0, sec 7.5.3.7, RCB is only meaningful in Root Ports
> > * (where it is read-only), Endpoints, and Bridges. It may only be
> > * set for Endpoints and Bridges if it is set in the Root Port.
> > */
> > if (!pci_is_pcie(dev) ||
> > pci_pcie_type(dev) == PCI_EXP_TYPE_ROOT_PORT ||
> > pci_pcie_type(dev) == PCI_EXP_TYPE_UPSTREAM ||
> > pci_pcie_type(dev) == PCI_EXP_TYPE_DOWNSTREAM ||
> > dev->is_virtfn)
>
> I see that sec 1.3.2 defines "Endpoints are classified as either
> legacy, PCI Express, or Root Complex Integrated Endpoints (RCiEPs)."
> But, shouldn't we also exclude Root Complex Event Collectors
> (PCI_EXP_TYPE_RC_EC)?
Yes, probably so.
next prev parent reply other threads:[~2026-01-22 10:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 11:35 [PATCH v2 0/2] PCI: Init RCB from pci_configure_device and fix program_hpx_type2 Håkon Bugge
2026-01-21 11:35 ` [PATCH v2 1/2] PCI: Initialize RCB from pci_configure_device Håkon Bugge
2026-01-21 17:41 ` Lukas Wunner
2026-01-21 19:13 ` Haakon Bugge
2026-01-21 22:40 ` Bjorn Helgaas
2026-01-22 9:42 ` Haakon Bugge
2026-01-22 10:22 ` Bjorn Helgaas [this message]
2026-01-22 10:36 ` Bjorn Helgaas
2026-01-22 10:49 ` Haakon Bugge
2026-01-22 11:04 ` Bjorn Helgaas
2026-01-22 11:12 ` Haakon Bugge
2026-01-22 11:35 ` Niklas Schnelle
2026-01-22 13:25 ` Haakon Bugge
2026-01-21 11:35 ` [PATCH v2 2/2] PCI/ACPI: Confine program_hpx_type2 to the AER bits Håkon Bugge
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=20260122102257.GA1239174@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=haakon.bugge@oracle.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=morbidrsa@gmail.com \
/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