<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Makefile</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>b88cbaaa - PCI/pwrctrl: Rename pwrctl files to pwrctrl</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/pci/Makefile#b88cbaaa</link>
        <description>PCI/pwrctrl: Rename pwrctl files to pwrctrlTo slightly reduce confusion between &quot;pwrctl&quot; (the power controller andpower sequencing framework) and &quot;bwctrl&quot; (the bandwidth controller),rename &quot;pwrctl&quot; to &quot;pwrctrl&quot; so they use the same &quot;ctrl&quot; 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 &lt;bhelgaas@google.com&gt;Signed-off-by: Krzysztof Wilczy&#324;ski &lt;kwilczynski@kernel.org&gt;Acked-by: Krzysztof Wilczy&#324;ski &lt;kw@linux.com&gt;

            List of files:
            /linux-6.15/drivers/pci/Makefile</description>
        <pubDate>Fri, 15 Nov 2024 21:44:27 +0000</pubDate>
        <dc:creator>Bjorn Helgaas &lt;bhelgaas@google.com&gt;</dc:creator>
    </item>
<item>
        <title>f69767a1 - PCI: Add TLP Processing Hints (TPH) support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/pci/Makefile#f69767a1</link>
        <description>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, &quot;pci=notph&quot;, 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 &lt;jing2.liu@intel.com&gt;Co-developed-by: Paul Luse &lt;paul.e.luse@linux.intel.com&gt;Co-developed-by: Eric Van Tassell &lt;Eric.VanTassell@amd.com&gt;Signed-off-by: Jing Liu &lt;jing2.liu@intel.com&gt;Signed-off-by: Paul Luse &lt;paul.e.luse@linux.intel.com&gt;Signed-off-by: Eric Van Tassell &lt;Eric.VanTassell@amd.com&gt;Signed-off-by: Wei Huang &lt;wei.huang2@amd.com&gt;Signed-off-by: Bjorn Helgaas &lt;bhelgaas@google.com&gt;Reviewed-by: Ajit Khaparde &lt;ajit.khaparde@broadcom.com&gt;Reviewed-by: Somnath Kotur &lt;somnath.kotur@broadcom.com&gt;Reviewed-by: Andy Gospodarek &lt;andrew.gospodarek@broadcom.com&gt;Reviewed-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;Reviewed-by: Lukas Wunner &lt;lukas@wunner.de&gt;

            List of files:
            /linux-6.15/drivers/pci/Makefile</description>
        <pubDate>Wed, 02 Oct 2024 16:59:50 +0000</pubDate>
        <dc:creator>Wei Huang &lt;wei.huang2@amd.com&gt;</dc:creator>
    </item>
<item>
        <title>4e893545 - PCI/NPEM: Add Native PCIe Enclosure Management support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/pci/Makefile#4e893545</link>
        <description>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&quot;10000:02:05.0&quot; on my setup:  leds/  &#9500;&#9472;&#9472; 10000:02:05.0:enclosure:fail  &#9500;&#9472;&#9472; 10000:02:05.0:enclosure:locate  &#9500;&#9472;&#9472; 10000:02:05.0:enclosure:ok  &#9492;&#9472;&#9472; 10000:02:05.0:enclosure:rebuildThey can be also found in &quot;/sys/class/leds&quot; directory. The parent PCIedevice domain/bus/device/function address is used to guarantee uniquenessacross leds subsystem.To enable/disable a &quot;fail&quot; indication, the &quot;brightness&quot; file can be edited:  echo 1 &gt; ./leds/10000:02:05.0:enclosure:fail/brightness  echo 0 &gt; ./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&apos;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 &lt;lukas@wunner.de&gt;Signed-off-by: Mariusz Tkaczyk &lt;mariusz.tkaczyk@linux.intel.com&gt;Signed-off-by: Bjorn Helgaas &lt;bhelgaas@google.com&gt;Tested-by: Stuart Hayes &lt;stuart.w.hayes@gmail.com&gt;Reviewed-by: Christoph Hellwig &lt;hch@lst.de&gt;Reviewed-by: Ilpo J&#228;rvinen &lt;ilpo.jarvinen@linux.intel.com&gt;

            List of files:
            /linux-6.15/drivers/pci/Makefile</description>
        <pubDate>Wed, 04 Sep 2024 10:48:47 +0000</pubDate>
        <dc:creator>Mariusz Tkaczyk &lt;mariusz.tkaczyk@linux.intel.com&gt;</dc:creator>
    </item>
<item>
        <title>4565d265 - PCI/pwrctl: Add PCI power control core code</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/pci/Makefile#4565d265</link>
        <description>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&apos;ll make it consume the sameDT node that the platform device did. When the device is bound, we&apos;llcreate a device link between it and the parent power control device.Tested-by: Amit Pundir &lt;amit.pundir@linaro.org&gt;Tested-by: Neil Armstrong &lt;neil.armstrong@linaro.org&gt; # on SM8550-QRD, SM8650-QRD &amp; SM8650-HDKTested-by: Caleb Connolly &lt;caleb.connolly@linaro.org&gt; # OnePlus 8TAcked-by: Bjorn Helgaas &lt;bhelgaas@google.com&gt;Link: https://lore.kernel.org/r/20240612082019.19161-5-brgl@bgdev.plSigned-off-by: Bartosz Golaszewski &lt;bartosz.golaszewski@linaro.org&gt;

            List of files:
            /linux-6.15/drivers/pci/Makefile</description>
        <pubDate>Wed, 12 Jun 2024 08:20:17 +0000</pubDate>
        <dc:creator>Bartosz Golaszewski &lt;bartosz.golaszewski@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>be9c3a4c - PCI/sysfs: Compile pci-sysfs.c only if CONFIG_SYSFS=y</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/pci/Makefile#be9c3a4c</link>
        <description>PCI/sysfs: Compile pci-sysfs.c only if CONFIG_SYSFS=yIt is possible to enable CONFIG_PCI but disable CONFIG_SYSFS and forspace-constrained devices such as routers, such a configuration mayactually make sense.However pci-sysfs.c is compiled even if CONFIG_SYSFS is disabled,unnecessarily increasing the kernel&apos;s size.To rectify that:* Move pci_mmap_fits() to mmap.c.  It is not only needed by  pci-sysfs.c, but also proc.c.* Move pci_dev_type to probe.c and make it private.  It references  pci_dev_attr_groups in pci-sysfs.c.  Make that public instead for  consistency with pci_dev_groups, pcibus_groups and pci_bus_groups,  which are likewise public and referenced by struct definitions in  pci-driver.c and probe.c.* Define pci_dev_groups, pci_dev_attr_groups, pcibus_groups and  pci_bus_groups to NULL if CONFIG_SYSFS is disabled.  Provide empty  static inlines for pci_{create,remove}_legacy_files() and  pci_{create,remove}_sysfs_dev_files().Result:vmlinux size is reduced by 122996 bytes in my arm 32-bit test build.Link: https://lore.kernel.org/r/85ca95ae8e4d57ccf082c5c069b8b21eb141846e.1698668982.git.lukas@wunner.deSigned-off-by: Lukas Wunner &lt;lukas@wunner.de&gt;Signed-off-by: Bjorn Helgaas &lt;bhelgaas@google.com&gt;Reviewed-by: Alistair Francis &lt;alistair.francis@wdc.com&gt;

            List of files:
            /linux-6.15/drivers/pci/Makefile</description>
        <pubDate>Mon, 30 Oct 2023 12:32:12 +0000</pubDate>
        <dc:creator>Lukas Wunner &lt;lukas@wunner.de&gt;</dc:creator>
    </item>
<item>
        <title>acc2364f - PCI: Move PCI-specific devres code to drivers/pci/</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/pci/Makefile#acc2364f</link>
        <description>PCI: Move PCI-specific devres code to drivers/pci/The pcim_*() functions in lib/devres.c are guarded by an #ifdef CONFIG_PCIand, thus, don&apos;t belong to this file. They are only ever used for PCI andare not generic infrastructure.Move all pcim_*() functions in lib/devres.c to drivers/pci/devres.c.Adjust the Makefile.Add drivers/pci/devres.c to Documentation.Link: https://lore.kernel.org/r/20240131090023.12331-4-pstanner@redhat.comSuggested-by: Danilo Krummrich &lt;dakr@redhat.com&gt;Signed-off-by: Philipp Stanner &lt;pstanner@redhat.com&gt;Signed-off-by: Bjorn Helgaas &lt;bhelgaas@google.com&gt;

            List of files:
            /linux-6.15/drivers/pci/Makefile</description>
        <pubDate>Wed, 31 Jan 2024 09:00:22 +0000</pubDate>
        <dc:creator>Philipp Stanner &lt;pstanner@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>ae874027 - PCI: Move pci_iomap.c to drivers/pci/</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/pci/Makefile#ae874027</link>
        <description>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 &lt;dakr@redhat.com&gt;Signed-off-by: Philipp Stanner &lt;pstanner@redhat.com&gt;Signed-off-by: Bjorn Helgaas &lt;bhelgaas@google.com&gt;Reviewed-by: Arnd Bergmann &lt;arnd@arndb.de&gt;

            List of files:
            /linux-6.15/drivers/pci/Makefile</description>
        <pubDate>Wed, 31 Jan 2024 09:00:21 +0000</pubDate>
        <dc:creator>Philipp Stanner &lt;pstanner@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>1e8cc8e6 - PCI: Place interrupt related code into irq.c</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/pci/Makefile#1e8cc8e6</link>
        <description>PCI: Place interrupt related code into irq.cInterrupt related code is spread into irq.c, pci.c, and setup-irq.c.Group them into pre-existing irq.c.Link: https://lore.kernel.org/r/20240129113655.3368-1-ilpo.jarvinen@linux.intel.comSigned-off-by: Ilpo J&#228;rvinen &lt;ilpo.jarvinen@linux.intel.com&gt;Signed-off-by: Bjorn Helgaas &lt;bhelgaas@google.com&gt;

            List of files:
            /linux-6.15/drivers/pci/Makefile</description>
        <pubDate>Mon, 29 Jan 2024 11:36:54 +0000</pubDate>
        <dc:creator>Ilpo J&#228;rvinen &lt;ilpo.jarvinen@linux.intel.com&gt;</dc:creator>
    </item>
<item>
        <title>407d1a51 - PCI: Create device tree node for bridge</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/pci/Makefile#407d1a51</link>
        <description>PCI: Create device tree node for bridgeThe PCI endpoint device such as Xilinx Alveo PCI card maps the registerspaces from multiple hardware peripherals to its PCI BAR. Normally,the PCI core discovers devices and BARs using the PCI enumeration process.There is no infrastructure to discover the hardware peripherals that arepresent in a PCI device, and which can be accessed through the PCI BARs.Apparently, the device tree framework requires a device tree node for thePCI device. Thus, it can generate the device tree nodes for hardwareperipherals underneath. Because PCI is self discoverable bus, there mightnot be a device tree node created for PCI devices. Furthermore, if the PCIdevice is hot pluggable, when it is plugged in, the device tree nodes forits parent bridges are required. Add support to generate device tree nodefor PCI bridges.Add an of_pci_make_dev_node() interface that can be used to create devicetree node for PCI devices.Add a PCI_DYNAMIC_OF_NODES config option. When the option is turned on,the kernel will generate device tree nodes for PCI bridges unconditionally.Initially, add the basic properties for the dynamically generated devicetree nodes which include #address-cells, #size-cells, device_type,compatible, ranges, reg.Acked-by: Bjorn Helgaas &lt;bhelgaas@google.com&gt;Signed-off-by: Lizhi Hou &lt;lizhi.hou@amd.com&gt;Link: https://lore.kernel.org/r/1692120000-46900-3-git-send-email-lizhi.hou@amd.comSigned-off-by: Rob Herring &lt;robh@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/pci/Makefile</description>
        <pubDate>Tue, 15 Aug 2023 17:19:57 +0000</pubDate>
        <dc:creator>Lizhi Hou &lt;lizhi.hou@amd.com&gt;</dc:creator>
    </item>
<item>
        <title>9d24322e - PCI/DOE: Add DOE mailbox support functions</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/pci/Makefile#9d24322e</link>
        <description>PCI/DOE: Add DOE mailbox support functionsIntroduced in a PCIe r6.0, sec 6.30, DOE provides a config space basedmailbox with standard protocol discovery.  Each mailbox is accessedthrough a DOE Extended Capability.Each DOE mailbox must support the DOE discovery protocol in addition toany number of additional protocols.Define core PCIe functionality to manage a single PCIe DOE mailbox at adefined config space offset.  Functionality includes iterating,creating, query of supported protocol, and task submission.  Destructionof the mailboxes is device managed.Cc: &quot;Li, Ming&quot; &lt;ming4.li@intel.com&gt;Cc: Bjorn Helgaas &lt;helgaas@kernel.org&gt;Cc: Matthew Wilcox &lt;willy@infradead.org&gt;Acked-by: Bjorn Helgaas &lt;helgaas@kernel.org&gt;Signed-off-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;Co-developed-by: Ira Weiny &lt;ira.weiny@intel.com&gt;Signed-off-by: Ira Weiny &lt;ira.weiny@intel.com&gt;Link: https://lore.kernel.org/r/20220719205249.566684-4-ira.weiny@intel.comSigned-off-by: Dan Williams &lt;dan.j.williams@intel.com&gt;

            List of files:
            /linux-6.15/drivers/pci/Makefile</description>
        <pubDate>Tue, 19 Jul 2022 20:52:46 +0000</pubDate>
        <dc:creator>Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;</dc:creator>
    </item>
<item>
        <title>1d38fe6e - PCI/VGA: Move vgaarb to drivers/pci</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/pci/Makefile#1d38fe6e</link>
        <description>PCI/VGA: Move vgaarb to drivers/pciThe VGA arbiter is really PCI-specific and doesn&apos;t depend on any GPUthings.  Move it to the PCI subsystem.Note that misc_init() must be called before vga_arb_device_init().  Theseare both subsys_initcalls, so this ordering depends on the link order,which is determined by drivers/Makefile:  obj-y += pci/  obj-y += char/        &lt;-- misc_init()  obj-y += gpu/         &lt;-- vga_arb_device_init() (before this commit)The drivers/pci/ subsys_initcalls are called *before* misc_init(), soconvert vga_arb_device_init() to subsys_initcall_sync(), which is calledafter *all* subsys_initcalls.Link: https://lore.kernel.org/r/20220224224753.297579-2-helgaas@kernel.orgSigned-off-by: Bjorn Helgaas &lt;bhelgaas@google.com&gt;

            List of files:
            /linux-6.15/drivers/pci/Makefile</description>
        <pubDate>Thu, 24 Feb 2022 22:47:43 +0000</pubDate>
        <dc:creator>Bjorn Helgaas &lt;bhelgaas@google.com&gt;</dc:creator>
    </item>
<item>
        <title>288c81ce - PCI/MSI: Move code into a separate directory</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/pci/Makefile#288c81ce</link>
        <description>PCI/MSI: Move code into a separate directorymsi.c is getting larger and really could do with a splitup. Move it intoits own directory to prepare for that.Signed-off-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;Tested-by: Juergen Gross &lt;jgross@suse.com&gt;Reviewed-by: Jason Gunthorpe &lt;jgg@nvidia.com&gt;Acked-by: Bjorn Helgaas &lt;bhelgaas@google.com&gt;Link: https://lore.kernel.org/r/20211206210224.655043033@linutronix.de

            List of files:
            /linux-6.15/drivers/pci/Makefile</description>
        <pubDate>Mon, 06 Dec 2021 22:27:47 +0000</pubDate>
        <dc:creator>Thomas Gleixner &lt;tglx@linutronix.de&gt;</dc:creator>
    </item>
<item>
        <title>e8e9aaba - PCI: Apply CONFIG_PCI_DEBUG to entire drivers/pci hierarchy</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/pci/Makefile#e8e9aaba</link>
        <description>PCI: Apply CONFIG_PCI_DEBUG to entire drivers/pci hierarchyCONFIG_PCI_DEBUG=y adds -DDEBUG to CFLAGS, which enables things likepr_debug() and dev_dbg() (and hence pci_dbg()).  Previously we added-DDEBUG for files in drivers/pci/, but not files in subdirectories ofdrivers/pci/.Add -DDEBUG to CFLAGS for all files below drivers/pci/ so CONFIG_PCI_DEBUGapplies to the entire hierarchy.[bhelgaas: commit log]Link: https://lore.kernel.org/r/1612438215-33105-1-git-send-email-yangyicong@hisilicon.comSigned-off-by: Junhao He &lt;hejunhao2@hisilicon.com&gt;Signed-off-by: Yicong Yang &lt;yangyicong@hisilicon.com&gt;Signed-off-by: Bjorn Helgaas &lt;bhelgaas@google.com&gt;Reviewed-by: Krzysztof Wilczy&#324;ski &lt;kw@linux.com&gt;

            List of files:
            /linux-6.15/drivers/pci/Makefile</description>
        <pubDate>Thu, 04 Feb 2021 11:30:15 +0000</pubDate>
        <dc:creator>Junhao He &lt;hejunhao2@hisilicon.com&gt;</dc:creator>
    </item>
<item>
        <title>cbc40d5c - PCI/MSI: Move MSI/MSI-X init to msi.c</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/pci/Makefile#cbc40d5c</link>
        <description>PCI/MSI: Move MSI/MSI-X init to msi.cMove pci_msi_setup_pci_dev(), which disables MSI and MSI-X interrupts, fromprobe.c to msi.c so it&apos;s with all the other MSI code and more consistentwith other capability initialization.  This means we must compile msi.calways, even without CONFIG_PCI_MSI, so wrap the rest of msi.c in an #ifdefand adjust the Makefile accordingly.  No functional change intended.Link: https://lore.kernel.org/r/20201203185110.1583077-2-helgaas@kernel.orgSigned-off-by: Bjorn Helgaas &lt;bhelgaas@google.com&gt;Reviewed-by: Thierry Reding &lt;treding@nvidia.com&gt;

            List of files:
            /linux-6.15/drivers/pci/Makefile</description>
        <pubDate>Thu, 03 Dec 2020 18:51:08 +0000</pubDate>
        <dc:creator>Bjorn Helgaas &lt;bhelgaas@google.com&gt;</dc:creator>
    </item>
<item>
        <title>b7da3d4d - PCI: Allow building PCIe things without PCIEPORTBUS</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/pci/Makefile#b7da3d4d</link>
        <description>PCI: Allow building PCIe things without PCIEPORTBUSSome things in drivers/pci/pcie (aspm.c and ptm.c) do not depend on thePCIe portdrv, so we should be able to build them even if PCIEPORTBUS is notselected.  Remove the PCIEPORTBUS guard from building pcie/.Link: https://lore.kernel.org/r/20191106222420.10216-6-helgaas@kernel.orgSigned-off-by: Bjorn Helgaas &lt;bhelgaas@google.com&gt;Reviewed-by: Andrew Murray &lt;andrew.murray@arm.com&gt;

            List of files:
            /linux-6.15/drivers/pci/Makefile</description>
        <pubDate>Wed, 06 Nov 2019 22:13:43 +0000</pubDate>
        <dc:creator>Bjorn Helgaas &lt;bhelgaas@google.com&gt;</dc:creator>
    </item>
<item>
        <title>40e5d614 - PCI: OF: Allow of_pci_get_max_link_speed() to be used by PCI Endpoint drivers</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/pci/Makefile#40e5d614</link>
        <description>PCI: OF: Allow of_pci_get_max_link_speed() to be used by PCI Endpoint driversof_pci_get_max_link_speed() is built only if CONFIG_PCI is enabled.Make of_pci_get_max_link_speed() to be also used by PCI Endpointcontrollers with just CONFIG_PCI_ENDPOINT enabled.Signed-off-by: Kishon Vijay Abraham I &lt;kishon@ti.com&gt;Signed-off-by: Sekhar Nori &lt;nsekhar@ti.com&gt;Signed-off-by: Lorenzo Pieralisi &lt;lorenzo.pieralisi@arm.com&gt;Acked-by: Bjorn Helgaas &lt;bhelgaas@google.com&gt;

            List of files:
            /linux-6.15/drivers/pci/Makefile</description>
        <pubDate>Mon, 25 Mar 2019 09:39:37 +0000</pubDate>
        <dc:creator>Kishon Vijay Abraham I &lt;kishon@ti.com&gt;</dc:creator>
    </item>
<item>
        <title>5d32a665 - PCI/ACPI: Allow ACPI to be built without CONFIG_PCI set</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/pci/Makefile#5d32a665</link>
        <description>PCI/ACPI: Allow ACPI to be built without CONFIG_PCI setWe are compiling PCI code today for systems with ACPI and no PCIdevice present. Remove the useless code and reduce the tightdependency.Signed-off-by: Sinan Kaya &lt;okaya@kernel.org&gt;Acked-by: Bjorn Helgaas &lt;bhelgaas@google.com&gt; # PCI partsAcked-by: Ingo Molnar &lt;mingo@kernel.org&gt;Signed-off-by: Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;

            List of files:
            /linux-6.15/drivers/pci/Makefile</description>
        <pubDate>Wed, 19 Dec 2018 22:46:56 +0000</pubDate>
        <dc:creator>Sinan Kaya &lt;okaya@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>23a5fba4 - PCI: Introduce PCI bridge emulated config space common logic</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/pci/Makefile#23a5fba4</link>
        <description>PCI: Introduce PCI bridge emulated config space common logicSome PCI host controllers do not expose a configuration space for theroot port PCI bridge. Due to this, the Marvell Armada 370/38x/XP PCIcontroller driver (pci-mvebu) emulates a root port PCI bridgeconfiguration space, and uses that to (among other things) dynamicallycreate the memory windows that correspond to the PCI MEM and I/Oregions.Since we now need to add a very similar logic for the Marvell Armada37xx PCI controller driver (pci-aardvark), instead of duplicating thecode, we create in this commit a common logic called pci-bridge-emul.The idea of this logic is to emulate a root port PCI bridgeconfiguration space by providing configuration space read/writeoperations, and faking behind the scenes the configuration space of aPCI bridge. A PCI host controller driver simply has to callpci_bridge_emul_conf_read() and pci_bridge_emul_conf_write() toread/write the configuration space of the bridge.By default, the PCI bridge configuration space is simply emulated by achunk of memory, but the PCI host controller can override the behaviorof the read and write operations on a per-register basis to doadditional actions if needed. We take care of complying with thebehavior of the PCI configuration space registers in terms of bitsthat are read-write, read-only, reserved and write-1-to-clear.Signed-off-by: Thomas Petazzoni &lt;thomas.petazzoni@bootlin.com&gt;Signed-off-by: Lorenzo Pieralisi &lt;lorenzo.pieralisi@arm.com&gt;Acked-by: Bjorn Helgaas &lt;bhelgaas@google.com&gt;Reviewed-by: Russell King &lt;rmk+kernel@armlinux.org.uk&gt;

            List of files:
            /linux-6.15/drivers/pci/Makefile</description>
        <pubDate>Thu, 18 Oct 2018 15:37:16 +0000</pubDate>
        <dc:creator>Thomas Petazzoni &lt;thomas.petazzoni@bootlin.com&gt;</dc:creator>
    </item>
<item>
        <title>52916982 - PCI/P2PDMA: Support peer-to-peer memory</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/pci/Makefile#52916982</link>
        <description>PCI/P2PDMA: Support peer-to-peer memorySome PCI devices may have memory mapped in a BAR space that&apos;s intended foruse in peer-to-peer transactions.  To enable such transactions the memorymust be registered with ZONE_DEVICE pages so it can be used by DMAinterfaces in existing drivers.Add an interface for other subsystems to find and allocate chunks of P2Pmemory as necessary to facilitate transfers between two PCI peers:  struct pci_dev *pci_p2pmem_find[_many]();  int pci_p2pdma_distance[_many]();  void *pci_alloc_p2pmem();The new interface requires a driver to collect a list of client devicesinvolved in the transaction then call pci_p2pmem_find() to obtain anysuitable P2P memory.  Alternatively, if the caller knows a device whichprovides P2P memory, they can use pci_p2pdma_distance() to determine if itis usable.  With a suitable p2pmem device, memory can then be allocatedwith pci_alloc_p2pmem() for use in DMA transactions.Depending on hardware, using peer-to-peer memory may reduce the bandwidthof the transfer but can significantly reduce pressure on system memory.This may be desirable in many cases: for example a system could be designedwith a small CPU connected to a PCIe switch by a small number of laneswhich would maximize the number of lanes available to connect to NVMedevices.The code is designed to only utilize the p2pmem device if all the devicesinvolved in a transfer are behind the same PCI bridge.  This is because wehave no way of knowing whether peer-to-peer routing between PCIe Root Portsis supported (PCIe r4.0, sec 1.3.1).  Additionally, the benefits of P2Ptransfers that go through the RC is limited to only reducing DRAM usageand, in some cases, coding convenience.  The PCI-SIG may be exploringadding a new capability bit to advertise whether this is possible forfuture hardware.This commit includes significant rework and feedback from ChristophHellwig.Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;Signed-off-by: Logan Gunthorpe &lt;logang@deltatee.com&gt;[bhelgaas: fold in fix from Keith Busch &lt;keith.busch@intel.com&gt;:https://lore.kernel.org/linux-pci/20181012155920.15418-1-keith.busch@intel.com,to address comment from Dan Carpenter &lt;dan.carpenter@oracle.com&gt;, fold inhttps://lore.kernel.org/linux-pci/20181017160510.17926-1-logang@deltatee.com]Signed-off-by: Bjorn Helgaas &lt;bhelgaas@google.com&gt;

            List of files:
            /linux-6.15/drivers/pci/Makefile</description>
        <pubDate>Thu, 04 Oct 2018 21:27:35 +0000</pubDate>
        <dc:creator>Logan Gunthorpe &lt;logang@deltatee.com&gt;</dc:creator>
    </item>
<item>
        <title>68bb22e9 - PCI: Initialize endpoint library before controllers</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/pci/Makefile#68bb22e9</link>
        <description>PCI: Initialize endpoint library before controllersThe endpoint library must be initialized before its users, which are indrivers/pci/controllers.  The endpoint initialization currently depends onlink order.This corrects a kernel crash when loading the Cadence EP driver, since itcalls devm_pci_epc_create() and this is only valid once the endpointlibrary has been initialized.Fixes: 6e0832fa432e (&quot;PCI: Collect all native drivers under drivers/pci/controller/&quot;)Signed-off-by: Alan Douglas &lt;adouglas@cadence.com&gt;Signed-off-by: Bjorn Helgaas &lt;bhelgaas@google.com&gt;

            List of files:
            /linux-6.15/drivers/pci/Makefile</description>
        <pubDate>Fri, 22 Jun 2018 16:17:17 +0000</pubDate>
        <dc:creator>Alan Douglas &lt;adouglas@cadence.com&gt;</dc:creator>
    </item>
</channel>
</rss>
