mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-11-24 22:30:52 +07:00
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>
400 lines
11 KiB
Plaintext
400 lines
11 KiB
Plaintext
# SPDX-License-Identifier: GPL-2.0
|
|
if ETRAX_ARCH_V10
|
|
|
|
menu "CRIS v10 options"
|
|
|
|
# ETRAX 100LX v1 has a MMU "feature" requiring a low mapping
|
|
config CRIS_LOW_MAP
|
|
bool
|
|
depends on ETRAX_ARCH_V10 && ETRAX100LX
|
|
default y
|
|
|
|
config ETRAX_DRAM_VIRTUAL_BASE
|
|
hex
|
|
depends on ETRAX_ARCH_V10
|
|
default "c0000000" if !ETRAX100LX
|
|
default "60000000" if ETRAX100LX
|
|
|
|
choice
|
|
prompt "Product LED port"
|
|
depends on ETRAX_ARCH_V10
|
|
default ETRAX_PA_LEDS
|
|
|
|
config ETRAX_PA_LEDS
|
|
bool "Port-PA-LEDs"
|
|
help
|
|
The ETRAX network driver is responsible for flashing LED's when
|
|
packets arrive and are sent. It uses macros defined in
|
|
<file:arch/cris/include/asm/io.h>, and those macros are defined after
|
|
what YOU choose in this option. The actual bits used are configured
|
|
separately. Select this if the LEDs are on port PA. Some products
|
|
put the leds on PB or a memory-mapped latch (CSP0) instead.
|
|
|
|
config ETRAX_PB_LEDS
|
|
bool "Port-PB-LEDs"
|
|
help
|
|
The ETRAX network driver is responsible for flashing LED's when
|
|
packets arrive and are sent. It uses macros defined in
|
|
<file:arch/cris/include/asm/io.h>, and those macros are defined after
|
|
what YOU choose in this option. The actual bits used are configured
|
|
separately. Select this if the LEDs are on port PB. Some products
|
|
put the leds on PA or a memory-mapped latch (CSP0) instead.
|
|
|
|
config ETRAX_CSP0_LEDS
|
|
bool "Port-CSP0-LEDs"
|
|
help
|
|
The ETRAX network driver is responsible for flashing LED's when
|
|
packets arrive and are sent. It uses macros defined in
|
|
<file:arch/cris/include/asm/io.h>, and those macros are defined after
|
|
what YOU choose in this option. The actual bits used are configured
|
|
separately. Select this if the LEDs are on a memory-mapped latch
|
|
using chip select CSP0, this is mapped at 0x90000000.
|
|
Some products put the leds on PA or PB instead.
|
|
|
|
config ETRAX_NO_LEDS
|
|
bool "None"
|
|
help
|
|
Select this option if you don't have any LED at all.
|
|
|
|
endchoice
|
|
|
|
config ETRAX_LED1G
|
|
int "First green LED bit"
|
|
depends on ETRAX_ARCH_V10 && !ETRAX_NO_LEDS
|
|
default "2"
|
|
help
|
|
Bit to use for the first green LED.
|
|
Most Axis products use bit 2 here.
|
|
|
|
config ETRAX_LED1R
|
|
int "First red LED bit"
|
|
depends on ETRAX_ARCH_V10 && !ETRAX_NO_LEDS
|
|
default "3"
|
|
help
|
|
Bit to use for the first red LED.
|
|
Most Axis products use bit 3 here.
|
|
For products with only one controllable LED,
|
|
set this to same as CONFIG_ETRAX_LED1G (normally 2).
|
|
|
|
config ETRAX_LED2G
|
|
int "Second green LED bit"
|
|
depends on ETRAX_ARCH_V10 && !ETRAX_NO_LEDS
|
|
default "4"
|
|
help
|
|
Bit to use for the second green LED. The "Active" LED.
|
|
Most Axis products use bit 4 here.
|
|
For products with only one controllable LED,
|
|
set this to same as CONFIG_ETRAX_LED1G (normally 2).
|
|
|
|
config ETRAX_LED2R
|
|
int "Second red LED bit"
|
|
depends on ETRAX_ARCH_V10 && !ETRAX_NO_LEDS
|
|
default "5"
|
|
help
|
|
Bit to use for the second red LED.
|
|
Most Axis products use bit 5 here.
|
|
For products with only one controllable LED,
|
|
set this to same as CONFIG_ETRAX_LED1G (normally 2).
|
|
|
|
config ETRAX_LED3G
|
|
int "Third green LED bit"
|
|
depends on ETRAX_ARCH_V10 && !ETRAX_NO_LEDS
|
|
default "2"
|
|
help
|
|
Bit to use for the third green LED. The "Drive" LED.
|
|
For products with only one or two controllable LEDs,
|
|
set this to same as CONFIG_ETRAX_LED1G (normally 2).
|
|
|
|
config ETRAX_LED3R
|
|
int "Third red LED bit"
|
|
depends on ETRAX_ARCH_V10 && !ETRAX_NO_LEDS
|
|
default "2"
|
|
help
|
|
Bit to use for the third red LED.
|
|
For products with only one or two controllable LEDs,
|
|
set this to same as CONFIG_ETRAX_LED1G (normally 2).
|
|
|
|
config ETRAX_LED4R
|
|
int "Fourth red LED bit"
|
|
depends on ETRAX_CSP0_LEDS
|
|
default "2"
|
|
help
|
|
Bit to use for the fourth red LED.
|
|
For products with only one or two controllable LEDs,
|
|
set this to same as CONFIG_ETRAX_LED1G (normally 2).
|
|
|
|
config ETRAX_LED4G
|
|
int "Fourth green LED bit"
|
|
depends on ETRAX_CSP0_LEDS
|
|
default "2"
|
|
help
|
|
Bit to use for the fourth green LED.
|
|
For products with only one or two controllable LEDs,
|
|
set this to same as CONFIG_ETRAX_LED1G (normally 2).
|
|
|
|
config ETRAX_LED5R
|
|
int "Fifth red LED bit"
|
|
depends on ETRAX_CSP0_LEDS
|
|
default "2"
|
|
help
|
|
Bit to use for the fifth red LED.
|
|
For products with only one or two controllable LEDs,
|
|
set this to same as CONFIG_ETRAX_LED1G (normally 2).
|
|
|
|
config ETRAX_LED5G
|
|
int "Fifth green LED bit"
|
|
depends on ETRAX_CSP0_LEDS
|
|
default "2"
|
|
help
|
|
Bit to use for the fifth green LED.
|
|
For products with only one or two controllable LEDs,
|
|
set this to same as CONFIG_ETRAX_LED1G (normally 2).
|
|
|
|
config ETRAX_LED6R
|
|
int "Sixth red LED bit"
|
|
depends on ETRAX_CSP0_LEDS
|
|
default "2"
|
|
help
|
|
Bit to use for the sixth red LED.
|
|
For products with only one or two controllable LEDs,
|
|
set this to same as CONFIG_ETRAX_LED1G (normally 2).
|
|
|
|
config ETRAX_LED6G
|
|
int "Sixth green LED bit"
|
|
depends on ETRAX_CSP0_LEDS
|
|
default "2"
|
|
help
|
|
Bit to use for the sixth green LED. The "Drive" LED.
|
|
For products with only one or two controllable LEDs,
|
|
set this to same as CONFIG_ETRAX_LED1G (normally 2).
|
|
|
|
config ETRAX_LED7R
|
|
int "Seventh red LED bit"
|
|
depends on ETRAX_CSP0_LEDS
|
|
default "2"
|
|
help
|
|
Bit to use for the seventh red LED.
|
|
For products with only one or two controllable LEDs,
|
|
set this to same as CONFIG_ETRAX_LED1G (normally 2).
|
|
|
|
config ETRAX_LED7G
|
|
int "Seventh green LED bit"
|
|
depends on ETRAX_CSP0_LEDS
|
|
default "2"
|
|
help
|
|
Bit to use for the seventh green LED.
|
|
For products with only one or two controllable LEDs,
|
|
set this to same as CONFIG_ETRAX_LED1G (normally 2).
|
|
|
|
config ETRAX_LED8Y
|
|
int "Eighth yellow LED bit"
|
|
depends on ETRAX_CSP0_LEDS
|
|
default "2"
|
|
help
|
|
Bit to use for the eighth yellow LED. The "Drive" LED.
|
|
For products with only one or two controllable LEDs,
|
|
set this to same as CONFIG_ETRAX_LED1G (normally 2).
|
|
|
|
config ETRAX_LED9Y
|
|
int "Ninth yellow LED bit"
|
|
depends on ETRAX_CSP0_LEDS
|
|
default "2"
|
|
help
|
|
Bit to use for the ninth yellow LED.
|
|
For products with only one or two controllable LEDs,
|
|
set this to same as CONFIG_ETRAX_LED1G (normally 2).
|
|
|
|
config ETRAX_LED10Y
|
|
int "Tenth yellow LED bit"
|
|
depends on ETRAX_CSP0_LEDS
|
|
default "2"
|
|
help
|
|
Bit to use for the tenth yellow LED.
|
|
For products with only one or two controllable LEDs,
|
|
set this to same as CONFIG_ETRAX_LED1G (normally 2).
|
|
|
|
config ETRAX_LED11Y
|
|
int "Eleventh yellow LED bit"
|
|
depends on ETRAX_CSP0_LEDS
|
|
default "2"
|
|
help
|
|
Bit to use for the eleventh yellow LED.
|
|
For products with only one or two controllable LEDs,
|
|
set this to same as CONFIG_ETRAX_LED1G (normally 2).
|
|
|
|
config ETRAX_LED12R
|
|
int "Twelfth red LED bit"
|
|
depends on ETRAX_CSP0_LEDS
|
|
default "2"
|
|
help
|
|
Bit to use for the twelfth red LED.
|
|
For products with only one or two controllable LEDs,
|
|
set this to same as CONFIG_ETRAX_LED1G (normally 2).
|
|
|
|
|
|
choice
|
|
prompt "Product rescue-port"
|
|
depends on ETRAX_ARCH_V10
|
|
default ETRAX_RESCUE_SER0
|
|
|
|
config ETRAX_RESCUE_SER0
|
|
bool "Serial-0"
|
|
help
|
|
Select one of the four serial ports as a rescue port. The default
|
|
is port 0.
|
|
|
|
config ETRAX_RESCUE_SER1
|
|
bool "Serial-1"
|
|
help
|
|
Use serial port 1 as the rescue port.
|
|
|
|
config ETRAX_RESCUE_SER2
|
|
bool "Serial-2"
|
|
help
|
|
Use serial port 2 as the rescue port.
|
|
|
|
config ETRAX_RESCUE_SER3
|
|
bool "Serial-3"
|
|
help
|
|
Use serial port 3 as the rescue port.
|
|
|
|
endchoice
|
|
|
|
config ETRAX_DEF_R_WAITSTATES
|
|
hex "R_WAITSTATES"
|
|
depends on ETRAX_ARCH_V10
|
|
default "95a6"
|
|
help
|
|
Waitstates for SRAM, Flash and peripherals (not DRAM). 95f8 is a
|
|
good choice for most Axis products...
|
|
|
|
config ETRAX_DEF_R_BUS_CONFIG
|
|
hex "R_BUS_CONFIG"
|
|
depends on ETRAX_ARCH_V10
|
|
default "104"
|
|
help
|
|
Assorted bits controlling write mode, DMA burst length etc. 104 is
|
|
a good choice for most Axis products...
|
|
|
|
config ETRAX_SDRAM
|
|
bool "SDRAM support"
|
|
depends on ETRAX_ARCH_V10
|
|
help
|
|
Enable this if you use SDRAM chips and configure
|
|
R_SDRAM_CONFIG and R_SDRAM_TIMING as well.
|
|
|
|
config ETRAX_DEF_R_DRAM_CONFIG
|
|
hex "R_DRAM_CONFIG"
|
|
depends on ETRAX_ARCH_V10 && !ETRAX_SDRAM
|
|
default "1a200040"
|
|
help
|
|
The R_DRAM_CONFIG register specifies everything on how the DRAM
|
|
chips in the system are connected to the ETRAX CPU. This is
|
|
different depending on the manufacturer, chip type and number of
|
|
chips. So this value often needs to be different for each Axis
|
|
product.
|
|
|
|
config ETRAX_DEF_R_DRAM_TIMING
|
|
hex "R_DRAM_TIMING"
|
|
depends on ETRAX_ARCH_V10 && !ETRAX_SDRAM
|
|
default "5611"
|
|
help
|
|
Different DRAM chips have different speeds. Current Axis products
|
|
use 50ns DRAM chips which can use the timing: 5611.
|
|
|
|
config ETRAX_DEF_R_SDRAM_CONFIG
|
|
hex "R_SDRAM_CONFIG"
|
|
depends on ETRAX_ARCH_V10 && ETRAX_SDRAM
|
|
default "d2fa7878"
|
|
help
|
|
The R_SDRAM_CONFIG register specifies everything on how the SDRAM
|
|
chips in the system are connected to the ETRAX CPU. This is
|
|
different depending on the manufacturer, chip type and number of
|
|
chips. So this value often needs to be different for each Axis
|
|
product.
|
|
|
|
config ETRAX_DEF_R_SDRAM_TIMING
|
|
hex "R_SDRAM_TIMING"
|
|
depends on ETRAX_ARCH_V10 && ETRAX_SDRAM
|
|
default "80004801"
|
|
help
|
|
Different SDRAM chips have different timing.
|
|
|
|
config ETRAX_DEF_R_PORT_PA_DIR
|
|
hex "R_PORT_PA_DIR"
|
|
depends on ETRAX_ARCH_V10
|
|
default "1c"
|
|
help
|
|
Configures the direction of general port A bits. 1 is out, 0 is in.
|
|
This is often totally different depending on the product used.
|
|
There are some guidelines though - if you know that only LED's are
|
|
connected to port PA, then they are usually connected to bits 2-4
|
|
and you can therefore use 1c. On other boards which don't have the
|
|
LED's at the general ports, these bits are used for all kinds of
|
|
stuff. If you don't know what to use, it is always safe to put all
|
|
as inputs, although floating inputs isn't good.
|
|
|
|
config ETRAX_DEF_R_PORT_PA_DATA
|
|
hex "R_PORT_PA_DATA"
|
|
depends on ETRAX_ARCH_V10
|
|
default "00"
|
|
help
|
|
Configures the initial data for the general port A bits. Most
|
|
products should use 00 here.
|
|
|
|
config ETRAX_DEF_R_PORT_PB_CONFIG
|
|
hex "R_PORT_PB_CONFIG"
|
|
depends on ETRAX_ARCH_V10
|
|
default "00"
|
|
help
|
|
Configures the type of the general port B bits. 1 is chip select,
|
|
0 is port. Most products should use 00 here.
|
|
|
|
config ETRAX_DEF_R_PORT_PB_DIR
|
|
hex "R_PORT_PB_DIR"
|
|
depends on ETRAX_ARCH_V10
|
|
default "00"
|
|
help
|
|
Configures the direction of general port B bits. 1 is out, 0 is in.
|
|
This is often totally different depending on the product used. Bits
|
|
0 and 1 on port PB are usually used for I2C communication, but the
|
|
kernel I2C driver sets the appropriate directions itself so you
|
|
don't need to take that into consideration when setting this option.
|
|
If you don't know what to use, it is always safe to put all as
|
|
inputs.
|
|
|
|
config ETRAX_DEF_R_PORT_PB_DATA
|
|
hex "R_PORT_PB_DATA"
|
|
depends on ETRAX_ARCH_V10
|
|
default "ff"
|
|
help
|
|
Configures the initial data for the general port A bits. Most
|
|
products should use FF here.
|
|
|
|
config ETRAX_SOFT_SHUTDOWN
|
|
bool "Software Shutdown Support"
|
|
depends on ETRAX_ARCH_V10
|
|
help
|
|
Enable this if ETRAX is used with a power-supply that can be turned
|
|
off and on with PS_ON signal. Gives the possibility to detect
|
|
powerbutton and then do a power off after unmounting disks.
|
|
|
|
config ETRAX_SHUTDOWN_BIT
|
|
int "Shutdown bit on port CSP0"
|
|
depends on ETRAX_SOFT_SHUTDOWN
|
|
default "12"
|
|
help
|
|
Configure what pin on CSPO-port that is used for controlling power
|
|
supply.
|
|
|
|
config ETRAX_POWERBUTTON_BIT
|
|
int "Power button bit on port G"
|
|
depends on ETRAX_SOFT_SHUTDOWN
|
|
default "25"
|
|
help
|
|
Configure where power button is connected.
|
|
|
|
endmenu
|
|
|
|
endif
|