Changes in Kconfig

bb115505a9f1f79b888aa0ccb28f42f05edea07f - PCI: Remove MPS/MRRS Kconfig settings (CONFIG_PCIE_BUS_*)

Thu, 26 Mar 2026 23:13:11 +0100

PCI: Remove MPS/MRRS Kconfig settings (CONFIG_PCIE_BUS_*)Revert b0e85c3c8554 ("PCI: Add Kconfig options for MPS/MRRS strategy"),which allowed build-time selection of the "off", "default", "safe","performance", or "peer2peer" strategies for MPS and MRRS configuration.These strategies can be selected at boot-time using the"pci=pcie_bus_tune_*" kernel parameters.Per the discussion mentioned below, these Kconfig options were added towork around a hardware defect in a WiFi device used in a cable modem. Thedefect occurred only when the device was configured with MPS=128, andKconfig was a way to avoid that setting. It was easier for the modemvendor to use Kconfig and update the kernel image than to change the kernelparameters.Neither Kconfig nor kernel parameters are a complete solution because thebroken WiFi device may be used in other systems where it may be configuredwith MPS=128 and be susceptible to the defect.Remove the Kconfig settings to simplify the MPS code. If we can identifythe WiFi device in question, we may be able to make a generic quirk toavoid the problem on all system.This is not a fix and should not be backported to previous kernels.Link: https://lore.kernel.org/all/CA+-6iNzd0RJO0L021qz8CKrSviSst6QehY-QtJxz_-EVY0Hj0Q@mail.gmail.comSigned-off-by: Bjorn Helgaas Link: https://patch.msgid.link/20260326221311.1356180-1-bhelgaas@google.com List of files: /linux/drivers/pci/Kconfig

7010f13acd3828056e50badb5138bf9ca21ddd8f - PCI: Clean up dead code in Kconfig

Mon, 30 Mar 2026 23:45:49 +0200

PCI: Clean up dead code in KconfigThere is already an 'if PCI' condition wrapping several config options,e.g., PCI_DOMAINS and VGA_ARB, making the 'depends on PCI' statement foreach of these a duplicate dependency (dead code).Leave the outer 'if PCI...endif' and remove the individual 'depends on PCI'statement from each option.This dead code was found by kconfirm, a static analysis tool for Kconfig.Signed-off-by: Julian Braha Signed-off-by: Bjorn Helgaas Link: https://patch.msgid.link/20260330214549.16157-1-julianbraha@gmail.com List of files: /linux/drivers/pci/Kconfig

269031b15c1433ff39e30fa7ea3ab8f0be9d6ae2 - x86/kaslr: Recognize all ZONE_DEVICE users as physaddr consumers

Fri, 07 Nov 2025 00:13:50 +0100

x86/kaslr: Recognize all ZONE_DEVICE users as physaddr consumersCommit 7ffb791423c7 ("x86/kaslr: Reduce KASLR entropy on most x86 systems")is too narrow. The effect being mitigated in that commit is caused byZONE_DEVICE which PCI_P2PDMA has a dependency. ZONE_DEVICE, in general,lets any physical address be added to the direct-map. I.e. not only ACPIhotplug ranges, CXL Memory Windows, or EFI Specific Purpose Memory, butalso any PCI MMIO range for the DEVICE_PRIVATE and PCI_P2PDMA cases. Updatethe mitigation, limit KASLR entropy, to apply in all ZONE_DEVICE=y cases.Distro kernels typically have PCI_P2PDMA=y, so the practical exposure ofthis problem is limited to the PCI_P2PDMA=n case.A potential path to recover entropy would be to walk ACPI and determine thelimits for hotplug and PCI MMIO before kernel_randomize_memory(). Onsmaller systems that could yield some KASLR address bits. This needsadditional investigation to determine if some limited ACPI table scanningcan happen this early without an open coded solution likearch/x86/boot/compressed/acpi.c needs to deploy.Cc: Ingo Molnar Cc: Kees Cook Cc: Bjorn Helgaas Cc: Peter Zijlstra Cc: Andy Lutomirski Cc: Logan Gunthorpe Cc: Andrew Morton Cc: David Hildenbrand Cc: Lorenzo Stoakes Cc: "Liam R. Howlett" Cc: Vlastimil Babka Cc: Mike Rapoport Cc: Suren Baghdasaryan Cc: Michal Hocko Fixes: 7ffb791423c7 ("x86/kaslr: Reduce KASLR entropy on most x86 systems")Cc: Signed-off-by: Dan Williams Reviewed-by: Balbir Singh Tested-by: Yasunori Goto Acked-by: Dave Hansen Link: http://patch.msgid.link/692e08b2516d4_261c1100a3@dwillia2-mobl4.notmuchSigned-off-by: Dave Jiang List of files: /linux/drivers/pci/Kconfig

3225f52cde56f46789a4972d3c54df8a4d75f022 - PCI/TSM: Establish Secure Sessions and Link Encryption

Fri, 31 Oct 2025 22:28:56 +0100

PCI/TSM: Establish Secure Sessions and Link EncryptionThe PCIe 7.0 specification, section 11, defines the Trusted ExecutionEnvironment (TEE) Device Interface Security Protocol (TDISP). Thisprotocol definition builds upon Component Measurement and Authentication(CMA), and link Integrity and Data Encryption (IDE). It adds support forassigning devices (PCI physical or virtual function) to a confidential VMsuch that the assigned device is enabled to access guest private memoryprotected by technologies like Intel TDX, AMD SEV-SNP, RISCV COVE, or ARMCCA.The "TSM" (TEE Security Manager) is a concept in the TDISP specificationof an agent that mediates between a "DSM" (Device Security Manager) andsystem software in both a VMM and a confidential VM. A VMM uses TSM ABIsto setup link security and assign devices. A confidential VM uses TSMABIs to transition an assigned device into the TDISP "RUN" state andvalidate its configuration. From a Linux perspective the TSM abstractsmany of the details of TDISP, IDE, and CMA. Some of those details leakthrough at times, but for the most part TDISP is an internalimplementation detail of the TSM.CONFIG_PCI_TSM adds an "authenticated" attribute and "tsm/" subdirectoryto pci-sysfs. Consider that the TSM driver may itself be a PCI driver.Userspace can watch for the arrival of a "TSM" device,/sys/class/tsm/tsm0/uevent KOBJ_CHANGE, to know when the PCI core hasinitialized TSM services.The operations that can be executed against a PCI device are split intotwo mutually exclusive operation sets, "Link" and "Security" (structpci_tsm_{link,security}_ops). The "Link" operations manage physical linksecurity properties and communication with the device's Device SecurityManager firmware. These are the host side operations in TDISP. The"Security" operations coordinate the security state of the assignedvirtual device (TDI). These are the guest side operations in TDISP.Only "link" (Secure Session and physical Link Encryption) operations aredefined at this stage. There are placeholders for the device security(Trusted Computing Base entry / exit) operations.The locking allows for multiple devices to be executing commandssimultaneously, one outstanding command per-device and an rwsemsynchronizes the implementation relative to TSM registration/unregistrationevents.Thanks to Wu Hao for his work on an early draft of this support.Cc: Lukas Wunner Cc: Samuel Ortiz Acked-by: Bjorn Helgaas Reviewed-by: Jonathan Cameron Reviewed-by: Alexey Kardashevskiy Co-developed-by: Xu Yilun Signed-off-by: Xu Yilun Link: https://patch.msgid.link/20251031212902.2256310-5-dan.j.williams@intel.comSigned-off-by: Dan Williams List of files: /linux/drivers/pci/Kconfig

f16469ee733ac52b2373216803699cbb05e82786 - PCI/IDE: Enumerate Selective Stream IDE capabilities

Fri, 31 Oct 2025 22:28:54 +0100

PCI/IDE: Enumerate Selective Stream IDE capabilitiesLink encryption is a new PCIe feature enumerated by "PCIe r7.0 section7.9.26 IDE Extended Capability".It is both a standalone port + endpoint capability, and a building blockfor the security protocol defined by "PCIe r7.0 section 11 TEE DeviceInterface Security Protocol (TDISP)". That protocol coordinates devicesecurity setup between a platform TSM (TEE Security Manager) and adevice DSM (Device Security Manager). While the platform TSM canallocate resources like Stream ID and manage keys, it still requiressystem software to manage the IDE capability register block.Add register definitions and basic enumeration in preparation forSelective IDE Stream establishment. A follow on change selects the newCONFIG_PCI_IDE symbol. Note that while the IDE specification definesboth a point-to-point "Link Stream" and a Root Port to endpoint"Selective Stream", only "Selective Stream" is considered for Linux asthat is the predominant mode expected by Trusted Execution EnvironmentSecurity Managers (TSMs), and it is the security model that limits thenumber of PCI components within the TCB in a PCIe topology withswitches.Co-developed-by: Alexey Kardashevskiy Signed-off-by: Alexey Kardashevskiy Co-developed-by: Xu Yilun Signed-off-by: Xu Yilun Reviewed-by: Jonathan Cameron Reviewed-by: Alexey Kardashevskiy Reviewed-by: Aneesh Kumar K.V Link: https://patch.msgid.link/20251031212902.2256310-3-dan.j.williams@intel.comSigned-off-by: Dan Williams List of files: /linux/drivers/pci/Kconfig

a78835b86a4414230e4cf9a9f16d22302cdb8388 - PCI/VGA: Select SCREEN_INFO on X86

Tue, 14 Oct 2025 00:08:26 +0200

PCI/VGA: Select SCREEN_INFO on X86commit 337bf13aa9dda ("PCI/VGA: Replace vga_is_firmware_default() with ascreen info check") introduced an implicit dependency upon SCREEN_INFO byremoving the open coded implementation.If a user didn't have CONFIG_SCREEN_INFO set, vga_is_firmware_default()would now return false. SCREEN_INFO is only used on X86 so add aconditional select for SCREEN_INFO to ensure that the VGA arbiter works asintended.Fixes: 337bf13aa9dda ("PCI/VGA: Replace vga_is_firmware_default() with a screen info check")Reported-by: Eric Biggers Closes: https://lore.kernel.org/linux-pci/20251012182302.GA3412@sol/Suggested-by: Thomas Zimmermann Signed-off-by: Mario Limonciello (AMD) Signed-off-by: Bjorn Helgaas Reviewed-by: Thomas Zimmermann Reviewed-by: Ilpo Järvinen Tested-by: Eric Biggers Link: https://patch.msgid.link/20251013220829.1536292-1-superm1@kernel.org List of files: /linux/drivers/pci/Kconfig

94b04355e6397a0a70b69c2571fa5c7d9990b835 - Drivers: hv: Add CONFIG_HYPERV_VMBUS option

Tue, 16 Sep 2025 01:46:03 +0200

Drivers: hv: Add CONFIG_HYPERV_VMBUS optionAt present VMBus driver is hinged off of CONFIG_HYPERV which entailslot of builtin code and encompasses too much. It's not always clearwhat depends on builtin hv code and what depends on VMBus. SettingCONFIG_HYPERV as a module and fudging the Makefile to switch to builtinadds even more confusion. VMBus is an independent module and should haveits own config option. Also, there are scenarios like baremetal dom0/rootwhere support is built in with CONFIG_HYPERV but without VMBus. Lastly,there are more features coming down that use CONFIG_HYPERV and add moredependencies on it.So, create a fine grained HYPERV_VMBUS option and update Kconfigs fordependency on VMBus.Signed-off-by: Mukesh Rathor Acked-by: Bjorn Helgaas # drivers/pciSigned-off-by: Wei Liu List of files: /linux/drivers/pci/Kconfig

5f83d6337c9c436d7b1a6580ca060122cb937551 - PCI: hv: Switch to msi_create_parent_irq_domain()

Mon, 07 Jul 2025 10:20:16 +0200

PCI: hv: Switch to msi_create_parent_irq_domain()Move away from the legacy MSI domain setup, switch to usemsi_create_parent_irq_domain().While doing the conversion, I noticed that hv_compose_msi_msg() is doingmore than it is supposed to (composing message). This function alsoallocates and populates struct tran_int_desc, which should be done inhv_pcie_domain_alloc() instead. It works, but it is not the correct design.However, I have no hardware to test such change, therefore I leave a TODOnote.Acked-by: Bjorn Helgaas Reviewed-by: Thomas Gleixner Signed-off-by: Nam Cao Reviewed-by: Michael Kelley Tested-by: Michael Kelley Signed-off-by: David S. Miller List of files: /linux/drivers/pci/Kconfig

8fe743b5eba0abfbee39fe27b12acfb0df9b8a2d - PCI: Add CONFIG_MMU dependency

Wed, 23 Apr 2025 22:16:32 +0200

PCI: Add CONFIG_MMU dependencyIt turns out that there are no platforms that have PCI but don't have anMMU, so adding a Kconfig dependency on CONFIG_PCI simplifies build testingkernels for those platforms a lot, and avoids a lot of inadvertent buildregressions.Add a dependency for CONFIG_PCI and remove all the ones for PCI specificdevice drivers that are currently marked not having it.There are a few platforms that have an optional MMU, but they usuallycannot have PCI at all. The one exception is Coldfire MCF54xx, but this ismainly for historic reasons, and anyone using those chips should really usethe MMU these days.Link: https://lore.kernel.org/lkml/a41f1b20-a76c-43d8-8c36-f12744327a54@app.fastmail.com/Signed-off-by: Arnd Bergmann Signed-off-by: Bjorn Helgaas Reviewed-by: Martin K. Petersen # SCSIReviewed-by: Thomas Zimmermann Acked-by: Alex Deucher Link: https://patch.msgid.link/20250423202215.3315550-1-arnd@kernel.org List of files: /linux/drivers/pci/Kconfig

7d06015d936c861160803e020f68f413b5c3cd9d - Merge tag 'pci-v6.15-changes' of git://git.kernel.org/pub/scm/linux/kernel/git/pci/pci

Sat, 29 Mar 2025 03:36:53 +0100

Merge tag 'pci-v6.15-changes' of git://git.kernel.org/pub/scm/linux/kernel/git/pci/pciPull pci updates from Bjorn Helgaas: "Enumeration: - Enable Configuration RRS SV, which makes device readiness visible, early instead of during child bus scanning (Bjorn Helgaas) - Log debug messages about reset methods being used (Bjorn Helgaas) - Avoid reset when it has been disabled via sysfs (Nishanth Aravamudan) - Add common pci-ep-bus.yaml schema for exporting several peripherals of a single PCI function via devicetree (Andrea della Porta) - Create DT nodes for PCI host bridges to enable loading device tree overlays to create platform devices for PCI devices that have several features that require multiple drivers (Herve Codina) Resource management: - Enlarge devres table[] to accommodate bridge windows, ROM, IOV BARs, etc., and validate BAR index in devres interfaces (Philipp Stanner) - Fix typo that repeatedly distributed resources to a bridge instead of iterating over subordinate bridges, which resulted in too little space to assign some BARs (Kai-Heng Feng) - Relax bridge window tail sizing for optional resources, e.g., IOV BARs, to avoid failures when removing and re-adding devices (Ilpo Järvinen) - Allow drivers to enable devices even if we haven't assigned optional IOV resources to them (Ilpo Järvinen) - Rework handling of optional resources (IOV BARs, ROMs) to reduce failures if we can't allocate them (Ilpo Järvinen) - Fix a NULL dereference in the SR-IOV VF creation error path (Shay Drory) - Fix s390 mmio_read/write syscalls, which didn't cause page faults in some cases, which broke vfio-pci lazy mapping on first access (Niklas Schnelle) - Add pdev->non_mappable_bars to replace CONFIG_VFIO_PCI_MMAP, which was disabled only for s390 (Niklas Schnelle) - Support mmap of PCI resources on s390 except for ISM devices (Niklas Schnelle) ASPM: - Delay pcie_link_state deallocation to avoid dangling pointers that cause invalid references during hot-unplug (Daniel Stodden) Power management: - Allow PCI bridges to go to D3Hot when suspending on all non-x86 systems (Manivannan Sadhasivam) Power control: - Create pwrctrl devices in pci_scan_device() to make it more symmetric with pci_pwrctrl_unregister() and make pwrctrl devices for PCI bridges possible (Manivannan Sadhasivam) - Unregister pwrctrl devices in pci_destroy_dev() so DOE, ASPM, etc. can still access devices after pci_stop_dev() (Manivannan Sadhasivam) - If there's a pwrctrl device for a PCI device, skip scanning it because the pwrctrl core will rescan the bus after the device is powered on (Manivannan Sadhasivam) - Add a pwrctrl driver for PCI slots based on voltage regulators described via devicetree (Manivannan Sadhasivam) Bandwidth control: - Add set_pcie_speed.sh to TEST_PROGS to fix issue when executing the set_pcie_cooling_state.sh test case (Yi Lai) - Avoid a NULL pointer dereference when we run out of bus numbers to assign for a bridge secondary bus (Lukas Wunner) Hotplug: - Drop superfluous pci_hotplug_slot_list, try_module_get() calls, and NULL pointer checks (Lukas Wunner) - Drop shpchp module init/exit logging, replace shpchp dbg() with ctrl_dbg(), and remove unused dbg(), err(), info(), warn() wrappers (Ilpo Järvinen) - Drop 'shpchp_debug' module parameter in favor of standard dynamic debugging (Ilpo Järvinen) - Drop unused cpcihp .get_power(), .set_power() function pointers (Guilherme Giacomo Simoes) - Disable hotplug interrupts in portdrv only when pciehp is not enabled to avoid issuing two hotplug commands too close together (Feng Tang) - Skip pciehp 'device replaced' check if the device has been removed to address a deadlock when resuming after a device was removed during system sleep (Lukas Wunner) - Don't enable pciehp hotplug interupt when resuming in poll mode (Ilpo Järvinen) Virtualization: - Fix bugs in 'pci=config_acs=' kernel command line parameter (Tushar Dave) DOE: - Expose supported DOE features via sysfs (Alistair Francis) - Allow DOE support to be enabled even if CXL isn't enabled (Alistair Francis) Endpoint framework: - Convert PCI device data so pci-epf-test works correctly on big-endian endpoint systems (Niklas Cassel) - Add BAR_RESIZABLE type to endpoint framework and add DWC core support for EPF drivers to set BAR_RESIZABLE type and size (Niklas Cassel) - Fix pci-epf-test double free that causes an oops if the host reboots and PERST# deassertion restarts endpoint BAR allocation (Christian Bruel) - Fix endpoint BAR testing so tests can skip disabled BARs instead of reporting them as failures (Niklas Cassel) - Widen endpoint test BAR size variable to accommodate BARs larger than INT_MAX (Niklas Cassel) - Remove unused tools 'pci' build target left over after moving tests to tools/testing/selftests/pci_endpoint (Jianfeng Liu) Altera PCIe controller driver: - Add DT binding and driver support for Agilex family (P-Tile, F-Tile, R-Tile) (Matthew Gerlach and D M, Sharath Kumar) AMD MDB PCIe controller driver: - Add DT binding and driver for AMD MDB (Multimedia DMA Bridge) (Thippeswamy Havalige) Broadcom STB PCIe controller driver: - Add BCM2712 MSI-X DT binding and interrupt controller drivers and add softdep on irq_bcm2712_mip driver to ensure that it is loaded first (Stanimir Varbanov) - Expand inbound window map to 64GB so it can accommodate BCM2712 (Stanimir Varbanov) - Add BCM2712 support and DT updates (Stanimir Varbanov) - Apply link speed restriction before bringing link up, not after (Jim Quinlan) - Update Max Link Speed in Link Capabilities via the internal writable register, not the read-only config register (Jim Quinlan) - Handle regulator_bulk_get() error to avoid panic when we call regulator_bulk_free() later (Jim Quinlan) - Disable regulators only when removing the bus immediately below a Root Port because we don't support regulators deeper in the hierarchy (Jim Quinlan) - Make const read-only arrays static (Colin Ian King) Cadence PCIe endpoint driver: - Correct MSG TLP generation so endpoints can generate INTx messages (Hans Zhang) Freescale i.MX6 PCIe controller driver: - Identify the second controller on i.MX8MQ based on devicetree 'linux,pci-domain' instead of DBI 'reg' address (Richard Zhu) - Remove imx_pcie_cpu_addr_fixup() since dwc core can now derive the ATU input address (using parent_bus_offset) from devicetree (Frank Li) Freescale Layerscape PCIe controller driver: - Drop deprecated 'num-ib-windows' and 'num-ob-windows' and unnecessary 'status' from example (Krzysztof Kozlowski) - Correct the syscon_regmap_lookup_by_phandle_args("fsl,pcie-scfg") arg_count to fix probe failure on LS1043A (Ioana Ciornei) HiSilicon STB PCIe controller driver: - Call phy_exit() to clean up if histb_pcie_probe() fails (Christophe JAILLET) Intel Gateway PCIe controller driver: - Remove intel_pcie_cpu_addr() since dwc core can now derive the ATU input address (using parent_bus_offset) from devicetree (Frank Li) Intel VMD host bridge driver: - Convert vmd_dev.cfg_lock from spinlock_t to raw_spinlock_t so pci_ops.read() will never sleep, even on PREEMPT_RT where spinlock_t becomes a sleepable lock, to avoid calling a sleeping function from invalid context (Ryo Takakura) MediaTek PCIe Gen3 controller driver: - Remove leftover mac_reset assert for Airoha EN7581 SoC (Lorenzo Bianconi) - Add EN7581 PBUS controller 'mediatek,pbus-csr' DT property and program host bridge memory aperture to this syscon node (Lorenzo Bianconi) Qualcomm PCIe controller driver: - Add qcom,pcie-ipq5332 binding (Varadarajan Narayanan) - Add qcom i.MX8QM and i.MX8QXP/DXP optional DMA interrupt (Alexander Stein) - Add optional dma-coherent DT property for Qualcomm SA8775P (Dmitry Baryshkov) - Make DT iommu property required for SA8775P and prohibited for SDX55 (Dmitry Baryshkov) - Add DT IOMMU and DMA-related properties for Qualcomm SM8450 (Dmitry Baryshkov) - Add endpoint DT properties for SAR2130P and enable endpoint mode in driver (Dmitry Baryshkov) - Describe endpoint BAR0 and BAR2 as 64-bit only and BAR1 and BAR3 as RESERVED (Manivannan Sadhasivam) Rockchip DesignWare PCIe controller driver: - Describe rk3568 and rk3588 BARs as Resizable, not Fixed (Niklas Cassel) Synopsys DesignWare PCIe controller driver: - Add debugfs-based Silicon Debug, Error Injection, Statistical Counter support for DWC (Shradha Todi) - Add debugfs property to expose LTSSM status of DWC PCIe link (Hans Zhang) - Add Rockchip support for DWC debugfs features (Niklas Cassel) - Add dw_pcie_parent_bus_offset() to look up the parent bus address of a specified 'reg' property and return the offset from the CPU physical address (Frank Li) - Use dw_pcie_parent_bus_offset() to derive CPU -> ATU addr offset via 'reg[config]' for host controllers and 'reg[addr_space]' for endpoint controllers (Frank Li) - Apply struct dw_pcie.parent_bus_offset in ATU users to remove use of .cpu_addr_fixup() when programming ATU (Frank Li) TI J721E PCIe driver: - Correct the 'link down' interrupt bit for J784S4 (Siddharth Vadapalli) TI Keystone PCIe controller driver: - Describe AM65x BARs 2 and 5 as Resizable (not Fixed) and reduce alignment requirement from 1MB to 64KB (Niklas Cassel) Xilinx Versal CPM PCIe controller driver: - Free IRQ domain in probe error path to avoid leaking it (Thippeswamy Havalige) - Add DT .compatible "xlnx,versal-cpm5nc-host" and driver support for Versal Net CPM5NC Root Port controller (Thippeswamy Havalige) - Add driver support for CPM5_HOST1 (Thippeswamy Havalige) Miscellaneous: - Convert fsl,mpc83xx-pcie binding to YAML (J. Neuschäfer) - Use for_each_available_child_of_node_scoped() to simplify apple, kirin, mediatek, mt7621, tegra drivers (Zhang Zekun)"* tag 'pci-v6.15-changes' of git://git.kernel.org/pub/scm/linux/kernel/git/pci/pci: (197 commits) PCI: layerscape: Fix arg_count to syscon_regmap_lookup_by_phandle_args() PCI: j721e: Fix the value of .linkdown_irq_regfield for J784S4 misc: pci_endpoint_test: Add support for PCITEST_IRQ_TYPE_AUTO PCI: endpoint: pci-epf-test: Expose supported IRQ types in CAPS register PCI: dw-rockchip: Endpoint mode cannot raise INTx interrupts PCI: endpoint: Add intx_capable to epc_features struct dt-bindings: PCI: Add common schema for devices accessible through PCI BARs PCI: intel-gw: Remove intel_pcie_cpu_addr() PCI: imx6: Remove imx_pcie_cpu_addr_fixup() PCI: dwc: Use parent_bus_offset to remove need for .cpu_addr_fixup() PCI: dwc: ep: Ensure proper iteration over outbound map windows PCI: dwc: ep: Use devicetree 'reg[addr_space]' to derive CPU -> ATU addr offset PCI: dwc: ep: Consolidate devicetree handling in dw_pcie_ep_get_resources() PCI: dwc: ep: Call epc_create() early in dw_pcie_ep_init() PCI: dwc: Use devicetree 'reg[config]' to derive CPU -> ATU addr offset PCI: dwc: Add dw_pcie_parent_bus_offset() checking and debug PCI: dwc: Add dw_pcie_parent_bus_offset() PCI/bwctrl: Fix NULL pointer dereference on bus number exhaustion PCI: xilinx-cpm: Add cpm_csr register mapping for CPM5_HOST1 variant PCI: brcmstb: Make const read-only arrays static ... List of files: /linux/drivers/pci/Kconfig

6fc6ded50ffc09a5cb3a9ec22dd1976401ea0bbc - PCI/DOE: Allow enabling DOE without CXL

Thu, 06 Mar 2025 08:52:11 +0100

PCI/DOE: Allow enabling DOE without CXLPCIe devices (not CXL) can support DOE as well, so allow DOE to be enabledeven if CXL isn't.Link: https://lore.kernel.org/r/20250306075211.1855177-4-alistair@alistair23.meSigned-off-by: Alistair Francis Signed-off-by: Bjorn Helgaas Reviewed-by: Jonathan Cameron List of files: /linux/drivers/pci/Kconfig

7ffb791423c7c518269a9aad35039ef824a40adb - x86/kaslr: Reduce KASLR entropy on most x86 systems

Fri, 07 Feb 2025 00:42:34 +0100

x86/kaslr: Reduce KASLR entropy on most x86 systemsWhen CONFIG_PCI_P2PDMA=y (which is basically enabled on alllarge x86 distros), it maps the PFN's via a ZONE_DEVICEmapping using devm_memremap_pages(). The mapped virtualaddress range corresponds to the pci_resource_start()of the BAR address and size corresponding to the BAR length.When KASLR is enabled, the direct map range of the kernel isreduced to the size of physical memory plus additional padding.If the BAR address is beyond this limit, PCI peer to peer DMAmappings fail.Fix this by not shrinking the size of the direct map whenCONFIG_PCI_P2PDMA=y.This reduces the total available entropy, but it's better thanthe current work around of having to disable KASLR completely.[ mingo: Clarified the changelog to point out the broad impact ... ]Signed-off-by: Balbir Singh Signed-off-by: Ingo Molnar Reviewed-by: Kees Cook Acked-by: Bjorn Helgaas # drivers/pci/KconfigCc: Linus Torvalds Cc: Peter Zijlstra Cc: Andy Lutomirski Link: https://lore.kernel.org/lkml/20250206023201.1481957-1-balbirs@nvidia.com/Link: https://lore.kernel.org/r/20250206234234.1912585-1-balbirs@nvidia.com-- arch/x86/mm/kaslr.c | 10 ++++++++-- drivers/pci/Kconfig | 6 ++++++ 2 files changed, 14 insertions(+), 2 deletions(-) List of files: /linux/drivers/pci/Kconfig

ab02bafcecedcd936d9e8526bcf1542642ad2947 - Merge branch 'pci/tph'

Mon, 25 Nov 2024 20:40:55 +0100

Merge branch 'pci/tph'- Add and document TLP Processing Hints (TPH) support so drivers can enable and disable TPH and the kernel can save/restore TPH configuration (Wei Huang)- Add TPH Steering Tag support so drivers can retrieve Steering Tag values associated with specific CPUs via an ACPI _DSM to direct DMA writes closer to their consumers (Wei Huang)* pci/tph: PCI/TPH: Add TPH documentation PCI/TPH: Add Steering Tag support PCI: Add TLP Processing Hints (TPH) support List of files: /linux/drivers/pci/Kconfig

b88cbaaa6fa109c2eb455d8fe2a318de0d197ea2 - PCI/pwrctrl: Rename pwrctl files to pwrctrl

Fri, 15 Nov 2024 22:44:27 +0100

PCI/pwrctrl: Rename pwrctl files to pwrctrlTo slightly reduce confusion between "pwrctl" (the power controller andpower sequencing framework) and "bwctrl" (the bandwidth controller),rename "pwrctl" to "pwrctrl" so they use the same "ctrl" suffix.Rename drivers/pci/pwrctl/ to drivers/pci/pwrctrl/, including the relatedMAINTAINERS, include file (include/linux/pci-pwrctl.h), Makefile, andKconfig changes.This is the minimal rename of files only. A subsequent commit will renamefunctions and data structures.Link: https://lore.kernel.org/r/20241115214428.2061153-2-helgaas@kernel.orgSigned-off-by: Bjorn Helgaas Signed-off-by: Krzysztof Wilczyński Acked-by: Krzysztof Wilczyński List of files: /linux/drivers/pci/Kconfig

f69767a1ada3ac74be2e1ac0795a05e1d1384eff - PCI: Add TLP Processing Hints (TPH) support

Wed, 02 Oct 2024 18:59:50 +0200

PCI: Add TLP Processing Hints (TPH) supportAdd support for PCIe TLP Processing Hints (TPH) support (see PCIe r6.2,sec 6.17).Add TPH register definitions in pci_regs.h, including the TPH Requestercapability register, TPH Requester control register, TPH Completercapability, and the ST fields of MSI-X entry.Introduce pcie_enable_tph() and pcie_disable_tph(), enabling drivers totoggle TPH support and configure specific ST mode as needed. Also add a newkernel parameter, "pci=notph", allowing users to disable TPH support acrossthe entire system.Link: https://lore.kernel.org/r/20241002165954.128085-2-wei.huang2@amd.comCo-developed-by: Jing Liu Co-developed-by: Paul Luse Co-developed-by: Eric Van Tassell Signed-off-by: Jing Liu Signed-off-by: Paul Luse Signed-off-by: Eric Van Tassell Signed-off-by: Wei Huang Signed-off-by: Bjorn Helgaas Reviewed-by: Ajit Khaparde Reviewed-by: Somnath Kotur Reviewed-by: Andy Gospodarek Reviewed-by: Jonathan Cameron Reviewed-by: Lukas Wunner List of files: /linux/drivers/pci/Kconfig

4e893545ef8712d25f3176790ebb95beb073637e - PCI/NPEM: Add Native PCIe Enclosure Management support

Wed, 04 Sep 2024 12:48:47 +0200

PCI/NPEM: Add Native PCIe Enclosure Management supportNative PCIe Enclosure Management (NPEM, PCIe r6.1 sec 6.28) allows managingLEDs in storage enclosures. NPEM is indication oriented and it does notgive direct access to LEDs. Although each indication *could* represent anindividual LED, multiple indications could also be represented as a single,multi-color LED or a single LED blinking in a specific interval. Thespecification leaves that open.Each enabled indication (capability register bit on) is represented as aledclass_dev which can be controlled through sysfs. For every ledclassdevice only 2 brightness states are allowed: LED_ON (1) or LED_OFF (0).This corresponds to the NPEM control register (Indication bit on/off).Ledclass devices appear in sysfs as child devices (subdirectory) of PCIdevice which has an NPEM Extended Capability and indication is enabled inNPEM capability register. For example, these are LEDs created for pcieport"10000:02:05.0" on my setup: leds/ ├── 10000:02:05.0:enclosure:fail ├── 10000:02:05.0:enclosure:locate ├── 10000:02:05.0:enclosure:ok └── 10000:02:05.0:enclosure:rebuildThey can be also found in "/sys/class/leds" directory. The parent PCIedevice domain/bus/device/function address is used to guarantee uniquenessacross leds subsystem.To enable/disable a "fail" indication, the "brightness" file can be edited: echo 1 > ./leds/10000:02:05.0:enclosure:fail/brightness echo 0 > ./leds/10000:02:05.0:enclosure:fail/brightnessPCIe r6.1, sec 7.9.19.2 defines the possible indications.Multiple indications for same parent PCIe device can conflict and hardwaremay update them when processing new request. To avoid issues, driverrefresh all indications by reading back control register.This driver expects to be the exclusive NPEM extended capability manager.It waits up to 1 second after imposing new request, it doesn't verify ifcontroller is busy before write, and it assumes the mutex lock givesprotection from concurrent updates.If _DSM LED management is available, we assume the platform may be usingNPEM for its own purposes (see PCI Firmware Spec r3.3 sec 4.7), so thedriver does not use NPEM. A future patch will add _DSM support; an infomessage notes whether NPEM or _DSM is being used.NPEM is a PCIe extended capability so it should be registered inpcie_init_capabilities() but it is not possible due to LED dependency. Theparent pci_device must be added earlier for led_classdev_register() to besuccessful. NPEM does not require configuration on kernel side, so it issafe to register LED devices later.Link: https://lore.kernel.org/r/20240904104848.23480-3-mariusz.tkaczyk@linux.intel.comSuggested-by: Lukas Wunner Signed-off-by: Mariusz Tkaczyk Signed-off-by: Bjorn Helgaas Tested-by: Stuart Hayes Reviewed-by: Christoph Hellwig Reviewed-by: Ilpo Järvinen List of files: /linux/drivers/pci/Kconfig

4565d2652a37e438e4cd729e2a8dfeffe34c958c - PCI/pwrctl: Add PCI power control core code

Wed, 12 Jun 2024 10:20:17 +0200

PCI/pwrctl: Add PCI power control core codeSome PCI devices must be powered-on before they can be detected on thebus. Introduce a simple framework reusing the existing PCI OFinfrastructure.The way this works is: a DT node representing a PCI device connected tothe port can be matched against its power control platform driver. Ifthe match succeeds, the driver is responsible for powering-up the deviceand calling pci_pwrctl_device_set_ready() which will trigger a PCI busrescan as well as subscribe to PCI bus notifications.When the device is detected and created, we'll make it consume the sameDT node that the platform device did. When the device is bound, we'llcreate a device link between it and the parent power control device.Tested-by: Amit Pundir Tested-by: Neil Armstrong # on SM8550-QRD, SM8650-QRD & SM8650-HDKTested-by: Caleb Connolly # OnePlus 8TAcked-by: Bjorn Helgaas Link: https://lore.kernel.org/r/20240612082019.19161-5-brgl@bgdev.plSigned-off-by: Bartosz Golaszewski List of files: /linux/drivers/pci/Kconfig

ae874027524c537a15e8d6f14ff69b855bc13ca8 - PCI: Move pci_iomap.c to drivers/pci/

Wed, 31 Jan 2024 10:00:21 +0100

PCI: Move pci_iomap.c to drivers/pci/The entirety of pci_iomap.c is guarded by an #ifdef CONFIG_PCI. It,consequently, does not belong to lib/ because it is not genericinfrastructure.Move pci_iomap.c to drivers/pci/ and implement the necessary changes toMakefiles and Kconfigs.Update MAINTAINERS file.Update Documentation.Link: https://lore.kernel.org/r/20240131090023.12331-3-pstanner@redhat.com[bhelgaas: squash in https://lore.kernel.org/r/20240212150934.24559-1-pstanner@redhat.com]Suggested-by: Danilo Krummrich Signed-off-by: Philipp Stanner Signed-off-by: Bjorn Helgaas Reviewed-by: Arnd Bergmann List of files: /linux/drivers/pci/Kconfig

43b0294abaceec20943c4ae222a0839b353a055f - PCI: Replace unnecessary UTF-8 in Kconfig

Wed, 20 Jul 2022 09:22:03 +0200

PCI: Replace unnecessary UTF-8 in KconfigThe CONFIG_PCI_P2PDMA Kconfig help text contains a Cyrillic small "Dze"(ѕ). When menuconfig renders it, it looks like "Enable ~U drivers" insteadof "Enables drivers".Replace it by a plain "s" so the help text is displayed correctly bymenuconfig.Uwe Kleine-König later posted the samepatch athttps://lore.kernel.org/r/20231006150209.87666-1-u.kleine-koenig@pengutronix.deLink: https://lore.kernel.org/r/1658301723-111283-1-git-send-email-liusong@linux.alibaba.comTested-by: Randy Dunlap Signed-off-by: Liu Song [bhelgaas: commit log, add Uwe's report]Signed-off-by: Bjorn Helgaas Acked-by: Randy Dunlap List of files: /linux/drivers/pci/Kconfig

26641b3f22abe3f03bd8e078c116cc98de740f43 - PCI: Fix CONFIG_PCI_DYNAMIC_OF_NODES kconfig dependencies

Thu, 31 Aug 2023 20:19:07 +0200

PCI: Fix CONFIG_PCI_DYNAMIC_OF_NODES kconfig dependenciesGenerating interrupt-map property depends on of_irq_parse_raw() whichis enabled by CONFIG_OF_IRQ. Change CONFIG_PCI_DYNAMIC_OF_NODESdependency from CONFIG_OF to CONFIG_OF_IRQ.Closes: https://lore.kernel.org/linux-devicetree/2187619d-55bc-41bb-bbb4-6059399db997@roeck-us.net/Fixes: 407d1a51921e ("PCI: Create device tree node for bridge")Link: https://lore.kernel.org/r/1693505947-29786-1-git-send-email-lizhi.hou@amd.comReported-by: Guenter Roeck Signed-off-by: Lizhi Hou Signed-off-by: Bjorn Helgaas List of files: /linux/drivers/pci/Kconfig