b24413180f
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>
217 lines
5.9 KiB
Plaintext
217 lines
5.9 KiB
Plaintext
# SPDX-License-Identifier: GPL-2.0
|
|
menuconfig ARCH_BCM
|
|
bool "Broadcom SoC Support"
|
|
depends on ARCH_MULTI_V6_V7
|
|
help
|
|
This enables support for Broadcom ARM based SoC chips
|
|
|
|
if ARCH_BCM
|
|
|
|
comment "IPROC architected SoCs"
|
|
|
|
config ARCH_BCM_IPROC
|
|
bool
|
|
select ARM_GIC
|
|
select CACHE_L2X0
|
|
select HAVE_ARM_SCU if SMP
|
|
select HAVE_ARM_TWD if SMP
|
|
select ARM_GLOBAL_TIMER
|
|
select CLKSRC_MMIO
|
|
select GPIOLIB
|
|
select ARM_AMBA
|
|
select PINCTRL
|
|
help
|
|
This enables support for systems based on Broadcom IPROC architected SoCs.
|
|
The IPROC complex contains one or more ARM CPUs along with common
|
|
core periperals. Application specific SoCs are created by adding a
|
|
uArchitecture containing peripherals outside of the IPROC complex.
|
|
Currently supported SoCs are Cygnus.
|
|
|
|
config ARCH_BCM_CYGNUS
|
|
bool "Broadcom Cygnus Support"
|
|
depends on ARCH_MULTI_V7
|
|
select ARCH_BCM_IPROC
|
|
help
|
|
Enable support for the Cygnus family,
|
|
which includes the following variants:
|
|
BCM11300, BCM11320, BCM11350, BCM11360,
|
|
BCM58300, BCM58302, BCM58303, BCM58305.
|
|
|
|
config ARCH_BCM_NSP
|
|
bool "Broadcom Northstar Plus SoC Support"
|
|
depends on ARCH_MULTI_V7
|
|
select ARCH_BCM_IPROC
|
|
select ARM_ERRATA_754322
|
|
select ARM_ERRATA_775420
|
|
select ARM_ERRATA_764369 if SMP
|
|
select HAVE_SMP
|
|
select THERMAL
|
|
select THERMAL_OF
|
|
help
|
|
Support for Broadcom Northstar Plus SoC.
|
|
Broadcom Northstar Plus family of SoCs are used for switching control
|
|
and management applications as well as residential router/gateway
|
|
applications. The SoC features dual core Cortex A9 ARM CPUs,
|
|
integrating several peripheral interfaces including multiple Gigabit
|
|
Ethernet PHYs, DDR3 memory, PCIE Gen-2, USB 2.0 and USB 3.0, serial and
|
|
NAND flash, SATA and several other IO controllers.
|
|
|
|
config ARCH_BCM_5301X
|
|
bool "Broadcom BCM470X / BCM5301X ARM SoC"
|
|
depends on ARCH_MULTI_V7
|
|
select ARCH_BCM_IPROC
|
|
select ARM_ERRATA_754322
|
|
select ARM_ERRATA_775420
|
|
select ARM_ERRATA_764369 if SMP
|
|
select HAVE_SMP
|
|
|
|
help
|
|
Support for Broadcom BCM470X and BCM5301X SoCs with ARM CPU cores.
|
|
|
|
This is a network SoC line mostly used in home routers and
|
|
wifi access points, it's internal name is Northstar.
|
|
This inclused the following SoC: BCM53010, BCM53011, BCM53012,
|
|
BCM53014, BCM53015, BCM53016, BCM53017, BCM53018, BCM4707,
|
|
BCM4708 and BCM4709.
|
|
|
|
Do not confuse this with the BCM4760 which is a totally
|
|
different SoC or with the older BCM47XX and BCM53XX based
|
|
network SoC using a MIPS CPU, they are supported by arch/mips/bcm47xx
|
|
|
|
comment "KONA architected SoCs"
|
|
|
|
config ARCH_BCM_MOBILE
|
|
bool
|
|
select GPIOLIB
|
|
select ARM_ERRATA_754322
|
|
select ARM_ERRATA_775420
|
|
select ARM_GIC
|
|
select GPIO_BCM_KONA
|
|
select TICK_ONESHOT
|
|
select HAVE_ARM_ARCH_TIMER
|
|
select PINCTRL
|
|
select ARCH_BCM_MOBILE_SMP if SMP
|
|
select BCM_KONA_TIMER
|
|
help
|
|
This enables support for systems based on Broadcom mobile SoCs.
|
|
|
|
config ARCH_BCM_281XX
|
|
bool "Broadcom BCM281XX SoC family"
|
|
depends on ARCH_MULTI_V7
|
|
select ARCH_BCM_MOBILE
|
|
select HAVE_SMP
|
|
help
|
|
Enable support for the BCM281XX family, which includes
|
|
BCM11130, BCM11140, BCM11351, BCM28145 and BCM28155
|
|
variants.
|
|
|
|
config ARCH_BCM_21664
|
|
bool "Broadcom BCM21664 SoC family"
|
|
depends on ARCH_MULTI_V7
|
|
select ARCH_BCM_MOBILE
|
|
select HAVE_SMP
|
|
help
|
|
Enable support for the BCM21664 family, which includes
|
|
BCM21663 and BCM21664 variants.
|
|
|
|
config ARCH_BCM_23550
|
|
bool "Broadcom BCM23550 SoC"
|
|
depends on ARCH_MULTI_V7
|
|
select ARCH_BCM_MOBILE
|
|
select HAVE_SMP
|
|
help
|
|
Enable support for the BCM23550.
|
|
|
|
config ARCH_BCM_MOBILE_L2_CACHE
|
|
bool "Broadcom mobile SoC level 2 cache support"
|
|
depends on ARCH_BCM_281XX || ARCH_BCM_21664
|
|
default y
|
|
select CACHE_L2X0
|
|
select ARCH_BCM_MOBILE_SMC
|
|
|
|
config ARCH_BCM_MOBILE_SMC
|
|
bool
|
|
depends on ARCH_BCM_MOBILE
|
|
|
|
config ARCH_BCM_MOBILE_SMP
|
|
bool
|
|
depends on ARCH_BCM_MOBILE
|
|
select HAVE_ARM_SCU
|
|
select ARM_ERRATA_764369
|
|
help
|
|
SMP support for the BCM281XX, BCM21664 and BCM23550 SoC families.
|
|
Provided as an option so SMP support for SoCs of this type
|
|
can be disabled for an SMP-enabled kernel.
|
|
|
|
comment "Other Architectures"
|
|
|
|
config ARCH_BCM2835
|
|
bool "Broadcom BCM2835 family"
|
|
depends on ARCH_MULTI_V6 || ARCH_MULTI_V7
|
|
select GPIOLIB
|
|
select ARM_AMBA
|
|
select ARM_ERRATA_411920 if ARCH_MULTI_V6
|
|
select ARM_TIMER_SP804
|
|
select HAVE_ARM_ARCH_TIMER if ARCH_MULTI_V7
|
|
select TIMER_OF
|
|
select BCM2835_TIMER
|
|
select PINCTRL
|
|
select PINCTRL_BCM2835
|
|
help
|
|
This enables support for the Broadcom BCM2835 and BCM2836 SoCs.
|
|
This SoC is used in the Raspberry Pi and Roku 2 devices.
|
|
|
|
config ARCH_BCM_53573
|
|
bool "Broadcom BCM53573 SoC series support"
|
|
depends on ARCH_MULTI_V7
|
|
select ARCH_BCM_IPROC
|
|
select HAVE_ARM_ARCH_TIMER
|
|
help
|
|
BCM53573 series is set of SoCs using ARM Cortex-A7 CPUs with wireless
|
|
embedded in the chipset.
|
|
This SoC line is mostly used in home routers and is some cheaper
|
|
alternative for Northstar family.
|
|
|
|
The base chip is BCM53573 and there are some packaging modifications
|
|
like BCM47189 and BCM47452.
|
|
|
|
config ARCH_BCM_63XX
|
|
bool "Broadcom BCM63xx DSL SoC"
|
|
depends on ARCH_MULTI_V7
|
|
depends on MMU
|
|
select ARM_ERRATA_754322
|
|
select ARM_ERRATA_764369 if SMP
|
|
select ARM_GIC
|
|
select ARM_GLOBAL_TIMER
|
|
select CACHE_L2X0
|
|
select HAVE_ARM_ARCH_TIMER
|
|
select HAVE_ARM_TWD if SMP
|
|
select HAVE_ARM_SCU if SMP
|
|
select HAVE_SMP
|
|
help
|
|
This enables support for systems based on Broadcom DSL SoCs.
|
|
It currently supports the 'BCM63XX' ARM-based family, which includes
|
|
the BCM63138 variant.
|
|
|
|
config ARCH_BRCMSTB
|
|
bool "Broadcom BCM7XXX based boards"
|
|
depends on ARCH_MULTI_V7
|
|
select ARM_GIC
|
|
select ARM_ERRATA_798181 if SMP
|
|
select HAVE_ARM_ARCH_TIMER
|
|
select BRCMSTB_L2_IRQ
|
|
select BCM7120_L2_IRQ
|
|
select ARCH_HAS_HOLES_MEMORYMODEL
|
|
select ARCH_DMA_ADDR_T_64BIT if ARM_LPAE
|
|
select ZONE_DMA if ARM_LPAE
|
|
select SOC_BRCMSTB
|
|
select SOC_BUS
|
|
help
|
|
Say Y if you intend to run the kernel on a Broadcom ARM-based STB
|
|
chipset.
|
|
|
|
This enables support for Broadcom ARM-based set-top box chipsets,
|
|
including the 7445 family of chips.
|
|
|
|
endif
|