License cleanup: add SPDX GPL-2.0 license identifier to files with no license
Many source files in the tree are missing licensing information, which
makes it harder for compliance tools to determine the correct license.
By default all files without license information are under the default
license 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 binding
shorthand, which can be used instead of the full boiler plate text.
This patch is based on work done by Thomas Gleixner and Kate Stewart and
Philippe Ombredanne.
How this work was done:
Patches were generated and checked against linux-4.14-rc6 for a subset of
the 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 cases
where non-standard license headers were used, and references to license
had to be inferred by heuristics based on keywords.
The analysis to determine which SPDX License Identifier to be applied to
a file was done in a spreadsheet of side by side results from of the
output of two independent scanners (ScanCode & Windriver) producing SPDX
tag:value files created by Philippe Ombredanne. Philippe prepared the
base 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 files
assessed. Kate Stewart did a file by file comparison of the scanner
results in the spreadsheet to determine which SPDX license identifier(s)
to be applied to the file. She confirmed any determination that was not
immediately 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 license
identifiers 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 the
spreadsheet to determine the SPDX license identifiers to apply to the
source files by Kate, Philippe, Thomas and, in some cases, confirmation
by lawyers working with the Linux Foundation.
Kate also obtained a third independent scan of the 4.13 code base from
FOSSology, and compared selected files where the other two scanners
disagreed against that SPDX file, to see if there was new insights. The
Windriver scanner is based on an older version of FOSSology in part, so
they are related.
Thomas did random spot checks in about 500 files from the spreadsheets
for the uapi headers and agreed with SPDX license identifier in the
files he inspected. For the non-uapi files Thomas did random spot checks
in about 15000 files.
In initial set of patches against 4.14-rc6, 3 files were found to have
copy/paste license identifier errors, and have been fixed to reflect the
correct identifier.
Additionally Philippe spent 10 hours this week doing a detailed manual
inspection and review of the 12,461 patched files from the initial patch
version 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 correct
This produced a worksheet with 20 files needing minor correction. This
worksheet was then exported into 3 different .csv files for the
different types of files to be modified.
These .csv files were then reviewed by Greg. Thomas wrote a script to
parse the csv files and add the proper SPDX tag to the file, in the
format that the file expected. This script was further refined by Greg
based on the output to detect more types of files automatically and to
distinguish between header and source .c files (which need different
comment types.) Finally Greg ran the script using the .csv files to
generate the patches.
Reviewed-by: Kate Stewart <kstewart@linuxfoundation.org>
Reviewed-by: Philippe Ombredanne <pombredanne@nexb.com>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-11-01 21:07:57 +07:00
|
|
|
/* SPDX-License-Identifier: GPL-2.0 */
|
2008-10-23 12:26:29 +07:00
|
|
|
#ifndef _ASM_X86_PCI_H
|
|
|
|
|
#define _ASM_X86_PCI_H
|
2007-10-13 04:07:23 +07:00
|
|
|
|
|
|
|
|
#include <linux/mm.h> /* for struct page */
|
|
|
|
|
#include <linux/types.h>
|
|
|
|
|
#include <linux/slab.h>
|
|
|
|
|
#include <linux/string.h>
|
2015-05-01 17:46:15 +07:00
|
|
|
#include <linux/scatterlist.h>
|
2019-03-06 06:42:58 +07:00
|
|
|
#include <linux/numa.h>
|
2007-10-13 04:07:23 +07:00
|
|
|
#include <asm/io.h>
|
2019-11-20 21:33:57 +07:00
|
|
|
#include <asm/memtype.h>
|
2010-10-07 03:12:28 +07:00
|
|
|
#include <asm/x86_init.h>
|
2007-10-13 04:07:23 +07:00
|
|
|
|
|
|
|
|
struct pci_sysdata {
|
|
|
|
|
int domain; /* PCI domain */
|
|
|
|
|
int node; /* NUMA node */
|
ACPI / PCI: Set root bridge ACPI handle in advance
The ACPI handles of PCI root bridges need to be known to
acpi_bind_one(), so that it can create the appropriate
"firmware_node" and "physical_node" files for them, but currently
the way it gets to know those handles is not exactly straightforward
(to put it lightly).
This is how it works, roughly:
1. acpi_bus_scan() finds the handle of a PCI root bridge,
creates a struct acpi_device object for it and passes that
object to acpi_pci_root_add().
2. acpi_pci_root_add() creates a struct acpi_pci_root object,
populates its "device" field with its argument's address
(device->handle is the ACPI handle found in step 1).
3. The struct acpi_pci_root object created in step 2 is passed
to pci_acpi_scan_root() and used to get resources that are
passed to pci_create_root_bus().
4. pci_create_root_bus() creates a struct pci_host_bridge object
and passes its "dev" member to device_register().
5. platform_notify(), which for systems with ACPI is set to
acpi_platform_notify(), is called.
So far, so good. Now it starts to be "interesting".
6. acpi_find_bridge_device() is used to find the ACPI handle of
the given device (which is the PCI root bridge) and executes
acpi_pci_find_root_bridge(), among other things, for the
given device object.
7. acpi_pci_find_root_bridge() uses the name (sic!) of the given
device object to extract the segment and bus numbers of the PCI
root bridge and passes them to acpi_get_pci_rootbridge_handle().
8. acpi_get_pci_rootbridge_handle() browses the list of ACPI PCI
root bridges and finds the one that matches the given segment
and bus numbers. Its handle is then used to initialize the
ACPI handle of the PCI root bridge's device object by
acpi_bind_one(). However, this is *exactly* the ACPI handle we
started with in step 1.
Needless to say, this is quite embarassing, but it may be avoided
thanks to commit f3fd0c8 (ACPI: Allow ACPI handles of devices to be
initialized in advance), which makes it possible to initialize the
ACPI handle of a device before passing it to device_register().
Accordingly, add a new __weak routine, pcibios_root_bridge_prepare(),
defaulting to an empty implementation that can be replaced by the
interested architecutres (x86 and ia64 at the moment) with functions
that will set the root bridge's ACPI handle before its dev member is
passed to device_register(). Make both x86 and ia64 provide such
implementations of pcibios_root_bridge_prepare() and remove
acpi_pci_find_root_bridge() and acpi_get_pci_rootbridge_handle() that
aren't necessary any more.
Included is a fix for breakage on systems with non-ACPI PCI host
bridges from Bjorn Helgaas.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
2013-01-10 04:33:37 +07:00
|
|
|
#ifdef CONFIG_ACPI
|
ACPI / driver core: Store an ACPI device pointer in struct acpi_dev_node
Modify struct acpi_dev_node to contain a pointer to struct acpi_device
associated with the given device object (that is, its ACPI companion
device) instead of an ACPI handle corresponding to it. Introduce two
new macros for manipulating that pointer in a CONFIG_ACPI-safe way,
ACPI_COMPANION() and ACPI_COMPANION_SET(), and rework the
ACPI_HANDLE() macro to take the above changes into account.
Drop the ACPI_HANDLE_SET() macro entirely and rework its users to
use ACPI_COMPANION_SET() instead. For some of them who used to
pass the result of acpi_get_child() directly to ACPI_HANDLE_SET()
introduce a helper routine acpi_preset_companion() doing an
equivalent thing.
The main motivation for doing this is that there are things
represented by struct acpi_device objects that don't have valid
ACPI handles (so called fixed ACPI hardware features, such as
power and sleep buttons) and we would like to create platform
device objects for them and "glue" them to their ACPI companions
in the usual way (which currently is impossible due to the
lack of valid ACPI handles). However, there are more reasons
why it may be useful.
First, struct acpi_device pointers allow of much better type checking
than void pointers which are ACPI handles, so it should be more
difficult to write buggy code using modified struct acpi_dev_node
and the new macros. Second, the change should help to reduce (over
time) the number of places in which the result of ACPI_HANDLE() is
passed to acpi_bus_get_device() in order to obtain a pointer to the
struct acpi_device associated with the given "physical" device,
because now that pointer is returned by ACPI_COMPANION() directly.
Finally, the change should make it easier to write generic code that
will build both for CONFIG_ACPI set and unset without adding explicit
compiler directives to it.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Tested-by: Mika Westerberg <mika.westerberg@linux.intel.com> # on Haswell
Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Reviewed-by: Aaron Lu <aaron.lu@intel.com> # for ATA and SDIO part
2013-11-12 04:41:56 +07:00
|
|
|
struct acpi_device *companion; /* ACPI companion device */
|
ACPI / PCI: Set root bridge ACPI handle in advance
The ACPI handles of PCI root bridges need to be known to
acpi_bind_one(), so that it can create the appropriate
"firmware_node" and "physical_node" files for them, but currently
the way it gets to know those handles is not exactly straightforward
(to put it lightly).
This is how it works, roughly:
1. acpi_bus_scan() finds the handle of a PCI root bridge,
creates a struct acpi_device object for it and passes that
object to acpi_pci_root_add().
2. acpi_pci_root_add() creates a struct acpi_pci_root object,
populates its "device" field with its argument's address
(device->handle is the ACPI handle found in step 1).
3. The struct acpi_pci_root object created in step 2 is passed
to pci_acpi_scan_root() and used to get resources that are
passed to pci_create_root_bus().
4. pci_create_root_bus() creates a struct pci_host_bridge object
and passes its "dev" member to device_register().
5. platform_notify(), which for systems with ACPI is set to
acpi_platform_notify(), is called.
So far, so good. Now it starts to be "interesting".
6. acpi_find_bridge_device() is used to find the ACPI handle of
the given device (which is the PCI root bridge) and executes
acpi_pci_find_root_bridge(), among other things, for the
given device object.
7. acpi_pci_find_root_bridge() uses the name (sic!) of the given
device object to extract the segment and bus numbers of the PCI
root bridge and passes them to acpi_get_pci_rootbridge_handle().
8. acpi_get_pci_rootbridge_handle() browses the list of ACPI PCI
root bridges and finds the one that matches the given segment
and bus numbers. Its handle is then used to initialize the
ACPI handle of the PCI root bridge's device object by
acpi_bind_one(). However, this is *exactly* the ACPI handle we
started with in step 1.
Needless to say, this is quite embarassing, but it may be avoided
thanks to commit f3fd0c8 (ACPI: Allow ACPI handles of devices to be
initialized in advance), which makes it possible to initialize the
ACPI handle of a device before passing it to device_register().
Accordingly, add a new __weak routine, pcibios_root_bridge_prepare(),
defaulting to an empty implementation that can be replaced by the
interested architecutres (x86 and ia64 at the moment) with functions
that will set the root bridge's ACPI handle before its dev member is
passed to device_register(). Make both x86 and ia64 provide such
implementations of pcibios_root_bridge_prepare() and remove
acpi_pci_find_root_bridge() and acpi_get_pci_rootbridge_handle() that
aren't necessary any more.
Included is a fix for breakage on systems with non-ACPI PCI host
bridges from Bjorn Helgaas.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
2013-01-10 04:33:37 +07:00
|
|
|
#endif
|
2007-10-13 04:07:23 +07:00
|
|
|
#ifdef CONFIG_X86_64
|
2008-03-23 15:03:04 +07:00
|
|
|
void *iommu; /* IOMMU private data */
|
2007-10-13 04:07:23 +07:00
|
|
|
#endif
|
2016-02-17 04:56:21 +07:00
|
|
|
#ifdef CONFIG_PCI_MSI_IRQ_DOMAIN
|
|
|
|
|
void *fwnode; /* IRQ domain for MSI assignment */
|
|
|
|
|
#endif
|
2016-09-13 22:05:40 +07:00
|
|
|
#if IS_ENABLED(CONFIG_VMD)
|
2020-01-21 20:37:46 +07:00
|
|
|
struct pci_dev *vmd_dev; /* VMD Device if in Intel VMD domain */
|
2016-09-13 22:05:40 +07:00
|
|
|
#endif
|
2007-10-13 04:07:23 +07:00
|
|
|
};
|
|
|
|
|
|
2008-05-12 20:43:37 +07:00
|
|
|
extern int pci_routeirq;
|
2008-06-11 21:35:14 +07:00
|
|
|
extern int noioapicquirk;
|
2008-07-15 18:48:55 +07:00
|
|
|
extern int noioapicreroute;
|
2008-05-12 20:43:37 +07:00
|
|
|
|
2020-01-21 20:37:45 +07:00
|
|
|
static inline struct pci_sysdata *to_pci_sysdata(const struct pci_bus *bus)
|
|
|
|
|
{
|
|
|
|
|
return bus->sysdata;
|
|
|
|
|
}
|
|
|
|
|
|
2020-02-04 04:53:06 +07:00
|
|
|
#ifdef CONFIG_PCI
|
|
|
|
|
|
2010-08-17 23:15:24 +07:00
|
|
|
#ifdef CONFIG_PCI_DOMAINS
|
2007-10-13 04:07:23 +07:00
|
|
|
static inline int pci_domain_nr(struct pci_bus *bus)
|
|
|
|
|
{
|
2020-01-21 20:37:45 +07:00
|
|
|
return to_pci_sysdata(bus)->domain;
|
2007-10-13 04:07:23 +07:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static inline int pci_proc_domain(struct pci_bus *bus)
|
|
|
|
|
{
|
|
|
|
|
return pci_domain_nr(bus);
|
|
|
|
|
}
|
2010-08-17 23:15:24 +07:00
|
|
|
#endif
|
2007-10-13 04:07:23 +07:00
|
|
|
|
2016-02-17 04:56:21 +07:00
|
|
|
#ifdef CONFIG_PCI_MSI_IRQ_DOMAIN
|
|
|
|
|
static inline void *_pci_root_bus_fwnode(struct pci_bus *bus)
|
|
|
|
|
{
|
2020-01-21 20:37:45 +07:00
|
|
|
return to_pci_sysdata(bus)->fwnode;
|
2016-02-17 04:56:21 +07:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
#define pci_root_bus_fwnode _pci_root_bus_fwnode
|
|
|
|
|
#endif
|
|
|
|
|
|
2020-01-21 20:37:45 +07:00
|
|
|
#if IS_ENABLED(CONFIG_VMD)
|
2016-09-13 22:05:40 +07:00
|
|
|
static inline bool is_vmd(struct pci_bus *bus)
|
|
|
|
|
{
|
2020-01-21 20:37:46 +07:00
|
|
|
return to_pci_sysdata(bus)->vmd_dev != NULL;
|
2016-09-13 22:05:40 +07:00
|
|
|
}
|
2020-01-21 20:37:45 +07:00
|
|
|
#else
|
|
|
|
|
#define is_vmd(bus) false
|
|
|
|
|
#endif /* CONFIG_VMD */
|
2016-09-13 22:05:40 +07:00
|
|
|
|
2007-10-13 04:07:23 +07:00
|
|
|
/* Can be used to override the logic in pci_scan_bus for skipping
|
|
|
|
|
already-configured bus numbers - to be used for buggy BIOSes
|
|
|
|
|
or architectures with incomplete PCI setup by the loader */
|
|
|
|
|
|
|
|
|
|
extern unsigned int pcibios_assign_all_busses(void);
|
2009-08-29 21:24:51 +07:00
|
|
|
extern int pci_legacy_init(void);
|
2007-10-13 04:07:23 +07:00
|
|
|
#else
|
2017-03-17 04:50:03 +07:00
|
|
|
static inline int pcibios_assign_all_busses(void) { return 0; }
|
2007-10-13 04:07:23 +07:00
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
extern unsigned long pci_mem_start;
|
|
|
|
|
#define PCIBIOS_MIN_IO 0x1000
|
|
|
|
|
#define PCIBIOS_MIN_MEM (pci_mem_start)
|
|
|
|
|
|
|
|
|
|
#define PCIBIOS_MIN_CARDBUS_IO 0x4000
|
|
|
|
|
|
2010-11-17 04:31:26 +07:00
|
|
|
extern int pcibios_enabled;
|
2014-01-29 06:40:36 +07:00
|
|
|
void pcibios_scan_root(int bus);
|
2007-10-13 04:07:23 +07:00
|
|
|
|
|
|
|
|
struct irq_routing_table *pcibios_get_irq_routing_table(void);
|
|
|
|
|
int pcibios_set_irq_routing(struct pci_dev *dev, int pin, int irq);
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
#define HAVE_PCI_MMAP
|
2017-04-12 19:25:54 +07:00
|
|
|
#define arch_can_pci_mmap_wc() pat_enabled()
|
2017-04-12 19:26:07 +07:00
|
|
|
#define ARCH_GENERIC_PCI_MMAP_RESOURCE
|
2007-10-13 04:07:23 +07:00
|
|
|
|
|
|
|
|
#ifdef CONFIG_PCI
|
2008-01-30 19:30:16 +07:00
|
|
|
extern void early_quirks(void);
|
|
|
|
|
#else
|
|
|
|
|
static inline void early_quirks(void) { }
|
2007-10-13 04:07:23 +07:00
|
|
|
#endif
|
|
|
|
|
|
2008-12-17 03:17:36 +07:00
|
|
|
extern void pci_iommu_alloc(void);
|
|
|
|
|
|
2010-10-07 03:12:28 +07:00
|
|
|
#ifdef CONFIG_PCI_MSI
|
|
|
|
|
/* implemented in arch/x86/kernel/apic/io_apic. */
|
2012-09-26 17:44:38 +07:00
|
|
|
struct msi_desc;
|
2010-10-07 03:12:28 +07:00
|
|
|
int native_setup_msi_irqs(struct pci_dev *dev, int nvec, int type);
|
|
|
|
|
void native_teardown_msi_irq(unsigned int irq);
|
2013-12-04 12:09:16 +07:00
|
|
|
void native_restore_msi_irqs(struct pci_dev *dev);
|
2010-10-07 03:12:28 +07:00
|
|
|
#else
|
|
|
|
|
#define native_setup_msi_irqs NULL
|
|
|
|
|
#define native_teardown_msi_irq NULL
|
|
|
|
|
#endif
|
2009-04-02 20:55:55 +07:00
|
|
|
|
2007-10-13 04:07:23 +07:00
|
|
|
/* generic pci stuff */
|
|
|
|
|
#include <asm-generic/pci.h>
|
|
|
|
|
|
2008-01-30 19:30:38 +07:00
|
|
|
#ifdef CONFIG_NUMA
|
|
|
|
|
/* Returns the node based on pci bus */
|
2008-12-26 18:53:38 +07:00
|
|
|
static inline int __pcibus_to_node(const struct pci_bus *bus)
|
2008-01-30 19:30:38 +07:00
|
|
|
{
|
2020-01-21 20:37:45 +07:00
|
|
|
return to_pci_sysdata(bus)->node;
|
2008-01-30 19:30:38 +07:00
|
|
|
}
|
2007-10-13 04:07:23 +07:00
|
|
|
|
2008-12-26 18:53:38 +07:00
|
|
|
static inline const struct cpumask *
|
|
|
|
|
cpumask_of_pcibus(const struct pci_bus *bus)
|
|
|
|
|
{
|
2009-09-18 17:41:10 +07:00
|
|
|
int node;
|
|
|
|
|
|
|
|
|
|
node = __pcibus_to_node(bus);
|
2019-03-06 06:42:58 +07:00
|
|
|
return (node == NUMA_NO_NODE) ? cpu_online_mask :
|
2009-09-18 17:41:10 +07:00
|
|
|
cpumask_of_node(node);
|
2008-12-26 18:53:38 +07:00
|
|
|
}
|
2008-01-30 19:30:38 +07:00
|
|
|
#endif
|
2007-10-13 04:07:23 +07:00
|
|
|
|
2012-12-06 04:33:26 +07:00
|
|
|
struct pci_setup_rom {
|
|
|
|
|
struct setup_data data;
|
|
|
|
|
uint16_t vendor;
|
|
|
|
|
uint16_t devid;
|
|
|
|
|
uint64_t pcilen;
|
|
|
|
|
unsigned long segment;
|
|
|
|
|
unsigned long bus;
|
|
|
|
|
unsigned long device;
|
|
|
|
|
unsigned long function;
|
|
|
|
|
uint8_t romdata[0];
|
|
|
|
|
};
|
|
|
|
|
|
2008-10-23 12:26:29 +07:00
|
|
|
#endif /* _ASM_X86_PCI_H */
|