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 22:07:57 +08:00
|
|
|
# SPDX-License-Identifier: GPL-2.0
|
2014-09-09 05:29:25 +08:00
|
|
|
config ARCH_OMAP
|
|
|
|
|
bool
|
|
|
|
|
|
2005-07-11 02:58:15 +08:00
|
|
|
if ARCH_OMAP
|
|
|
|
|
|
2010-07-05 21:31:47 +08:00
|
|
|
menu "TI OMAP Common Features"
|
2005-07-11 02:58:15 +08:00
|
|
|
|
|
|
|
|
config ARCH_OMAP_OTG
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
comment "OMAP Feature Selections"
|
|
|
|
|
|
2006-12-07 09:14:03 +08:00
|
|
|
config OMAP_DEBUG_DEVICES
|
2006-12-07 09:14:03 +08:00
|
|
|
bool
|
|
|
|
|
help
|
2006-12-07 09:14:03 +08:00
|
|
|
For debug cards on TI reference boards.
|
|
|
|
|
|
|
|
|
|
config OMAP_DEBUG_LEDS
|
2012-03-14 02:14:39 +08:00
|
|
|
def_bool y if NEW_LEDS
|
2006-12-07 09:14:03 +08:00
|
|
|
depends on OMAP_DEBUG_DEVICES
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select LEDS_CLASS
|
2006-12-07 09:14:03 +08:00
|
|
|
|
2012-04-24 14:08:50 +08:00
|
|
|
config POWER_AVS_OMAP
|
|
|
|
|
bool "AVS(Adaptive Voltage Scaling) support for OMAP IP versions 1&2"
|
2012-04-25 19:13:17 +08:00
|
|
|
depends on POWER_AVS && (ARCH_OMAP3 || ARCH_OMAP4) && PM
|
2012-09-20 22:36:56 +08:00
|
|
|
select POWER_SUPPLY
|
OMAP3: PM: Adding smartreflex driver support.
SmartReflex modules do adaptive voltage control for real-time
voltage adjustments. With Smartreflex the power supply voltage
can be adapted to the silicon performance(manufacturing process,
temperature induced performance, age induced performance etc).
There are differnet classes of smartreflex implementation.
Class-0: Manufacturing Test Calibration
Class-1: Boot-Time Software Calibration
Class-2: Continuous Software Calibration
Class-3: Continuous Hardware Calibration
Class-4: Fully Integrated Power Management
OMAP3 has two smartreflex modules one associated with VDD MPU and the
other associated with VDD CORE.
This patch adds support for smartreflex driver. The driver is designed
for Class-1 , Class-2 and Class-3 support and is a platform driver.
Smartreflex driver can be enabled through a Kconfig option
"SmartReflex support" under "System type"->"TI OMAP implementations" menu.
Smartreflex autocompensation feature can be enabled runtime through
a debug fs option.
To enable smartreflex autocompensation feature
echo 1 > /debug/voltage/vdd_<X>/smartreflex/autocomp
To disable smartreflex autocompensation feature
echo 0 > /debug/voltage/vdd_<X>/smartreflex/autocomp
where X can be mpu, core , iva etc.
This patch contains code originally in linux omap pm branch.
Major contributors to this driver are
Lesly A M, Rajendra Nayak, Kalle Jokiniemi, Paul Walmsley,
Nishant Menon, Kevin Hilman.
Signed-off-by: Thara Gopinath <thara@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
2010-05-30 00:32:22 +08:00
|
|
|
help
|
2012-04-25 19:13:17 +08:00
|
|
|
Say Y to enable AVS(Adaptive Voltage Scaling)
|
|
|
|
|
support on OMAP containing the version 1 or
|
2012-04-24 14:08:50 +08:00
|
|
|
version 2 of the SmartReflex IP.
|
|
|
|
|
V1 is the 65nm version used in OMAP3430.
|
|
|
|
|
V2 is the update for the 45nm version of the IP used in OMAP3630
|
|
|
|
|
and OMAP4430
|
OMAP3: PM: Adding smartreflex driver support.
SmartReflex modules do adaptive voltage control for real-time
voltage adjustments. With Smartreflex the power supply voltage
can be adapted to the silicon performance(manufacturing process,
temperature induced performance, age induced performance etc).
There are differnet classes of smartreflex implementation.
Class-0: Manufacturing Test Calibration
Class-1: Boot-Time Software Calibration
Class-2: Continuous Software Calibration
Class-3: Continuous Hardware Calibration
Class-4: Fully Integrated Power Management
OMAP3 has two smartreflex modules one associated with VDD MPU and the
other associated with VDD CORE.
This patch adds support for smartreflex driver. The driver is designed
for Class-1 , Class-2 and Class-3 support and is a platform driver.
Smartreflex driver can be enabled through a Kconfig option
"SmartReflex support" under "System type"->"TI OMAP implementations" menu.
Smartreflex autocompensation feature can be enabled runtime through
a debug fs option.
To enable smartreflex autocompensation feature
echo 1 > /debug/voltage/vdd_<X>/smartreflex/autocomp
To disable smartreflex autocompensation feature
echo 0 > /debug/voltage/vdd_<X>/smartreflex/autocomp
where X can be mpu, core , iva etc.
This patch contains code originally in linux omap pm branch.
Major contributors to this driver are
Lesly A M, Rajendra Nayak, Kalle Jokiniemi, Paul Walmsley,
Nishant Menon, Kevin Hilman.
Signed-off-by: Thara Gopinath <thara@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
2010-05-30 00:32:22 +08:00
|
|
|
|
|
|
|
|
Please note, that by default SmartReflex is only
|
2012-04-24 14:08:50 +08:00
|
|
|
initialized and not enabled. To enable the automatic voltage
|
|
|
|
|
compensation for vdd mpu and vdd core from user space,
|
OMAP3: PM: Adding smartreflex driver support.
SmartReflex modules do adaptive voltage control for real-time
voltage adjustments. With Smartreflex the power supply voltage
can be adapted to the silicon performance(manufacturing process,
temperature induced performance, age induced performance etc).
There are differnet classes of smartreflex implementation.
Class-0: Manufacturing Test Calibration
Class-1: Boot-Time Software Calibration
Class-2: Continuous Software Calibration
Class-3: Continuous Hardware Calibration
Class-4: Fully Integrated Power Management
OMAP3 has two smartreflex modules one associated with VDD MPU and the
other associated with VDD CORE.
This patch adds support for smartreflex driver. The driver is designed
for Class-1 , Class-2 and Class-3 support and is a platform driver.
Smartreflex driver can be enabled through a Kconfig option
"SmartReflex support" under "System type"->"TI OMAP implementations" menu.
Smartreflex autocompensation feature can be enabled runtime through
a debug fs option.
To enable smartreflex autocompensation feature
echo 1 > /debug/voltage/vdd_<X>/smartreflex/autocomp
To disable smartreflex autocompensation feature
echo 0 > /debug/voltage/vdd_<X>/smartreflex/autocomp
where X can be mpu, core , iva etc.
This patch contains code originally in linux omap pm branch.
Major contributors to this driver are
Lesly A M, Rajendra Nayak, Kalle Jokiniemi, Paul Walmsley,
Nishant Menon, Kevin Hilman.
Signed-off-by: Thara Gopinath <thara@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
2010-05-30 00:32:22 +08:00
|
|
|
user must write 1 to
|
2012-04-24 14:08:50 +08:00
|
|
|
/debug/smartreflex/sr_<X>/autocomp,
|
|
|
|
|
where X is mpu_iva or core for OMAP3.
|
2011-02-25 14:09:35 +08:00
|
|
|
Optionally autocompensation can be enabled in the kernel
|
OMAP3: PM: Adding smartreflex driver support.
SmartReflex modules do adaptive voltage control for real-time
voltage adjustments. With Smartreflex the power supply voltage
can be adapted to the silicon performance(manufacturing process,
temperature induced performance, age induced performance etc).
There are differnet classes of smartreflex implementation.
Class-0: Manufacturing Test Calibration
Class-1: Boot-Time Software Calibration
Class-2: Continuous Software Calibration
Class-3: Continuous Hardware Calibration
Class-4: Fully Integrated Power Management
OMAP3 has two smartreflex modules one associated with VDD MPU and the
other associated with VDD CORE.
This patch adds support for smartreflex driver. The driver is designed
for Class-1 , Class-2 and Class-3 support and is a platform driver.
Smartreflex driver can be enabled through a Kconfig option
"SmartReflex support" under "System type"->"TI OMAP implementations" menu.
Smartreflex autocompensation feature can be enabled runtime through
a debug fs option.
To enable smartreflex autocompensation feature
echo 1 > /debug/voltage/vdd_<X>/smartreflex/autocomp
To disable smartreflex autocompensation feature
echo 0 > /debug/voltage/vdd_<X>/smartreflex/autocomp
where X can be mpu, core , iva etc.
This patch contains code originally in linux omap pm branch.
Major contributors to this driver are
Lesly A M, Rajendra Nayak, Kalle Jokiniemi, Paul Walmsley,
Nishant Menon, Kevin Hilman.
Signed-off-by: Thara Gopinath <thara@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
2010-05-30 00:32:22 +08:00
|
|
|
by default during system init via the enable_on_init flag
|
|
|
|
|
which an be passed as platform data to the smartreflex driver.
|
|
|
|
|
|
2012-04-24 14:08:50 +08:00
|
|
|
config POWER_AVS_OMAP_CLASS3
|
2010-05-30 00:32:25 +08:00
|
|
|
bool "Class 3 mode of Smartreflex Implementation"
|
2012-04-24 14:08:50 +08:00
|
|
|
depends on POWER_AVS_OMAP && TWL4030_CORE
|
2010-05-30 00:32:25 +08:00
|
|
|
help
|
|
|
|
|
Say Y to enable Class 3 implementation of Smartreflex
|
|
|
|
|
|
|
|
|
|
Class 3 implementation of Smartreflex employs continuous hardware
|
|
|
|
|
voltage calibration.
|
|
|
|
|
|
2005-07-11 02:58:18 +08:00
|
|
|
config OMAP_RESET_CLOCKS
|
|
|
|
|
bool "Reset unused clocks during boot"
|
|
|
|
|
depends on ARCH_OMAP
|
|
|
|
|
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.
|
|
|
|
|
|
2005-07-11 02:58:15 +08:00
|
|
|
config OMAP_MPU_TIMER
|
|
|
|
|
bool "Use mpu timer"
|
2011-01-19 04:42:23 +08:00
|
|
|
depends on ARCH_OMAP1
|
2005-07-11 02:58:15 +08:00
|
|
|
help
|
|
|
|
|
Select this option if you want to use the OMAP mpu timer. This
|
|
|
|
|
timer provides more intra-tick resolution than the 32KHz timer,
|
|
|
|
|
but consumes more power.
|
|
|
|
|
|
|
|
|
|
config OMAP_32K_TIMER
|
|
|
|
|
bool "Use 32KHz timer"
|
2010-02-13 04:26:48 +08:00
|
|
|
depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS
|
2011-01-19 04:42:23 +08:00
|
|
|
default y if (ARCH_OMAP16XX || ARCH_OMAP2PLUS)
|
2005-07-11 02:58:15 +08:00
|
|
|
help
|
|
|
|
|
Select this option if you want to enable the OMAP 32KHz timer.
|
|
|
|
|
This timer saves power compared to the OMAP_MPU_TIMER, and has
|
|
|
|
|
support for no tick during idle. The 32KHz timer provides less
|
|
|
|
|
intra-tick resolution than OMAP_MPU_TIMER. The 32KHz timer is
|
2013-02-07 18:51:46 +08:00
|
|
|
currently only available for OMAP16XX, 24XX, 34XX, OMAP4/5 and DRA7XX.
|
2005-07-11 02:58:15 +08:00
|
|
|
|
2012-11-20 15:17:15 +08:00
|
|
|
On OMAP2PLUS this value is only used for CONFIG_HZ and
|
|
|
|
|
CLOCK_TICK_RATE compile time calculation.
|
|
|
|
|
The actual timer selection is done in the board file
|
|
|
|
|
through the (DT_)MACHINE_START structure.
|
|
|
|
|
|
|
|
|
|
|
2009-11-12 18:07:22 +08:00
|
|
|
config OMAP3_L2_AUX_SECURE_SAVE_RESTORE
|
|
|
|
|
bool "OMAP3 HS/EMU save and restore for L2 AUX control register"
|
|
|
|
|
depends on ARCH_OMAP3 && PM
|
|
|
|
|
help
|
|
|
|
|
Without this option, L2 Auxiliary control register contents are
|
|
|
|
|
lost during off-mode entry on HS/EMU devices. This feature
|
|
|
|
|
requires support from PPA / boot-loader in HS/EMU devices, which
|
|
|
|
|
currently does not exist by default.
|
|
|
|
|
|
|
|
|
|
config OMAP3_L2_AUX_SECURE_SERVICE_SET_ID
|
|
|
|
|
int "Service ID for the support routine to set L2 AUX control"
|
|
|
|
|
depends on OMAP3_L2_AUX_SECURE_SAVE_RESTORE
|
|
|
|
|
default 43
|
|
|
|
|
help
|
|
|
|
|
PPA routine service ID for setting L2 auxiliary control register.
|
|
|
|
|
|
2005-09-08 00:20:26 +08:00
|
|
|
config OMAP_SERIAL_WAKE
|
|
|
|
|
bool "Enable wake-up events for serial ports"
|
2009-05-29 01:56:16 +08:00
|
|
|
depends on ARCH_OMAP1 && OMAP_MUX
|
2005-09-08 00:20:26 +08:00
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Select this option if you want to have your system wake up
|
|
|
|
|
to data on the serial RX line. This allows you to wake the
|
|
|
|
|
system from serial console.
|
|
|
|
|
|
2005-07-11 02:58:15 +08:00
|
|
|
endmenu
|
|
|
|
|
|
|
|
|
|
endif
|