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
|
2008-08-19 02:08:44 -06:00
|
|
|
/*
|
2011-09-14 16:01:21 -06:00
|
|
|
* OMAP2/3 clockdomain common data
|
2008-08-19 02:08:44 -06:00
|
|
|
*
|
2011-09-14 16:01:21 -06:00
|
|
|
* Copyright (C) 2008-2011 Texas Instruments, Inc.
|
2010-01-26 20:13:13 -07:00
|
|
|
* Copyright (C) 2008-2010 Nokia Corporation
|
2008-08-19 02:08:44 -06:00
|
|
|
*
|
2010-12-21 20:01:20 -07:00
|
|
|
* Paul Walmsley, Jouni Högander
|
2010-01-26 20:12:59 -07:00
|
|
|
*
|
|
|
|
|
* This file contains clockdomains and clockdomain wakeup/sleep
|
|
|
|
|
* dependencies for the OMAP2/3 chips. Some notes:
|
|
|
|
|
*
|
|
|
|
|
* A useful validation rule for struct clockdomain: Any clockdomain
|
|
|
|
|
* referenced by a wkdep_srcs or sleepdep_srcs array must have a
|
|
|
|
|
* dep_bit assigned. So wkdep_srcs/sleepdep_srcs are really just
|
|
|
|
|
* software-controllable dependencies. Non-software-controllable
|
|
|
|
|
* dependencies do exist, but they are not encoded below (yet).
|
|
|
|
|
*
|
|
|
|
|
* 24xx does not support programmable sleep dependencies (SLEEPDEP)
|
|
|
|
|
*
|
|
|
|
|
* The overly-specific dep_bit names are due to a bit name collision
|
|
|
|
|
* with CM_FCLKEN_{DSP,IVA2}. The DSP/IVA2 PM_WKDEP and CM_SLEEPDEP shift
|
|
|
|
|
* value are the same for all powerdomains: 2
|
|
|
|
|
*
|
|
|
|
|
* XXX should dep_bit be a mask, so we can test to see if it is 0 as a
|
|
|
|
|
* sanity check?
|
|
|
|
|
* XXX encode hardware fixed wakeup dependencies -- esp. for 3430 CORE
|
2008-08-19 02:08:44 -06:00
|
|
|
*/
|
|
|
|
|
|
2010-01-26 20:12:54 -07:00
|
|
|
/*
|
|
|
|
|
* To-Do List
|
|
|
|
|
* -> Port the Sleep/Wakeup dependencies for the domains
|
|
|
|
|
* from the Power domain framework
|
|
|
|
|
*/
|
|
|
|
|
|
2010-12-21 20:01:20 -07:00
|
|
|
#include <linux/kernel.h>
|
|
|
|
|
#include <linux/io.h>
|
2008-08-19 02:08:44 -06:00
|
|
|
|
2010-12-21 21:05:15 -07:00
|
|
|
#include "clockdomain.h"
|
2010-12-21 15:30:55 -07:00
|
|
|
#include "prm2xxx_3xxx.h"
|
|
|
|
|
#include "cm2xxx_3xxx.h"
|
2010-12-21 20:01:17 -07:00
|
|
|
#include "cm-regbits-24xx.h"
|
|
|
|
|
#include "cm-regbits-34xx.h"
|
|
|
|
|
#include "cm-regbits-44xx.h"
|
|
|
|
|
#include "prm-regbits-24xx.h"
|
|
|
|
|
#include "prm-regbits-34xx.h"
|
2008-08-19 02:08:44 -06:00
|
|
|
|
2010-01-26 20:12:59 -07:00
|
|
|
/*
|
|
|
|
|
* Clockdomain dependencies for wkdeps/sleepdeps
|
|
|
|
|
*
|
|
|
|
|
* XXX Hardware dependencies (e.g., dependencies that cannot be
|
|
|
|
|
* changed in software) are not included here yet, but should be.
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
/* Wakeup dependency source arrays */
|
|
|
|
|
|
2011-09-14 16:01:21 -06:00
|
|
|
/* 2xxx-specific possible dependencies */
|
2010-01-26 20:12:59 -07:00
|
|
|
|
2011-09-14 16:01:21 -06:00
|
|
|
/* 2xxx PM_WKDEP_GFX: CORE, MPU, WKUP */
|
|
|
|
|
struct clkdm_dep gfx_24xx_wkdeps[] = {
|
|
|
|
|
{ .clkdm_name = "core_l3_clkdm" },
|
|
|
|
|
{ .clkdm_name = "core_l4_clkdm" },
|
|
|
|
|
{ .clkdm_name = "mpu_clkdm" },
|
|
|
|
|
{ .clkdm_name = "wkup_clkdm" },
|
2010-01-26 20:12:59 -07:00
|
|
|
{ NULL },
|
|
|
|
|
};
|
|
|
|
|
|
2011-09-14 16:01:21 -06:00
|
|
|
/* 2xxx PM_WKDEP_DSP: CORE, MPU, WKUP */
|
|
|
|
|
struct clkdm_dep dsp_24xx_wkdeps[] = {
|
|
|
|
|
{ .clkdm_name = "core_l3_clkdm" },
|
|
|
|
|
{ .clkdm_name = "core_l4_clkdm" },
|
|
|
|
|
{ .clkdm_name = "mpu_clkdm" },
|
|
|
|
|
{ .clkdm_name = "wkup_clkdm" },
|
2010-01-26 20:12:59 -07:00
|
|
|
{ NULL },
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
|
2008-08-19 02:08:44 -06:00
|
|
|
/*
|
|
|
|
|
* OMAP2/3-common clockdomains
|
2008-09-10 10:47:36 -06:00
|
|
|
*
|
|
|
|
|
* Even though the 2420 has a single PRCM module from the
|
|
|
|
|
* interconnect's perspective, internally it does appear to have
|
|
|
|
|
* separate PRM and CM clockdomains. The usual test case is
|
|
|
|
|
* sys_clkout/sys_clkout2.
|
2008-08-19 02:08:44 -06:00
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
/* This is an implicit clockdomain - it is never defined as such in TRM */
|
2011-09-14 16:01:21 -06:00
|
|
|
struct clockdomain wkup_common_clkdm = {
|
2008-08-19 02:08:44 -06:00
|
|
|
.name = "wkup_clkdm",
|
2009-02-03 02:10:03 -07:00
|
|
|
.pwrdm = { .name = "wkup_pwrdm" },
|
2010-01-26 20:12:59 -07:00
|
|
|
.dep_bit = OMAP_EN_WKUP_SHIFT,
|
ARM: OMAP2+: hwmod code/clockdomain data: fix 32K sync timer
Kevin discovered that commit c8d82ff68fb6873691536cf33021977efbf5593c
("ARM: OMAP2/3: hwmod data: Add 32k-sync timer data to hwmod
database") broke CORE idle on OMAP3. This prevents device low power
states.
The root cause is that the 32K sync timer IP block does not support
smart-idle mode[1], and so the hwmod code keeps the IP block in
no-idle mode while it is active. This in turn prevents the WKUP
clockdomain from transitioning to idle. There is a hardcoded sleep
dependency that prevents the CORE_L3 and CORE_CM clockdomains from
transitioning to idle when the WKUP clockdomain is active[2], so the
chip cannot enter any device low power states.
It turns out that there is no need to take the 32k sync timer out of
idle. The IP block itself probably does not have any native idle
handling at all, due to its simplicity. Furthermore, the PRCM will
never request target idle for this IP block while the kernel is
running, due to the sleep dependency that prevents the WKUP
clockdomain from idling while the CORE_L3 clockdomain is active. So
we can safely leave the 32k sync timer in target-force-idle mode, even
while we continue to access it.
This workaround is implemented by defining a new clockdomain flag,
CLKDM_ACTIVE_WITH_MPU, that indicates that the clockdomain is
guaranteed to be active whenever the MPU is inactive. If an IP
block's main functional clock exists inside this clockdomain, and the
IP block does not support smart-idle modes, then the hwmod code will
place the IP block into target force-idle mode even when enabled. The
WKUP clockdomains on OMAP3/4 are marked with this flag. (On OMAP2xxx,
no OCP header existed on the 32k sync timer.) Other clockdomains also
should be marked with this flag, but those changes are deferred until
a later merge window, to create a minimal fix.
Another theoretically clean fix for this problem would be to implement
PM runtime-based control for 32k sync timer accesses. These PM
runtime calls would need to located in a custom clocksource, since the
32k sync timer is currently used as an MMIO clocksource. But in
practice, there would be little benefit to doing so; and there would
be some cost, due to the addition of unnecessary lines of code and the
additional CPU overhead of the PM runtime and hwmod code - unnecessary
in this case.
Another possible fix would have been to modify the pm34xx.c code to
force the IP block idle before entering WFI. But this would not have
been an acceptable approach: we are trying to remove this type of
centralized IP block idle control from the PM code.
This patch is a collaboration between Kevin Hilman <khilman@ti.com>
and Paul Walmsley <paul@pwsan.com>.
Thanks to Vaibhav Hiremath <hvaibhav@ti.com> for providing comments on
an earlier version of this patch. Thanks to Tero Kristo
<t-kristo@ti.com> for identifying a bug in an earlier version of this
patch. Thanks to Benoît Cousson <b-cousson@ti.com> for identifying
some bugs in several versions of this patch and for implementation
comments.
References:
1. Table 16-96 "REG_32KSYNCNT_SYSCONFIG" of the OMAP34xx TRM Rev. ZU
(SWPU223U), available from:
http://www.ti.com/pdfs/wtbu/OMAP34x_ES3.1.x_PUBLIC_TRM_vzU.zip
2. Table 4-72 "Sleep Dependencies" of the OMAP34xx TRM Rev. ZU
(SWPU223U)
3. ibid.
Cc: Tony Lindgren <tony@atomide.com>
Cc: Vaibhav Hiremath <hvaibhav@ti.com>
Cc: Benoît Cousson <b-cousson@ti.com>
Cc: Tero Kristo <t-kristo@ti.com>
Tested-by: Kevin Hilman <khilman@ti.com>
Signed-off-by: Paul Walmsley <paul@pwsan.com>
Signed-off-by: Kevin Hilman <khilman@ti.com>
2012-07-04 05:22:53 -06:00
|
|
|
.flags = CLKDM_ACTIVE_WITH_MPU,
|
2008-08-19 02:08:44 -06:00
|
|
|
};
|