Changes in Makefile

e434e54d - PCI: hotplug: Add OCTEON PCI hotplug controller driver

Mon, 11 Nov 2024 13:45:11 +0000

PCI: hotplug: Add OCTEON PCI hotplug controller driverAdd a PCI hotplug controller driver for the OCTEON PCIe device. The OCTEONPCIe device is a multi-function device where function 0 serves as the PCIhotplug controller.There is an out-of-band management console interface to firmware running onfunction 0 whereby an administrator can disable functions to save power orenable them with one of several personalities (virtio-net, virtio-crypto,NVMe, etc) for the other functions. Function 0 initiates hotplug eventshandled by this driver when the other functions are enabled or disabled. +--------------------------------+ | Root Port | +--------------------------------+ | PCIe | +---------------------------------------------------------------+ | OCTEON PCIe Multifunction Device | +---------------------------------------------------------------+ | | | | | | | | +---------------------+ +----------------+ +-----+ +----------------+ | Function 0 | | Function 1 | | ... | | Function 7 | | (Hotplug controller)| | (Hotplug slot) | | | | (Hotplug slot) | +---------------------+ +----------------+ +-----+ +----------------+ | | +-------------------------+ | Controller Firmware | +-------------------------+The hotplug controller driver enables hotplugging of non-controllerfunctions within the same device. During probing, the driver removesthe non-controller functions and registers them as PCI hotplug slots.These slots are added back by the driver, only upon request from thedevice firmware.The controller uses MSI-X interrupts to notify the host of hotplugevents initiated by the OCTEON firmware. Additionally, the driverallows users to enable or disable individual functions via sysfs slotentries, as provided by the PCI hotplug framework.Link: https://lore.kernel.org/r/20241111134523.2796699-1-sthotton@marvell.comCo-developed-by: Vamsi Attunuru Signed-off-by: Vamsi Attunuru Signed-off-by: Shijith Thotton [bhelgaas: use pci_info() when possible]Signed-off-by: Bjorn Helgaas List of files: /linux-6.15/drivers/pci/hotplug/Makefile

820f59ed - PCI: hotplug: Add Ampere Altra Attention Indicator extension driver

Sat, 30 Sep 2023 00:20:36 +0000

PCI: hotplug: Add Ampere Altra Attention Indicator extension driverOn Ampere Altra, PCIe hotplug is handled through ACPI. A side interface isalso present to request system firmware control of the hotplug AttentionIndicators. Add an ACPI PCI Hotplug companion driver to support AttentionIndicator control.Link: https://lore.kernel.org/r/20230930002036.6491-2-scott@os.amperecomputing.comSigned-off-by: D Scott Phillips [bhelgaas: mask domain to low 4 bits]Signed-off-by: Bjorn Helgaas Acked-by: "Rafael J. Wysocki" List of files: /linux-6.15/drivers/pci/hotplug/Makefile

c7532b60 - PCI/hotplug: remove the sgi_hotplug driver

Tue, 13 Aug 2019 07:24:51 +0000

PCI/hotplug: remove the sgi_hotplug driverThe SGI SN2 support is about to be removed. Remove this driver thatdepends on the SN2 support.Signed-off-by: Christoph Hellwig Link: https://lkml.kernel.org/r/20190813072514.23299-6-hch@lst.deSigned-off-by: Tony Luck List of files: /linux-6.15/drivers/pci/hotplug/Makefile

b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license

Wed, 01 Nov 2017 14:07:57 +0000

License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the 'GPL-2.0'SPDX license identifier. The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode & Windriver) producing SPDXtag:value files created by Philippe Ombredanne. Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed. Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained >5 lines of source - File already had some variant of a license header in it (even if <5 lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn't find any license traces, file was considered to have no license information in it, and the top level COPYING file license applied. For non */uapi/* files that summary was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 11139 and resulted in the first patch in this series. If that file was a */uapi/* path one, it was "GPL-2.0 WITH Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 WITH Linux-syscall-note 930 and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one of the */uapi/* ones, it was denoted with the Linux-syscall-note if any GPL family license was found in the file or had no licensing in it (per prior point). Results summary: SPDX license identifier # files ---------------------------------------------------|------ GPL-2.0 WITH Linux-syscall-note 270 GPL-2.0+ WITH Linux-syscall-note 169 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17 LGPL-2.1+ WITH Linux-syscall-note 15 GPL-1.0+ WITH Linux-syscall-note 14 ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5 LGPL-2.0+ WITH Linux-syscall-note 4 LGPL-2.1 WITH Linux-syscall-note 3 ((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3 ((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1 and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became the concluded license(s). - when there was disagreement between the two scanners (one detected a license but the other didn't, or they both detected different licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file resulted in a clear resolution of the license that should apply (and which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier, the file was flagged for further research and to be revisited later in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights. TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected license ids and scores - reviewing anything where there was a license detected (about 500+ files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied SPDX license was correctThis produced a worksheet with 20 files needing minor correction. Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg. Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected. This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.) Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart Reviewed-by: Philippe Ombredanne Reviewed-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/pci/hotplug/Makefile

66725152 - PCI/hotplug: PowerPC PowerNV PCI hotplug driver

Fri, 20 May 2016 06:41:42 +0000

PCI/hotplug: PowerPC PowerNV PCI hotplug driverThis adds standalone driver to support PCI hotplug for PowerPC PowerNVplatform that runs on top of skiboot firmware. The firmware identifieshotpluggable slots and marked their device tree node with proper"ibm,slot-pluggable" and "ibm,reset-by-firmware". The driver scansdevice tree nodes to create/register PCI hotplug slot accordingly.The PCI slots are organized in fashion of tree, which means onePCI slot might have parent PCI slot and parent PCI slot possiblycontains multiple child PCI slots. At the plugging time, the parentPCI slot is populated before its children. The child PCI slots areremoved before their parent PCI slot can be removed from the system.If the skiboot firmware doesn't support slot status retrieval, the PCIslot device node shouldn't have property "ibm,reset-by-firmware". Inthat case, none of valid PCI slots will be detected from device tree.The skiboot firmware doesn't export the capability to access attentionLEDs yet and it's something for TBD.Signed-off-by: Gavin Shan Acked-by: Bjorn Helgaas Signed-off-by: Michael Ellerman List of files: /linux-6.15/drivers/pci/hotplug/Makefile

e705c295 - PCI: pciehp: Drop pointless ACPI-based "slot detection" check

Tue, 19 May 2015 13:27:58 +0000

PCI: pciehp: Drop pointless ACPI-based "slot detection" checkJarod Wilson reports that ExpressCard hotplug doesn't work on HP ZBook G2.The problem turns out to be the ACPI-based "slot detection" code calledfrom pciehp_probe() which uses questionable heuristics based on what ACPIobjects are present for the PCIe port device to figure out whether toregister a hotplug slot for that port.That code is used if there is at least one PCIe port having an ACPI deviceconfiguration object related to hotplug (such as _EJ0 or _RMV), and theThunderbolt port on the ZBook has _RMV. Of course, Thunderbolt and PCIenative hotplug need not be mutually exclusive (as they aren't on theZBook), so that rule is simply incorrect.Moreover, the ACPI-based "slot detection" check does not add any value ifpciehp_probe() is called at all and the service type of the device objectit has been called for is PCIE_PORT_SERVICE_HP, because PCIe hotplugservices are only registered if the _OSC handshake in acpi_pci_root_add()allows the kernel to control the PCIe native hotplug feature. No morechecks need to be carried out to decide whether or not to register a nativePCIe hotlug slot in that case.For the above reasons, make pciehp_probe() check if it has been called forthe right service type and drop the pointless ACPI-based "slot detection"check from it. Also remove the entire code whose only user is that check(the entire pciehp_acpi.c file goes away as a result) and drop functionheaders related to it from the internal pciehp header file.Link: http://lkml.kernel.org/r/1431632038-39917-1-git-send-email-jarod@redhat.comLink: https://bugzilla.kernel.org/show_bug.cgi?id=98581Reported-by: Jarod Wilson Signed-off-by: Rafael J. Wysocki Signed-off-by: Bjorn Helgaas Reviewed-by: Jarod Wilson Tested-by: Jarod Wilson List of files: /linux-6.15/drivers/pci/hotplug/Makefile

589fcc23 - PCI: Move pci_configure_slot() to drivers/pci/probe.c

Sat, 13 Sep 2014 02:02:00 +0000

PCI: Move pci_configure_slot() to drivers/pci/probe.cMove pci_configure_slot() and related functions fromdrivers/pci/hotplug/pcihp_slot to drivers/pci/probe.c.This is to prepare for doing device configuration during the normalenumeration process instead of just after hot-add.No functional change.Signed-off-by: Bjorn Helgaas List of files: /linux-6.15/drivers/pci/hotplug/Makefile

f7625980 - PCI: Fix whitespace, capitalization, and spelling errors

Thu, 14 Nov 2013 18:28:18 +0000

PCI: Fix whitespace, capitalization, and spelling errorsFix whitespace, capitalization, and spelling errors. No functional change.I know "busses" is not an error, but "buses" was more common, so I used itconsistently.Signed-off-by: Marta Rybczynska (pci_reset_bridge_secondary_bus())Signed-off-by: Bjorn Helgaas Acked-by: Rafael J. Wysocki List of files: /linux-6.15/drivers/pci/hotplug/Makefile

7441b062 - s390/pci: PCI hotplug support via SCLP

Thu, 29 Nov 2012 13:35:47 +0000

s390/pci: PCI hotplug support via SCLPAdd SCLP PCI configure/deconfigure and implement a PCI hotplugcontroller (s390_pci_hpc). The hotplug controller creates a slotfor every PCI function in stand-by or configured state. The PCIfunctions are named after the PCI function ID (fid). By writing tothe power attribute in /sys/bus/pci/slots//power the PCI functionis moved to stand-by or configured state. If moved to the configuredstate the device is automatically scanned by the s390 PCI layer.Signed-off-by: Jan Glauber Signed-off-by: Martin Schwidefsky List of files: /linux-6.15/drivers/pci/hotplug/Makefile

c2b5acc3 - PCI: Remove the fakephp driver

Fri, 24 Aug 2012 20:32:07 +0000

PCI: Remove the fakephp driverThe fakephp driver was scheduled for removal in 2011.Fakephp presented /sys/bus/pci/slots/.../power files for every PCIfunction. Writing "0" to one of these files logically removed the devicefrom the system. The PCI core now provides the same functionality with/sys/bus/pci/devices/.../remove.Signed-off-by: Bjorn Helgaas List of files: /linux-6.15/drivers/pci/hotplug/Makefile

3368dd29 - PCI hotplug: acpiphp should be linked after vendor drivers

Mon, 26 Oct 2009 17:18:22 +0000

PCI hotplug: acpiphp should be linked after vendor driversAs a followup to 71a082efc9fdc12068a3cee6cebb1330b00ebeee, it's conceivablethat some vendors may expose PCI hotplug functionality through both vendormechanisms and ACPI. The native mechanism will generally be a superset ofany functionality provided via ACPI, so the acpiphp driver should alwaysbe initialised after any others. Change the link order such that acpiphpwill not be initialised until any other statically linked drivers have hadan opportunity to claim the hardware.Signed-off-by: Matthew Garrett Signed-off-by: Jesse Barnes List of files: /linux-6.15/drivers/pci/hotplug/Makefile

8838400d - PCI hotplug: add pci_configure_slot()

Mon, 14 Sep 2009 22:35:20 +0000

PCI hotplug: add pci_configure_slot()This patch adds a new pci_configure_slot() function that programs thePCI bus characteristics for a newly-added device. This is based oncode in pciehp_pci.c, but should be generic enough to be used by pciehp,shpchp, and acpiphp.The hotplug_params struct and the program_hpp_typeX() functions are basedon the ACPI definitions, but they aren't really ACPI-specific, and there'sno alternate implementation, so I don't see the need to abstract them yet.Signed-off-by: Bjorn Helgaas Reviewed-by: Alex Chiang Reviewed-by: Kenji Kaneshige Acked-by: Kenji Kaneshige Signed-off-by: Jesse Barnes List of files: /linux-6.15/drivers/pci/hotplug/Makefile

8ffd2545 - PCI Hotplug: rename legacy_fakephp to fakephp

Fri, 20 Mar 2009 20:56:51 +0000

PCI Hotplug: rename legacy_fakephp to fakephpWe wanted to replace fakephp wholesale, so rename legacy_fakephp backto fakephp. Yes, this is a silly commit, but it produces a much easierpatch to read and review.Signed-off-by: Alex Chiang Signed-off-by: Jesse Barnes List of files: /linux-6.15/drivers/pci/hotplug/Makefile

83dbf66f - PCI Hotplug: restore fakephp interface with complete reimplementation

Fri, 20 Mar 2009 20:56:46 +0000

PCI Hotplug: restore fakephp interface with complete reimplementationA complete re-implementation of fakephp is necessary if it is topresent its former interface (pre-2.6.27, when it broke). Thereason is that PCI hotplug drivers call pci_hp_register(), whichenforces the rule that only one /sys/bus/pci/slots/ file may becreated per physical slot.The change breaks the old fakephp's assumption that it couldcreate a file per function. So we re-implement fakephp to avoidusing the standard PCI hotplug API so that we can restore the oldfakephp user interface.It puts entries in /sys/bus/pci/slots with the names of all PCIdevices/functions, exactly symmetrical to what is shown in/sys/bus/pci/devices. Each slots/ entry has a "power" attribute,which works the same way as the fakephp driver's power attributehas worked.There are a few improvements over old fakephp, which couldn't handlePCI devices being added or removed via a means outside offakephp's knowledge. If a device was added another way, old fakephpdidn't notice and didn't create the fake slot for it. If adevice was removed another way, old fakephp didn't delete the fakeslot for it (and accessing the stale slot caused an oops).The new implementation overcomes these limitations. As aconsequence, removing a bridge with other devices behind it nowworks as well, which is something else old fakephp couldn't dopreviously.This duplicates a tiny bit of the code in the PCI core that doesthis same function. Re-using that code ends up being morecomplex than duplicating it, and it makes code in the PCI coremore ugly just to support this legacy fakephp interfacecompatibility layer.Reviewed-by: James Cameron Signed-off-by: Trent Piepho Signed-off-by: Alex Chiang Signed-off-by: Jesse Barnes List of files: /linux-6.15/drivers/pci/hotplug/Makefile

71a082ef - PCI hotplug: Change link order of pciehp & acpiphp

Tue, 27 Jan 2009 01:03:35 +0000

PCI hotplug: Change link order of pciehp & acpiphpSome hardware exposes PCIE slots in such a way that they can be claimedby either the acpiphp or pciehp driver. pciehp is the preferred driverif the firmware allows the OS to claim control via the _OSC method soshould be loaded first - if it fails to bind (either due to a missing_OSC method or the firmware refusing to hand off control) then we canfall back to acpiphp or a vendor-specific driver.This patch simply changes the link order to ensure that pciehp will beinitialised before acpiphp if both are statically built into the kernel.Signed-off-by: Matthew Garrett Acked-by: Randy Dunlap Signed-off-by: Jesse Barnes List of files: /linux-6.15/drivers/pci/hotplug/Makefile

c9ffa5a5 - PCI: pciehp: add ACPI based slot detection

Wed, 17 Dec 2008 03:07:38 +0000

PCI: pciehp: add ACPI based slot detectionThere is a problem that some non hot-pluggable PCIe slots are detectedas hot-pluggable by pciehp on some platforms. The immediate cause ofthis problem is that hot-plug capable bit in the Slot Capabilitiesregister is set even for non hot-pluggable slots on those platforms.It seems a BIOS/hardware problem, but we need workaround about that.Some of those platforms define hot-pluggable PCIe slots on ACPInamespace properly, while hot-plug capable bit in the SlotCapabilities register is set improperly. So using ACPI namespaceinformation in pciehp to detect PCIe hot-pluggable slots would be aworkaround.This patch adds 'pciehp_detect_mode' module option. When 'acpi' isspecified, pciehp uses ACPI namespace information to detect PCIehot-pluggable slots.Signed-off-by: Kenji Kaneshige Signed-off-by: Jesse Barnes List of files: /linux-6.15/drivers/pci/hotplug/Makefile

561e55e8 - PCI: hotplug: Link fakephp last

Fri, 12 Oct 2007 23:20:33 +0000

PCI: hotplug: Link fakephp lastCurrently, fakephp will claim all devices; we really only want itto claim those not in slots.Signed-off-by: Alex Chiang Signed-off-by: Matthew Wilcox Signed-off-by: Kristen Carlson Accardi Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/pci/hotplug/Makefile

4e8662bb - ACPIPHP: use ACPI dock driver

Wed, 28 Jun 2006 07:08:06 +0000

ACPIPHP: use ACPI dock driverModify the acpiphp driver to use the ACPI dock driver for docknotifications. Only load the acpiphp driver if we find we have pci dockdevices.Signed-off-by: Kristen Carlson Accardi Signed-off-by: Adrian Bunk Signed-off-by: Andrew Morton Signed-off-by: Len Brown List of files: /linux-6.15/drivers/pci/hotplug/Makefile

783c49fc - [PATCH] PCI Hotplug: add common acpi functions to core

Fri, 03 Mar 2006 18:16:05 +0000

[PATCH] PCI Hotplug: add common acpi functions to coreshpchprm_acpi.c and pciehprm_acpi.c are nearly identical. In addition,there are functions in both these files that are also in acpiphp_glue.c.This patch will remove duplicate functions from shpchp, pciehp, andacpiphp and move this functionality to pci_hotplug, as it is nothardware specific. Get rid of shpchprm* and pciehprm* files since theyare no longer needed. shpchprm_nonacpi.c and pciehprm_nonacpi.c areidentical, as well as shpchprm_legacy.c and can be replaced with amacro.This patch also changes acpiphp to use the common hpp code.Signed-off-by: Kristen Carlson Accardi Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/pci/hotplug/Makefile

20416ea5 - [PATCH] acpiphp: add dock event handling

Fri, 24 Feb 2006 01:56:03 +0000

[PATCH] acpiphp: add dock event handlingThese patches add generic dock event handling to acpiphp. If there arepci devices that need to be inserted/removed after the dock event, theevent notification will be handed down to the normal pci hotplug eventhandler in acpiphp so that new bridges/devices can be enumerated.Because some dock stations do not have pci bridges or pci devices thatneed to be inserted after a dock, acpiphp will remain loaded to handledock events even if no hotpluggable pci slots are discovered.You probably need to have the pci=assign-busses kernel parameter enabledto use these patches, and you may not allow ibm_acpi to handle dockingnotifications and use this patch.This patch incorporates feedback provided by many.Signed-off-by: Kristen Carlson Accardi Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/pci/hotplug/Makefile