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 */
|
2005-04-17 05:20:36 +07:00
|
|
|
#ifndef __ASM_PARISC_PCI_H
|
|
|
|
#define __ASM_PARISC_PCI_H
|
|
|
|
|
2015-05-01 17:46:15 +07:00
|
|
|
#include <linux/scatterlist.h>
|
2005-04-17 05:20:36 +07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
** HP PCI platforms generally support multiple bus adapters.
|
|
|
|
** (workstations 1-~4, servers 2-~32)
|
|
|
|
**
|
|
|
|
** Newer platforms number the busses across PCI bus adapters *sparsely*.
|
|
|
|
** E.g. 0, 8, 16, ...
|
|
|
|
**
|
|
|
|
** Under a PCI bus, most HP platforms support PPBs up to two or three
|
|
|
|
** levels deep. See "Bit3" product line.
|
|
|
|
*/
|
|
|
|
#define PCI_MAX_BUSSES 256
|
|
|
|
|
2006-01-18 02:40:40 +07:00
|
|
|
|
|
|
|
/* To be used as: mdelay(pci_post_reset_delay);
|
|
|
|
*
|
|
|
|
* post_reset is the time the kernel should stall to prevent anyone from
|
|
|
|
* accessing the PCI bus once #RESET is de-asserted.
|
|
|
|
* PCI spec somewhere says 1 second but with multi-PCI bus systems,
|
|
|
|
* this makes the boot time much longer than necessary.
|
|
|
|
* 20ms seems to work for all the HP PCI implementations to date.
|
|
|
|
*/
|
|
|
|
#define pci_post_reset_delay 50
|
|
|
|
|
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
/*
|
|
|
|
** pci_hba_data (aka H2P_OBJECT in HP/UX)
|
|
|
|
**
|
|
|
|
** This is the "common" or "base" data structure which HBA drivers
|
|
|
|
** (eg Dino or LBA) are required to place at the top of their own
|
|
|
|
** platform_data structure. I've heard this called "C inheritance" too.
|
|
|
|
**
|
|
|
|
** Data needed by pcibios layer belongs here.
|
|
|
|
*/
|
|
|
|
struct pci_hba_data {
|
|
|
|
void __iomem *base_addr; /* aka Host Physical Address */
|
|
|
|
const struct parisc_device *dev; /* device from PA bus walk */
|
|
|
|
struct pci_bus *hba_bus; /* primary PCI bus below HBA */
|
|
|
|
int hba_num; /* I/O port space access "key" */
|
|
|
|
struct resource bus_num; /* PCI bus numbers */
|
|
|
|
struct resource io_space; /* PIOP */
|
|
|
|
struct resource lmmio_space; /* bus addresses < 4Gb */
|
|
|
|
struct resource elmmio_space; /* additional bus addresses < 4Gb */
|
|
|
|
struct resource gmmio_space; /* bus addresses > 4Gb */
|
|
|
|
|
|
|
|
/* NOTE: Dino code assumes it can use *all* of the lmmio_space,
|
|
|
|
* elmmio_space and gmmio_space as a contiguous array of
|
|
|
|
* resources. This #define represents the array size */
|
|
|
|
#define DINO_MAX_LMMIO_RESOURCES 3
|
|
|
|
|
|
|
|
unsigned long lmmio_space_offset; /* CPU view - PCI view */
|
|
|
|
void * iommu; /* IOMMU this device is under */
|
|
|
|
/* REVISIT - spinlock to protect resources? */
|
|
|
|
|
|
|
|
#define HBA_NAME_SIZE 16
|
|
|
|
char io_name[HBA_NAME_SIZE];
|
|
|
|
char lmmio_name[HBA_NAME_SIZE];
|
|
|
|
char elmmio_name[HBA_NAME_SIZE];
|
|
|
|
char gmmio_name[HBA_NAME_SIZE];
|
|
|
|
};
|
|
|
|
|
|
|
|
#define HBA_DATA(d) ((struct pci_hba_data *) (d))
|
|
|
|
|
|
|
|
/*
|
|
|
|
** We support 2^16 I/O ports per HBA. These are set up in the form
|
|
|
|
** 0xbbxxxx, where bb is the bus number and xxxx is the I/O port
|
|
|
|
** space address.
|
|
|
|
*/
|
|
|
|
#define HBA_PORT_SPACE_BITS 16
|
|
|
|
|
|
|
|
#define HBA_PORT_BASE(h) ((h) << HBA_PORT_SPACE_BITS)
|
|
|
|
#define HBA_PORT_SPACE_SIZE (1UL << HBA_PORT_SPACE_BITS)
|
|
|
|
|
|
|
|
#define PCI_PORT_HBA(a) ((a) >> HBA_PORT_SPACE_BITS)
|
|
|
|
#define PCI_PORT_ADDR(a) ((a) & (HBA_PORT_SPACE_SIZE - 1))
|
|
|
|
|
2005-10-22 09:49:05 +07:00
|
|
|
#ifdef CONFIG_64BIT
|
2005-04-17 05:20:36 +07:00
|
|
|
#define PCI_F_EXTEND 0xffffffff00000000UL
|
|
|
|
#else /* !CONFIG_64BIT */
|
|
|
|
#define PCI_F_EXTEND 0UL
|
|
|
|
#endif /* !CONFIG_64BIT */
|
|
|
|
|
|
|
|
/*
|
|
|
|
* If the PCI device's view of memory is the same as the CPU's view of memory,
|
|
|
|
* PCI_DMA_BUS_IS_PHYS is true. The networking and block device layers use
|
|
|
|
* this boolean for bounce buffer decisions.
|
|
|
|
*/
|
|
|
|
#ifdef CONFIG_PA20
|
|
|
|
/* All PA-2.0 machines have an IOMMU. */
|
|
|
|
#define PCI_DMA_BUS_IS_PHYS 0
|
|
|
|
#define parisc_has_iommu() do { } while (0)
|
|
|
|
#else
|
|
|
|
|
|
|
|
#if defined(CONFIG_IOMMU_CCIO) || defined(CONFIG_IOMMU_SBA)
|
|
|
|
extern int parisc_bus_is_phys; /* in arch/parisc/kernel/setup.c */
|
|
|
|
#define PCI_DMA_BUS_IS_PHYS parisc_bus_is_phys
|
|
|
|
#define parisc_has_iommu() do { parisc_bus_is_phys = 0; } while (0)
|
|
|
|
#else
|
|
|
|
#define PCI_DMA_BUS_IS_PHYS 1
|
|
|
|
#define parisc_has_iommu() do { } while (0)
|
|
|
|
#endif
|
|
|
|
|
|
|
|
#endif /* !CONFIG_PA20 */
|
|
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
** Most PCI devices (eg Tulip, NCR720) also export the same registers
|
|
|
|
** to both MMIO and I/O port space. Due to poor performance of I/O Port
|
2006-11-30 11:24:39 +07:00
|
|
|
** access under HP PCI bus adapters, strongly recommend the use of MMIO
|
2005-04-17 05:20:36 +07:00
|
|
|
** address space.
|
|
|
|
**
|
|
|
|
** While I'm at it more PA programming notes:
|
|
|
|
**
|
|
|
|
** 1) MMIO stores (writes) are posted operations. This means the processor
|
|
|
|
** gets an "ACK" before the write actually gets to the device. A read
|
|
|
|
** to the same device (or typically the bus adapter above it) will
|
|
|
|
** force in-flight write transaction(s) out to the targeted device
|
|
|
|
** before the read can complete.
|
|
|
|
**
|
|
|
|
** 2) The Programmed I/O (PIO) data may not always be strongly ordered with
|
|
|
|
** respect to DMA on all platforms. Ie PIO data can reach the processor
|
|
|
|
** before in-flight DMA reaches memory. Since most SMP PA platforms
|
|
|
|
** are I/O coherent, it generally doesn't matter...but sometimes
|
|
|
|
** it does.
|
|
|
|
**
|
|
|
|
** I've helped device driver writers debug both types of problems.
|
|
|
|
*/
|
|
|
|
struct pci_port_ops {
|
|
|
|
u8 (*inb) (struct pci_hba_data *hba, u16 port);
|
|
|
|
u16 (*inw) (struct pci_hba_data *hba, u16 port);
|
|
|
|
u32 (*inl) (struct pci_hba_data *hba, u16 port);
|
|
|
|
void (*outb) (struct pci_hba_data *hba, u16 port, u8 data);
|
|
|
|
void (*outw) (struct pci_hba_data *hba, u16 port, u16 data);
|
|
|
|
void (*outl) (struct pci_hba_data *hba, u16 port, u32 data);
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
|
|
struct pci_bios_ops {
|
|
|
|
void (*init)(void);
|
|
|
|
void (*fixup_bus)(struct pci_bus *bus);
|
|
|
|
};
|
|
|
|
|
|
|
|
/*
|
|
|
|
** Stuff declared in arch/parisc/kernel/pci.c
|
|
|
|
*/
|
|
|
|
extern struct pci_port_ops *pci_port;
|
|
|
|
extern struct pci_bios_ops *pci_bios;
|
|
|
|
|
|
|
|
#ifdef CONFIG_PCI
|
|
|
|
extern void pcibios_register_hba(struct pci_hba_data *);
|
|
|
|
#else
|
2007-10-17 04:24:59 +07:00
|
|
|
static inline void pcibios_register_hba(struct pci_hba_data *x)
|
2005-04-17 05:20:36 +07:00
|
|
|
{
|
|
|
|
}
|
|
|
|
#endif
|
2015-12-21 16:00:49 +07:00
|
|
|
extern void pcibios_init_bridge(struct pci_dev *);
|
2005-04-17 05:20:36 +07:00
|
|
|
|
|
|
|
/*
|
|
|
|
* pcibios_assign_all_busses() is used in drivers/pci/pci.c:pci_do_scan_bus()
|
|
|
|
* 0 == check if bridge is numbered before re-numbering.
|
|
|
|
* 1 == pci_do_scan_bus() should automatically number all PCI-PCI bridges.
|
|
|
|
*
|
|
|
|
* We *should* set this to zero for "legacy" platforms and one
|
|
|
|
* for PAT platforms.
|
|
|
|
*
|
|
|
|
* But legacy platforms also need to renumber the busses below a Host
|
|
|
|
* Bus controller. Adding a 4-port Tulip card on the first PCI root
|
|
|
|
* bus of a C200 resulted in the secondary bus being numbered as 1.
|
|
|
|
* The second PCI host bus controller's root bus had already been
|
|
|
|
* assigned bus number 1 by firmware and sysfs complained.
|
|
|
|
*
|
|
|
|
* Firmware isn't doing anything wrong here since each controller
|
|
|
|
* is its own PCI domain. It's simpler and easier for us to renumber
|
|
|
|
* the busses rather than treat each Dino as a separate PCI domain.
|
|
|
|
* Eventually, we may want to introduce PCI domains for Superdome or
|
|
|
|
* rp7420/8420 boxes and then revisit this issue.
|
|
|
|
*/
|
|
|
|
#define pcibios_assign_all_busses() (1)
|
|
|
|
|
|
|
|
#define PCIBIOS_MIN_IO 0x10
|
|
|
|
#define PCIBIOS_MIN_MEM 0x1000 /* NBPG - but pci/setup-res.c dies */
|
|
|
|
|
2006-09-20 08:37:09 +07:00
|
|
|
static inline int pci_get_legacy_ide_irq(struct pci_dev *dev, int channel)
|
|
|
|
{
|
|
|
|
return channel ? 15 : 14;
|
|
|
|
}
|
|
|
|
|
2013-06-14 14:05:41 +07:00
|
|
|
#define HAVE_PCI_MMAP
|
2017-04-12 19:26:04 +07:00
|
|
|
#define ARCH_GENERIC_PCI_MMAP_RESOURCE
|
2013-06-14 14:05:41 +07:00
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
#endif /* __ASM_PARISC_PCI_H */
|