From: "Håkon Bugge" <haakon.bugge@oracle.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Johannes Thumshirn <morbidrsa@gmail.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org
Subject: [PATCH v2 0/2] PCI: Init RCB from pci_configure_device and fix program_hpx_type2
Date: Wed, 21 Jan 2026 12:35:39 +0100 [thread overview]
Message-ID: <20260121113544.4163457-1-haakon.bugge@oracle.com> (raw)
This series add the initialization of the Link Control register's RCB
to pci_configure_rcb() called from pci_configure_device() and also
cleans up the incorrect program_hpx_type2():
1. It should only be called when we own the PCIe native hotplug and
not the AER ownership
2. It should only manipulate the AER-bits
In addition, the second commit adds a warning if the _HPX type2
record attempts to modify the Link Control register.
Håkon Bugge (2):
PCI: Initialize RCB from pci_configure_device
PCI/ACPI: Confine program_hpx_type2 to the AER bits
drivers/pci/pci-acpi.c | 61 +++++++++++++++++++-----------------------
drivers/pci/pci.h | 3 +++
drivers/pci/pcie/aer.c | 3 ---
drivers/pci/probe.c | 27 +++++++++++++++++++
4 files changed, 57 insertions(+), 37 deletions(-)
--
2.43.5
next reply other threads:[~2026-01-21 11:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 11:35 Håkon Bugge [this message]
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
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=20260121113544.4163457-1-haakon.bugge@oracle.com \
--to=haakon.bugge@oracle.com \
--cc=bhelgaas@google.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