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 08:07:57 -06:00
|
|
|
# SPDX-License-Identifier: GPL-2.0
|
2005-04-16 16:20:36 -06:00
|
|
|
# CPUfreq core
|
2013-10-03 08:59:08 -06:00
|
|
|
obj-$(CONFIG_CPU_FREQ) += cpufreq.o freq_table.o
|
2014-05-05 07:33:50 -06:00
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
# CPUfreq stats
|
|
|
|
|
obj-$(CONFIG_CPU_FREQ_STAT) += cpufreq_stats.o
|
|
|
|
|
|
|
|
|
|
# CPUfreq governors
|
|
|
|
|
obj-$(CONFIG_CPU_FREQ_GOV_PERFORMANCE) += cpufreq_performance.o
|
|
|
|
|
obj-$(CONFIG_CPU_FREQ_GOV_POWERSAVE) += cpufreq_powersave.o
|
|
|
|
|
obj-$(CONFIG_CPU_FREQ_GOV_USERSPACE) += cpufreq_userspace.o
|
2012-12-28 18:55:20 -07:00
|
|
|
obj-$(CONFIG_CPU_FREQ_GOV_ONDEMAND) += cpufreq_ondemand.o
|
|
|
|
|
obj-$(CONFIG_CPU_FREQ_GOV_CONSERVATIVE) += cpufreq_conservative.o
|
cpufreq: Add android's 'interactive' governor
Interactive governor has lived in Android sources for a very long time
and this commit is based on the code present in following branch:
https://android.googlesource.com/kernel/common android-4.4
The Interactive governor is designed for latency-sensitive workloads,
such as interactive user interfaces like the mobile phones and tablets.
The interactive governor aims to be significantly more responsive to
ramp CPU quickly up when CPU-intensive activity begins.
Existing governors sample CPU load at a particular rate, typically every
X ms and then update the frequency from a work-handler. This can lead
to under-powering UI threads for the period of time during which the
user begins interacting with a previously-idle system until the next
sample period happens.
The 'interactive' governor uses a different approach.
A real-time thread is used for scaling up, giving the remaining tasks
the CPU performance benefit, unlike existing governors which are more
likely to schedule ramp-up work to occur after your performance starved
tasks have completed.
The Android version of interactive governor also checks whether to scale
the CPU frequency up soon after coming out of idle. When the CPU comes
out of idle, the governor check if the CPU sampling is overdue or not.
If yes, it immediately starts the sampling. Otherwise, the utilization
hooks from the scheduler handle the sampling later. If the CPU is very
busy from exiting idle to when the evaluation happens, then it assumes
that the CPU is under-powered and ramps it to MAX speed.
If the CPU was not sufficiently busy to immediately ramp to MAX speed,
then the governor evaluates the CPU load since the last speed
adjustment, choosing the highest value between that longer-term load or
the short-term load since idle exit to determine the CPU speed to ramp
to.
Idle notifiers will be be handled later and are not included for now.
The core of this code is written and maintained (in Android
repositories) by Mike Chan and Todd Poyner over a long period of time.
Vireshk has made changes to to the governor to align it with the current
practices followed with mainline governors, like using utilization hooks
from the scheduler and handling kobject (for governor's sysfs directory)
in a race free manner. And of course this included general cleanup of
the governor as well.
Signed-off-by: Mike Chan <mike@android.com>
Signed-off-by: Todd Poynor <toddpoynor@google.com>
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
2016-05-17 03:11:22 -06:00
|
|
|
obj-$(CONFIG_CPU_FREQ_GOV_INTERACTIVE) += cpufreq_interactive.o
|
2012-12-28 18:55:20 -07:00
|
|
|
obj-$(CONFIG_CPU_FREQ_GOV_COMMON) += cpufreq_governor.o
|
2016-03-21 19:49:15 -06:00
|
|
|
obj-$(CONFIG_CPU_FREQ_GOV_ATTR_SET) += cpufreq_governor_attr_set.o
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2014-09-09 08:28:03 -06:00
|
|
|
obj-$(CONFIG_CPUFREQ_DT) += cpufreq-dt.o
|
2016-03-30 02:15:26 -06:00
|
|
|
obj-$(CONFIG_CPUFREQ_DT_PLATDEV) += cpufreq-dt-platdev.o
|
2012-09-06 01:09:11 -06:00
|
|
|
|
2011-06-06 19:10:04 -06:00
|
|
|
##################################################################################
|
2011-05-19 16:51:07 -06:00
|
|
|
# x86 drivers.
|
|
|
|
|
# Link order matters. K8 is preferred to ACPI because of firmware bugs in early
|
2013-01-20 03:24:27 -07:00
|
|
|
# K8 systems. This is still the case but acpi-cpufreq errors out so that
|
|
|
|
|
# powernow-k8 can load then. ACPI is preferred to all other hardware-specific drivers.
|
2011-05-19 16:51:07 -06:00
|
|
|
# speedstep-* is preferred over p4-clockmod.
|
|
|
|
|
|
2013-06-05 10:01:42 -06:00
|
|
|
obj-$(CONFIG_X86_ACPI_CPUFREQ) += acpi-cpufreq.o
|
2013-01-20 03:24:27 -07:00
|
|
|
obj-$(CONFIG_X86_POWERNOW_K8) += powernow-k8.o
|
2011-05-19 16:51:07 -06:00
|
|
|
obj-$(CONFIG_X86_PCC_CPUFREQ) += pcc-cpufreq.o
|
|
|
|
|
obj-$(CONFIG_X86_POWERNOW_K6) += powernow-k6.o
|
|
|
|
|
obj-$(CONFIG_X86_POWERNOW_K7) += powernow-k7.o
|
|
|
|
|
obj-$(CONFIG_X86_LONGHAUL) += longhaul.o
|
|
|
|
|
obj-$(CONFIG_X86_E_POWERSAVER) += e_powersaver.o
|
|
|
|
|
obj-$(CONFIG_ELAN_CPUFREQ) += elanfreq.o
|
|
|
|
|
obj-$(CONFIG_SC520_CPUFREQ) += sc520_freq.o
|
|
|
|
|
obj-$(CONFIG_X86_LONGRUN) += longrun.o
|
|
|
|
|
obj-$(CONFIG_X86_GX_SUSPMOD) += gx-suspmod.o
|
|
|
|
|
obj-$(CONFIG_X86_SPEEDSTEP_ICH) += speedstep-ich.o
|
|
|
|
|
obj-$(CONFIG_X86_SPEEDSTEP_LIB) += speedstep-lib.o
|
|
|
|
|
obj-$(CONFIG_X86_SPEEDSTEP_SMI) += speedstep-smi.o
|
|
|
|
|
obj-$(CONFIG_X86_SPEEDSTEP_CENTRINO) += speedstep-centrino.o
|
|
|
|
|
obj-$(CONFIG_X86_P4_CLOCKMOD) += p4-clockmod.o
|
|
|
|
|
obj-$(CONFIG_X86_CPUFREQ_NFORCE2) += cpufreq-nforce2.o
|
2013-02-06 10:02:13 -07:00
|
|
|
obj-$(CONFIG_X86_INTEL_PSTATE) += intel_pstate.o
|
2013-04-04 10:19:04 -06:00
|
|
|
obj-$(CONFIG_X86_AMD_FREQ_SENSITIVITY) += amd_freq_sensitivity.o
|
2014-12-19 10:43:51 -07:00
|
|
|
obj-$(CONFIG_X86_SFI_CPUFREQ) += sfi-cpufreq.o
|
2011-05-19 16:51:07 -06:00
|
|
|
|
2011-06-06 19:10:04 -06:00
|
|
|
##################################################################################
|
2011-05-15 11:34:29 -06:00
|
|
|
# ARM SoC drivers
|
2013-04-01 06:57:49 -06:00
|
|
|
obj-$(CONFIG_ARM_BIG_LITTLE_CPUFREQ) += arm_big_little.o
|
|
|
|
|
# big LITTLE per platform glues. Keep DT_BL_CPUFREQ as the last entry in all big
|
|
|
|
|
# LITTLE drivers, so that it is probed last.
|
|
|
|
|
obj-$(CONFIG_ARM_DT_BL_CPUFREQ) += arm_big_little_dt.o
|
|
|
|
|
|
2016-10-27 15:05:35 -06:00
|
|
|
obj-$(CONFIG_ARM_BRCMSTB_AVS_CPUFREQ) += brcmstb-avs-cpufreq.o
|
2014-07-08 09:25:38 -06:00
|
|
|
obj-$(CONFIG_ARCH_DAVINCI) += davinci-cpufreq.o
|
2013-04-08 03:57:34 -06:00
|
|
|
obj-$(CONFIG_ARM_EXYNOS5440_CPUFREQ) += exynos5440-cpufreq.o
|
2013-04-04 06:54:09 -06:00
|
|
|
obj-$(CONFIG_ARM_HIGHBANK_CPUFREQ) += highbank-cpufreq.o
|
|
|
|
|
obj-$(CONFIG_ARM_IMX6Q_CPUFREQ) += imx6q-cpufreq.o
|
2013-02-05 14:52:51 -07:00
|
|
|
obj-$(CONFIG_ARM_KIRKWOOD_CPUFREQ) += kirkwood-cpufreq.o
|
2017-07-18 00:01:43 -06:00
|
|
|
obj-$(CONFIG_ARM_MEDIATEK_CPUFREQ) += mediatek-cpufreq.o
|
2013-01-28 09:13:15 -07:00
|
|
|
obj-$(CONFIG_ARM_OMAP2PLUS_CPUFREQ) += omap-cpufreq.o
|
2014-11-23 20:59:26 -07:00
|
|
|
obj-$(CONFIG_ARM_PXA2xx_CPUFREQ) += pxa2xx-cpufreq.o
|
2013-04-04 06:54:12 -06:00
|
|
|
obj-$(CONFIG_PXA3xx) += pxa3xx-cpufreq.o
|
2013-04-04 06:54:15 -06:00
|
|
|
obj-$(CONFIG_ARM_S3C24XX_CPUFREQ) += s3c24xx-cpufreq.o
|
|
|
|
|
obj-$(CONFIG_ARM_S3C24XX_CPUFREQ_DEBUGFS) += s3c24xx-cpufreq-debugfs.o
|
|
|
|
|
obj-$(CONFIG_ARM_S3C2410_CPUFREQ) += s3c2410-cpufreq.o
|
|
|
|
|
obj-$(CONFIG_ARM_S3C2412_CPUFREQ) += s3c2412-cpufreq.o
|
2013-04-04 06:54:09 -06:00
|
|
|
obj-$(CONFIG_ARM_S3C2416_CPUFREQ) += s3c2416-cpufreq.o
|
2013-04-04 06:54:15 -06:00
|
|
|
obj-$(CONFIG_ARM_S3C2440_CPUFREQ) += s3c2440-cpufreq.o
|
2013-04-04 06:54:09 -06:00
|
|
|
obj-$(CONFIG_ARM_S3C64XX_CPUFREQ) += s3c64xx-cpufreq.o
|
|
|
|
|
obj-$(CONFIG_ARM_S5PV210_CPUFREQ) += s5pv210-cpufreq.o
|
2013-04-04 06:54:16 -06:00
|
|
|
obj-$(CONFIG_ARM_SA1100_CPUFREQ) += sa1100-cpufreq.o
|
|
|
|
|
obj-$(CONFIG_ARM_SA1110_CPUFREQ) += sa1110-cpufreq.o
|
2015-03-30 03:59:52 -06:00
|
|
|
obj-$(CONFIG_ARM_SCPI_CPUFREQ) += scpi-cpufreq.o
|
2012-11-27 06:05:26 -07:00
|
|
|
obj-$(CONFIG_ARM_SPEAR_CPUFREQ) += spear-cpufreq.o
|
2015-12-10 02:42:16 -07:00
|
|
|
obj-$(CONFIG_ARM_STI_CPUFREQ) += sti-cpufreq.o
|
2017-07-18 10:48:39 -06:00
|
|
|
obj-$(CONFIG_ARM_TANGO_CPUFREQ) += tango-cpufreq.o
|
2015-05-13 08:58:47 -06:00
|
|
|
obj-$(CONFIG_ARM_TEGRA20_CPUFREQ) += tegra20-cpufreq.o
|
2015-05-13 08:58:48 -06:00
|
|
|
obj-$(CONFIG_ARM_TEGRA124_CPUFREQ) += tegra124-cpufreq.o
|
2017-04-11 02:09:15 -06:00
|
|
|
obj-$(CONFIG_ARM_TEGRA186_CPUFREQ) += tegra186-cpufreq.o
|
2017-02-03 10:29:28 -07:00
|
|
|
obj-$(CONFIG_ARM_TI_CPUFREQ) += ti-cpufreq.o
|
2013-10-29 06:18:39 -06:00
|
|
|
obj-$(CONFIG_ARM_VEXPRESS_SPC_CPUFREQ) += vexpress-spc-cpufreq.o
|
2015-10-02 08:04:01 -06:00
|
|
|
obj-$(CONFIG_ACPI_CPPC_CPUFREQ) += cppc_cpufreq.o
|
2016-04-26 21:22:27 -06:00
|
|
|
obj-$(CONFIG_MACH_MVEBU_V7) += mvebu-cpufreq.o
|
2015-10-02 08:04:01 -06:00
|
|
|
|
2011-06-28 23:07:56 -06:00
|
|
|
|
2011-07-25 23:59:39 -06:00
|
|
|
##################################################################################
|
2011-06-28 23:07:56 -06:00
|
|
|
# PowerPC platform drivers
|
2013-03-24 23:50:23 -06:00
|
|
|
obj-$(CONFIG_CPU_FREQ_CBE) += ppc-cbe-cpufreq.o
|
|
|
|
|
ppc-cbe-cpufreq-y += ppc_cbe_cpufreq_pervasive.o ppc_cbe_cpufreq.o
|
|
|
|
|
obj-$(CONFIG_CPU_FREQ_CBE_PMI) += ppc_cbe_cpufreq_pmi.o
|
2011-06-28 23:07:56 -06:00
|
|
|
obj-$(CONFIG_CPU_FREQ_MAPLE) += maple-cpufreq.o
|
2015-03-12 22:39:02 -06:00
|
|
|
obj-$(CONFIG_QORIQ_CPUFREQ) += qoriq-cpufreq.o
|
2013-04-04 06:54:25 -06:00
|
|
|
obj-$(CONFIG_CPU_FREQ_PMAC) += pmac32-cpufreq.o
|
|
|
|
|
obj-$(CONFIG_CPU_FREQ_PMAC64) += pmac64-cpufreq.o
|
|
|
|
|
obj-$(CONFIG_PPC_PASEMI_CPUFREQ) += pasemi-cpufreq.o
|
2014-04-01 01:13:26 -06:00
|
|
|
obj-$(CONFIG_POWERNV_CPUFREQ) += powernv-cpufreq.o
|
2013-04-04 06:54:17 -06:00
|
|
|
|
|
|
|
|
##################################################################################
|
|
|
|
|
# Other platform drivers
|
|
|
|
|
obj-$(CONFIG_AVR32_AT32AP_CPUFREQ) += at32ap-cpufreq.o
|
2013-06-12 00:02:00 -06:00
|
|
|
obj-$(CONFIG_BFIN_CPU_FREQ) += blackfin-cpufreq.o
|
2017-02-07 14:58:55 -07:00
|
|
|
obj-$(CONFIG_BMIPS_CPUFREQ) += bmips-cpufreq.o
|
2013-04-04 06:54:19 -06:00
|
|
|
obj-$(CONFIG_CRIS_MACH_ARTPEC3) += cris-artpec3-cpufreq.o
|
|
|
|
|
obj-$(CONFIG_ETRAXFS) += cris-etraxfs-cpufreq.o
|
2013-04-04 06:54:20 -06:00
|
|
|
obj-$(CONFIG_IA64_ACPI_CPUFREQ) += ia64-acpi-cpufreq.o
|
2013-04-04 06:54:21 -06:00
|
|
|
obj-$(CONFIG_LOONGSON2_CPUFREQ) += loongson2_cpufreq.o
|
2016-04-12 04:40:15 -06:00
|
|
|
obj-$(CONFIG_LOONGSON1_CPUFREQ) += loongson1-cpufreq.o
|
2013-04-04 06:54:22 -06:00
|
|
|
obj-$(CONFIG_SH_CPU_FREQ) += sh-cpufreq.o
|
2013-04-04 06:54:24 -06:00
|
|
|
obj-$(CONFIG_SPARC_US2E_CPUFREQ) += sparc-us2e-cpufreq.o
|
|
|
|
|
obj-$(CONFIG_SPARC_US3_CPUFREQ) += sparc-us3-cpufreq.o
|
2013-04-04 06:54:23 -06:00
|
|
|
obj-$(CONFIG_UNICORE32) += unicore2-cpufreq.o
|