forked from luck/tmp_suning_uos_patched
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>
249 lines
6.9 KiB
Plaintext
249 lines
6.9 KiB
Plaintext
# SPDX-License-Identifier: GPL-2.0
|
|
if ARCH_DAVINCI
|
|
|
|
config AINTC
|
|
bool
|
|
|
|
config CP_INTC
|
|
bool
|
|
select IRQ_DOMAIN
|
|
|
|
config ARCH_DAVINCI_DMx
|
|
bool
|
|
|
|
menu "TI DaVinci Implementations"
|
|
|
|
comment "DaVinci Core Type"
|
|
|
|
config ARCH_DAVINCI_DM644x
|
|
bool "DaVinci 644x based system"
|
|
select AINTC
|
|
select ARCH_DAVINCI_DMx
|
|
|
|
config ARCH_DAVINCI_DM355
|
|
bool "DaVinci 355 based system"
|
|
select AINTC
|
|
select ARCH_DAVINCI_DMx
|
|
|
|
config ARCH_DAVINCI_DM646x
|
|
bool "DaVinci 646x based system"
|
|
select AINTC
|
|
select ARCH_DAVINCI_DMx
|
|
|
|
config ARCH_DAVINCI_DA830
|
|
bool "DA830/OMAP-L137/AM17x based system"
|
|
depends on !ARCH_DAVINCI_DMx || (AUTO_ZRELADDR && ARM_PATCH_PHYS_VIRT)
|
|
select ARCH_DAVINCI_DA8XX
|
|
# needed on silicon revs 1.0, 1.1:
|
|
select CPU_DCACHE_WRITETHROUGH if !CPU_DCACHE_DISABLE
|
|
select CP_INTC
|
|
|
|
config ARCH_DAVINCI_DA850
|
|
bool "DA850/OMAP-L138/AM18x based system"
|
|
depends on !ARCH_DAVINCI_DMx || (AUTO_ZRELADDR && ARM_PATCH_PHYS_VIRT)
|
|
select ARCH_DAVINCI_DA8XX
|
|
select CP_INTC
|
|
|
|
config ARCH_DAVINCI_DA8XX
|
|
bool
|
|
|
|
config ARCH_DAVINCI_DM365
|
|
bool "DaVinci 365 based system"
|
|
select AINTC
|
|
select ARCH_DAVINCI_DMx
|
|
|
|
comment "DaVinci Board Type"
|
|
|
|
config MACH_DA8XX_DT
|
|
bool "Support DA8XX platforms using device tree"
|
|
default y
|
|
depends on ARCH_DAVINCI_DA850
|
|
select PINCTRL
|
|
help
|
|
Say y here to include support for TI DaVinci DA850 based using
|
|
Flattened Device Tree. More information at Documentation/devicetree
|
|
|
|
config MACH_DAVINCI_EVM
|
|
bool "TI DM644x EVM"
|
|
default ARCH_DAVINCI_DM644x
|
|
depends on ARCH_DAVINCI_DM644x
|
|
help
|
|
Configure this option to specify the whether the board used
|
|
for development is a DM644x EVM
|
|
|
|
config MACH_SFFSDR
|
|
bool "Lyrtech SFFSDR"
|
|
depends on ARCH_DAVINCI_DM644x
|
|
help
|
|
Say Y here to select the Lyrtech Small Form Factor
|
|
Software Defined Radio (SFFSDR) board.
|
|
|
|
config MACH_NEUROS_OSD2
|
|
bool "Neuros OSD2 Open Television Set Top Box"
|
|
depends on ARCH_DAVINCI_DM644x
|
|
help
|
|
Configure this option to specify the whether the board used
|
|
for development is a Neuros OSD2 Open Set Top Box.
|
|
|
|
config MACH_DAVINCI_DM355_EVM
|
|
bool "TI DM355 EVM"
|
|
default ARCH_DAVINCI_DM355
|
|
depends on ARCH_DAVINCI_DM355
|
|
help
|
|
Configure this option to specify the whether the board used
|
|
for development is a DM355 EVM
|
|
|
|
config MACH_DM355_LEOPARD
|
|
bool "DM355 Leopard board"
|
|
depends on ARCH_DAVINCI_DM355
|
|
help
|
|
Configure this option to specify the whether the board used
|
|
for development is a DM355 Leopard board.
|
|
|
|
config MACH_DAVINCI_DM6467_EVM
|
|
bool "TI DM6467 EVM"
|
|
default ARCH_DAVINCI_DM646x
|
|
depends on ARCH_DAVINCI_DM646x
|
|
select MACH_DAVINCI_DM6467TEVM
|
|
help
|
|
Configure this option to specify the whether the board used
|
|
for development is a DM6467 EVM
|
|
|
|
config MACH_DAVINCI_DM6467TEVM
|
|
bool
|
|
|
|
config MACH_DAVINCI_DM365_EVM
|
|
bool "TI DM365 EVM"
|
|
default ARCH_DAVINCI_DM365
|
|
depends on ARCH_DAVINCI_DM365
|
|
help
|
|
Configure this option to specify whether the board used
|
|
for development is a DM365 EVM
|
|
|
|
config MACH_DAVINCI_DA830_EVM
|
|
bool "TI DA830/OMAP-L137/AM17x Reference Platform"
|
|
default ARCH_DAVINCI_DA830
|
|
depends on ARCH_DAVINCI_DA830
|
|
select GPIO_PCF857X if I2C
|
|
help
|
|
Say Y here to select the TI DA830/OMAP-L137/AM17x Evaluation Module.
|
|
|
|
choice
|
|
prompt "Select DA830/OMAP-L137/AM17x UI board peripheral"
|
|
depends on MACH_DAVINCI_DA830_EVM
|
|
help
|
|
The presence of UI card on the DA830/OMAP-L137/AM17x EVM is
|
|
detected automatically based on successful probe of the I2C
|
|
based GPIO expander on that board. This option selected in this
|
|
menu has an effect only in case of a successful UI card detection.
|
|
|
|
config DA830_UI_LCD
|
|
bool "LCD"
|
|
help
|
|
Say Y here to use the LCD as a framebuffer or simple character
|
|
display.
|
|
|
|
config DA830_UI_NAND
|
|
bool "NAND flash"
|
|
help
|
|
Say Y here to use the NAND flash. Do not forget to setup
|
|
the switch correctly.
|
|
endchoice
|
|
|
|
config MACH_DAVINCI_DA850_EVM
|
|
bool "TI DA850/OMAP-L138/AM18x Reference Platform"
|
|
default ARCH_DAVINCI_DA850
|
|
depends on ARCH_DAVINCI_DA850
|
|
help
|
|
Say Y here to select the TI DA850/OMAP-L138/AM18x Evaluation Module.
|
|
|
|
choice
|
|
prompt "Select peripherals connected to expander on UI board"
|
|
depends on MACH_DAVINCI_DA850_EVM
|
|
help
|
|
The presence of User Interface (UI) card on the DA850/OMAP-L138/AM18x
|
|
EVM is detected automatically based on successful probe of the I2C
|
|
based GPIO expander on that card. This option selected in this
|
|
menu has an effect only in case of a successful UI card detection.
|
|
|
|
config DA850_UI_NONE
|
|
bool "No peripheral is enabled"
|
|
help
|
|
Say Y if you do not want to enable any of the peripherals connected
|
|
to TCA6416 expander on DA850/OMAP-L138/AM18x EVM UI card
|
|
|
|
config DA850_UI_RMII
|
|
bool "RMII Ethernet PHY"
|
|
help
|
|
Say Y if you want to use the RMII PHY on the DA850/OMAP-L138/AM18x
|
|
EVM. This PHY is found on the UI daughter card that is supplied with
|
|
the EVM.
|
|
NOTE: Please take care while choosing this option, MII PHY will
|
|
not be functional if RMII mode is selected.
|
|
|
|
config DA850_UI_SD_VIDEO_PORT
|
|
bool "Video Port Interface"
|
|
help
|
|
Say Y if you want to use Video Port Interface (VPIF) on the
|
|
DA850/OMAP-L138 EVM. The Video decoders/encoders are found on the
|
|
UI daughter card that is supplied with the EVM.
|
|
|
|
endchoice
|
|
|
|
config MACH_MITYOMAPL138
|
|
bool "Critical Link MityDSP-L138/MityARM-1808 SoM"
|
|
depends on ARCH_DAVINCI_DA850
|
|
help
|
|
Say Y here to select the Critical Link MityDSP-L138/MityARM-1808
|
|
System on Module. Information on this SoM may be found at
|
|
http://www.mitydsp.com
|
|
|
|
config MACH_OMAPL138_HAWKBOARD
|
|
bool "TI AM1808 / OMAPL-138 Hawkboard platform"
|
|
depends on ARCH_DAVINCI_DA850
|
|
help
|
|
Say Y here to select the TI AM1808 / OMAPL-138 Hawkboard platform .
|
|
Information of this board may be found at
|
|
http://www.hawkboard.org/
|
|
|
|
config DAVINCI_MUX
|
|
bool "DAVINCI multiplexing support"
|
|
depends on ARCH_DAVINCI
|
|
default y
|
|
help
|
|
Pin multiplexing support for DAVINCI boards. If your bootloader
|
|
sets the multiplexing correctly, say N. Otherwise, or if unsure,
|
|
say Y.
|
|
|
|
config DAVINCI_MUX_DEBUG
|
|
bool "Multiplexing debug output"
|
|
depends on DAVINCI_MUX
|
|
help
|
|
Makes the multiplexing functions print out a lot of debug info.
|
|
This is useful if you want to find out the correct values of the
|
|
multiplexing registers.
|
|
|
|
config DAVINCI_MUX_WARNINGS
|
|
bool "Warn about pins the bootloader didn't set up"
|
|
depends on DAVINCI_MUX
|
|
help
|
|
Choose Y here to warn whenever driver initialization logic needs
|
|
to change the pin multiplexing setup. When there are no warnings
|
|
printed, it's safe to deselect DAVINCI_MUX for your product.
|
|
|
|
config DAVINCI_RESET_CLOCKS
|
|
bool "Reset unused clocks during boot"
|
|
depends on ARCH_DAVINCI
|
|
help
|
|
Say Y if you want to reset unused clocks during boot.
|
|
This option saves power, but assumes all drivers are
|
|
using the clock framework. Broken drivers that do not
|
|
yet use clock framework may not work with this option.
|
|
If you are booting from another operating system, you
|
|
probably do not want this option enabled until your
|
|
device drivers work properly.
|
|
|
|
endmenu
|
|
|
|
endif
|