Changes in Makefile

35fa2d88 - driver core: add a faux bus for use when a simple device/bus is needed

Mon, 10 Feb 2025 12:30:25 +0000

driver core: add a faux bus for use when a simple device/bus is neededMany drivers abuse the platform driver/bus system as it provides asimple way to create and bind a device to a driver-specific set ofprobe/release functions. Instead of doing that, and wasting all of thememory associated with a platform device, here is a "faux" bus thatcan be used instead.Reviewed-by: Jonathan Cameron Reviewed-by: Danilo Krummrich Reviewed-by: Lyude Paul Reviewed-by: Thomas Weißschuh Reviewed-by: Zijun Hu Link: https://lore.kernel.org/r/2025021026-atlantic-gibberish-3f0c@gregkhSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/base/Makefile

a8088783 - driver core: auxiliary bus: show auxiliary device IRQs

Sun, 14 Apr 2024 08:05:25 +0000

driver core: auxiliary bus: show auxiliary device IRQsPCI subfunctions (SF) are anchored on the auxiliary bus. PCI physicaland virtual functions are anchored on the PCI bus. The irq informationof each such function is visible to users via sysfs directory "msi_irqs"containing files for each irq entry. However, for PCI SFs suchinformation is unavailable. Due to this users have no visibility on IRQsused by the SFs.Secondly, an SF can be multi function device supporting rdma, netdeviceand more. Without irq information at the bus level, the user is unableto view or use the affinity of the SF IRQs.Hence to match to the equivalent PCI PFs and VFs, add "irqs" directory,for supporting auxiliary devices, containing file for each irq entry.For example:$ ls /sys/bus/auxiliary/devices/mlx5_core.sf.1/irqs/50 51 52 53 54 55 56 57 58Cc: Simon Horman Reviewed-by: Przemek Kitszel Reviewed-by: Parav Pandit Reviewed-by: Greg Kroah-Hartman Signed-off-by: Shay Drory Signed-off-by: Saeed Mahameed ---v9-v10:- remove Przemek RB- add name field to auxiliary_irq_info (Greg and Przemek)- handle bogus IRQ in auxiliary_device_sysfs_irq_remove (Greg)v8-v9:- add Przemek RB- use guard() in auxiliary_irq_dir_prepare (Paolo)v7-v8:- use cleanup.h for info and name fields (Greg)- correct error flow in auxiliary_irq_dir_prepare (Przemek)- add documentation for new fields of auxiliary_device (Simon)v6-v7:- dynamically creating irqs directory when first irq file created (Greg)- removed irqs flag and simplified the dev_add() API (Greg)- move sysfs related new code to a new auxiliary_sysfs.c file (Greg)v5-v6:- removed concept of shared and exclusive and hence global xarray (Greg)v4-v5:- restore global mutex and replace refcount_t with simple integer (Greg)v3->4:- remove global mutex (Przemek)v2->v3:- fix function declaration in case SYSFS isn't definedv1->v2:- move #ifdefs from drivers/base/auxiliary.c to include/linux/auxiliary_bus.h (Greg)- use EXPORT_SYMBOL_GPL instead of EXPORT_SYMBOL (Greg)- Fix kzalloc(ref) to kzalloc(*ref) (Simon)- Add return description in auxiliary_device_sysfs_irq_add() kdoc (Simon)- Fix auxiliary_irq_mode_show doc (kernel test boot) List of files: /linux-6.15/drivers/base/Makefile

13e7accb - genirq: Get rid of GENERIC_MSI_IRQ_DOMAIN

Fri, 11 Nov 2022 13:54:40 +0000

genirq: Get rid of GENERIC_MSI_IRQ_DOMAINAdjust to reality and remove another layer of pointless Kconfigindirection. CONFIG_GENERIC_MSI_IRQ is good enough to serveall purposes.Signed-off-by: Thomas Gleixner Reviewed-by: Jason Gunthorpe Link: https://lore.kernel.org/r/20221111122014.524842979@linutronix.de List of files: /linux-6.15/drivers/base/Makefile

6423d295 - driver core: Add sysfs support for physical location of a device

Mon, 14 Mar 2022 19:54:58 +0000

driver core: Add sysfs support for physical location of a deviceWhen ACPI table includes _PLD fields for a device, create a newdirectory (physical_location) in sysfs to share _PLD fields.Currently without PLD information, when there are multiple of samedevices, it is hard to distinguish which device corresponds to whichphysical device at which location. For example, when there are two TypeC connectors, it is hard to find out which connector corresponds to theType C port on the left panel versus the Type C port on the right panel.With PLD information provided, we can determine which specific device atwhich location is doing what._PLD output includes much more fields, but only generic fields are addedand exposed to sysfs, so that non-ACPI devices can also support it inthe future. The minimal generic fields needed for locating a device arethe following.- panel- vertical_position- horizontal_position- dock- lidSigned-off-by: Won Chung Link: https://lore.kernel.org/r/20220314195458.271430-1-wonchung@google.comSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/base/Makefile

50f9481e - mm/memory_hotplug: remove CONFIG_MEMORY_HOTPLUG_SPARSE

Fri, 05 Nov 2021 20:44:24 +0000

mm/memory_hotplug: remove CONFIG_MEMORY_HOTPLUG_SPARSECONFIG_MEMORY_HOTPLUG depends on CONFIG_SPARSEMEM, so there is no need forCONFIG_MEMORY_HOTPLUG_SPARSE anymore; adjust all instances to useCONFIG_MEMORY_HOTPLUG and remove CONFIG_MEMORY_HOTPLUG_SPARSE.Link: https://lkml.kernel.org/r/20210929143600.49379-3-david@redhat.comSigned-off-by: David Hildenbrand Acked-by: Shuah Khan [kselftest]Acked-by: Greg Kroah-Hartman Acked-by: Oscar Salvador Cc: Alex Shi Cc: Andy Lutomirski Cc: Benjamin Herrenschmidt Cc: Borislav Petkov Cc: Dave Hansen Cc: "H. Peter Anvin" Cc: Ingo Molnar Cc: Jason Wang Cc: Jonathan Corbet Cc: Michael Ellerman Cc: "Michael S. Tsirkin" Cc: Michal Hocko Cc: Mike Rapoport Cc: Paul Mackerras Cc: Peter Zijlstra Cc: "Rafael J. Wysocki" Cc: Thomas Gleixner Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/drivers/base/Makefile

09705dcb - devres: Enable trace events

Mon, 17 May 2021 12:29:46 +0000

devres: Enable trace eventsIn some cases the printf() mechanism is too heavy and can't be used.For example, when debugging a race condition involving devres API.When CONFIG_DEBUG_DEVRES is enabled I can't reproduce an issue, andotherwise it's quite visible with a useful information being collected.Enable trace events for devres part of the driver core.Signed-off-by: Andy Shevchenko Link: https://lore.kernel.org/r/20210517122946.53161-4-andriy.shevchenko@linux.intel.comSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/base/Makefile

ae3c107c - numa: Move numa implementation to common code

Thu, 19 Nov 2020 00:38:26 +0000

numa: Move numa implementation to common codeARM64 numa implementation is generic enough that RISC-V can reuse thatimplementation with very minor cosmetic changes. This will help bothARM64 and RISC-V in terms of maintanace and feature improvementMove the numa implementation code to common directory so that both ISAscan reuse this. This doesn't introduce any function changes for ARM64.Signed-off-by: Atish Patra Acked-by: Jonathan Cameron Tested-by: Jonathan Cameron Acked-by: Catalin Marinas Signed-off-by: Palmer Dabbelt List of files: /linux-6.15/drivers/base/Makefile

7de3697e - Add auxiliary bus support

Thu, 03 Dec 2020 00:54:24 +0000

Add auxiliary bus supportAdd support for the Auxiliary Bus, auxiliary_device and auxiliary_driver.It enables drivers to create an auxiliary_device and bind anauxiliary_driver to it.The bus supports probe/remove shutdown and suspend/resume callbacks.Each auxiliary_device has a unique string based id; driver binds toan auxiliary_device based on this id through the bus.Co-developed-by: Kiran Patil Co-developed-by: Ranjani Sridharan Co-developed-by: Fred Oh Co-developed-by: Leon Romanovsky Signed-off-by: Kiran Patil Signed-off-by: Ranjani Sridharan Signed-off-by: Fred Oh Signed-off-by: Leon Romanovsky Signed-off-by: Dave Ertman Reviewed-by: Pierre-Louis Bossart Reviewed-by: Shiraz Saleem Reviewed-by: Parav Pandit Reviewed-by: Dan Williams Reviewed-by: Martin Habets Link: https://lore.kernel.org/r/20201113161859.1775473-2-david.m.ertman@intel.comSigned-off-by: Dan Williams Link: https://lore.kernel.org/r/160695681289.505290.8978295443574440604.stgit@dwillia2-desk3.amr.corp.intel.comSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/base/Makefile

d7cf5590 - device property: Move fwnode_connection_find_match() under drivers/base/property.c

Mon, 07 Sep 2020 12:05:31 +0000

device property: Move fwnode_connection_find_match() under drivers/base/property.cThe function is now only a helper that searches theconnection from device graph and then by checking if thesupplied connection identifier matches a property thatcontains reference.Signed-off-by: Heikki Krogerus Link: https://lore.kernel.org/r/20200907120532.37611-2-heikki.krogerus@linux.intel.comSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/base/Makefile

59abd836 - drivers: base: Introducing software nodes to the firmware node framework

Fri, 09 Nov 2018 14:21:36 +0000

drivers: base: Introducing software nodes to the firmware node frameworkSoftware node is a new struct fwnode_handle type that can beused to describe devices in kernel (software). It is meantto complement fwnodes representing real firmware nodes whenthey are incomplete (for example missing device properties)and to supply the primary fwnode when the firmware lackshardware description for a device completely.The software node type is really meant to replace thecurrently used "property_set" struct fwnode_handle type. Thehandling of struct property_set is glued to the genericdevice property handling code, and it is not possible tocreate a struct property_set independently from the devicethat it is bind to. struct property_set is only created whendevice properties are added to already initialized structdevice, and control of it is only possible from the genericproperty handling code.Software nodes are instead designed to be createdindependently from the device entries (struct device). Itmakes them much more flexible, as then the device meant tobe bind to the node can be created at a later time, and fromanother location. It is also possible to bind multipledevices to a single software node if needed.The software node implementation also includes support fornode hierarchy, which was the main motivation for thiscommit. The node hierarchy was something that was requestedfor the struct property_set, but it did not seem reasonableto try to extend the property_set support for that purpose.struct property_set was really meant only for deviceproperty handling like the name suggests.Support for struct property_set is not yet removed in thiscommit, but it will be in the following one.Signed-off-by: Heikki Krogerus Acked-by: Linus Walleij Reviewed-by: Andy Shevchenko Signed-off-by: Rafael J. Wysocki List of files: /linux-6.15/drivers/base/Makefile

cf65a0f6 - dma-mapping: move all DMA mapping code to kernel/dma

Tue, 12 Jun 2018 17:01:45 +0000

dma-mapping: move all DMA mapping code to kernel/dmaCurrently the code is split over various files with dma- prefixes in thelib/ and drives/base directories, and the number of files keeps growing.Move them into a single directory to keep the code together and removethe file name prefixes. To match the irq infrastructure this directoryis placed under the kernel/ directory.Signed-off-by: Christoph Hellwig List of files: /linux-6.15/drivers/base/Makefile

f2d9b66d - drivers: base: Unified device connection lookup

Tue, 20 Mar 2018 12:57:02 +0000

drivers: base: Unified device connection lookupSeveral frameworks - clk, gpio, phy, pmw, etc. - maintainlookup tables for describing connections and provide customAPI for handling them. This introduces a single genericlookup table and API for the connections.The motivation for this commit is centralizing theconnection lookup, but the goal is to ultimately extract theconnection descriptions also from firmware by using thefwnode_graph_* functions and other mechanisms that areavailable.Reviewed-by: Hans de Goede Reviewed-by: Andy Shevchenko Signed-off-by: Heikki Krogerus Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/base/Makefile

5d6d1ddd - firmware: move firmware loader into its own directory

Sat, 10 Mar 2018 14:14:50 +0000

firmware: move firmware loader into its own directoryThis will make it much easier to manage as we manage tokeep trimming componnents down into their own files to moreeasily manage and maintain this codebase.Suggested-by: Kees Cook Signed-off-by: Luis R. Rodriguez Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/base/Makefile

d73f821c - firmware: split firmware fallback functionality into its own file

Sat, 10 Mar 2018 14:14:49 +0000

firmware: split firmware fallback functionality into its own fileThe firmware fallback code is optional. Split that code out to helpdistinguish the fallback functionlity from othere core firmware loaderfeatures. This should make it easier to maintain and review codechanges.The reason for keeping the configuration onto a table which is built-inif you enable firmware loading is so that we can later enable the kernelafter subsequent patches to tweak this configuration, even if thefirmware loader is modular.This introduces no functional changes.Signed-off-by: Luis R. Rodriguez Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/base/Makefile

ad4365f1 - firmware: enable to split firmware_class into separate target files

Sat, 10 Mar 2018 14:14:45 +0000

firmware: enable to split firmware_class into separate target filesThe firmware loader code has grown quite a bit over the years.The practice of stuffing everything we need into one file makesthe code hard to follow.In order to split the firmware loader code into different componentswe must pick a module name and a first object target file. We mustkeep the firmware_class name to remain compatible with scripts whichhave been relying on the sysfs loader path for years, so the old modulename stays. We can however rename the C file without affecting themodule name.The firmware_class used to represent the idea that the code was a simplesysfs firmware loader, provided by the struct class firmware_class.The sysfs firmware loader used to be the default, today its only thefallback mechanism.This only renames the target code then to make emphasis of what the codedoes these days. With this change new features can also use a new objectfiles.Signed-off-by: Luis R. Rodriguez Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/base/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/base/Makefile

2ef7a295 - arm, arm64: factorize common cpu capacity default code

Wed, 31 May 2017 16:59:28 +0000

arm, arm64: factorize common cpu capacity default codearm and arm64 share lot of code relative to parsing CPU capacityinformation from DT, using that information for appropriate scaling andexposing a sysfs interface for chaging such values at runtime.Factorize such code in a common place (driver/base/arch_topology.c) inpreparation for further additions.Suggested-by: Will Deacon Suggested-by: Mark Rutland Suggested-by: Catalin Marinas Cc: Russell King Cc: Catalin Marinas Cc: Will Deacon Cc: Greg Kroah-Hartman Signed-off-by: Juri Lelli Acked-by: Russell King Acked-by: Catalin Marinas Acked-by: Greg Kroah-Hartman Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/base/Makefile

79543cf2 - driver-core: add test module for asynchronous probing

Thu, 29 Sep 2016 15:13:14 +0000

driver-core: add test module for asynchronous probingThis test module tries to test asynchronous driver probing by having adriver that sleeps for an extended period of time (5 secs) in itsprobe() method. It measures the time needed to register this driver(with device already registered) and a new device (with driver alreadyregistered). The module will fail to load if the time spent in registercall is more than half the probing sleep time.As a sanity check the driver will then try to synchronously registerdriver and device and fail if registration takes less than half of theprobing sleep time.Signed-off-by: Dmitry Torokhov Reviewed-by: Olof Johansson Signed-off-by: Guenter Roeck Signed-off-by: Thierry Escande Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/base/Makefile

3a495511 - isa: Allow ISA-style drivers on modern systems

Fri, 27 May 2016 22:08:27 +0000

isa: Allow ISA-style drivers on modern systemsSeveral modern devices, such as PC/104 cards, are expected to run onmodern systems via an ISA bus interface. Since ISA is a legacy interfacefor most modern architectures, ISA support should remain disabled ingeneral. Support for ISA-style drivers should be enabled on a per driverbasis.To allow ISA-style drivers on modern systems, this patch introduces theISA_BUS_API and ISA_BUS Kconfig options. The ISA bus driver will nowbuild conditionally on the ISA_BUS_API Kconfig option, which defaults tothe legacy ISA Kconfig option. The ISA_BUS Kconfig option allows theISA_BUS_API Kconfig option to be selected on architectures which do notenable ISA (e.g. X86_64).The ISA_BUS Kconfig option is currently only implemented for X86architectures. Other architectures may have their own ISA_BUS Kconfigoptions added as required.Reviewed-by: Guenter Roeck Signed-off-by: William Breathitt Gray Acked-by: Linus Torvalds Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/base/Makefile

8ac0fba2 - isa: Decouple X86_32 dependency from the ISA Kconfig option

Sun, 01 May 2016 21:50:29 +0000

isa: Decouple X86_32 dependency from the ISA Kconfig optionThe introduction of the ISA_BUS option blocks the compilation of ISAdrivers on non-x86 platforms. The ISA_BUS configuration option shouldnot be necessary if the X86_32 dependency can be decoupled from the ISAconfiguration option. This patch both removes the ISA_BUS configurationoption entirely and removes the X86_32 dependency from the ISAconfiguration option.Acked-by: Ingo Molnar Signed-off-by: William Breathitt Gray Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/base/Makefile