[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <E8CB259F-49BB-47FB-8D41-591DD302F168@oracle.com>
Date: Thu, 29 Jan 2026 16:36:10 +0000
From: Haakon Bugge <haakon.bugge@...cle.com>
To: Bjorn Helgaas <helgaas@...nel.org>
CC: Bjorn Helgaas <bhelgaas@...gle.com>,
Niklas Schnelle
<schnelle@...ux.ibm.com>,
"Rafael J. Wysocki" <rafael@...nel.org>, Len Brown
<lenb@...nel.org>,
Mahesh J Salgaonkar <mahesh@...ux.ibm.com>,
Oliver
O'Halloran <oohall@...il.com>,
Greg Kroah-Hartman <gregkh@...e.de>,
Kenji
Kaneshige <kaneshige.kenji@...fujitsu.com>,
Alex Williamson
<alex@...zbot.org>,
Johannes Thumshirn <morbidrsa@...il.com>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>
Subject: Re: [PATCH v3 2/2] PCI/ACPI: Confine program_hpx_type2 to the AER
bits
>>> Thanks for the word-smithing and improved accuracy!
>>>
>>> + /* Log if _HPX attempts to modify PCIe Link Control register */
>>> if (pcie_cap_has_lnkctl(dev)) {
>>> -
>>> - /*
>>> - * If the Root Port supports Read Completion Boundary of
>>> - * 128, set RCB to 128. Otherwise, clear it.
>>> - */
>>> - hpx->pci_exp_lnkctl_and |= PCI_EXP_LNKCTL_RCB;
>>> - hpx->pci_exp_lnkctl_or &= ~PCI_EXP_LNKCTL_RCB;
>>> - if (pcie_root_rcb_set(dev))
>>> - hpx->pci_exp_lnkctl_or |= PCI_EXP_LNKCTL_RCB;
>>> -
>>> - pcie_capability_clear_and_set_word(dev, PCI_EXP_LNKCTL,
>>> - ~hpx->pci_exp_lnkctl_and, hpx->pci_exp_lnkctl_or);
>>>
> This was what confused me a lot, the bit-wise NOT above. That must be wrong, as pcie_capability_clear_and_set_word() inverts the "clear" argument.
Have to correct myself here. ACPI states:
When configuring a given register, OSPM uses the following algorithm:
1. Read the register’s current value, which contains the register’s default value.
2. Perform a bit-wise AND operation with the “AND mask” from the table below.
[]
Because pcie_capability_clear_and_set_word() inverts the "clear" argument, the above bitwise NOT is of course correct. Two bitwise NOTs is a no-op and we follow the ACPI outlined algorithm.
Sorry for the noise, Håkon
Powered by blists - more mailing lists