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 */
|
drivers/base: provide an infrastructure for componentised subsystems
Subsystems such as ALSA, DRM and others require a single card-level
device structure to represent a subsystem. However, firmware tends to
describe the individual devices and the connections between them.
Therefore, we need a way to gather up the individual component devices
together, and indicate when we have all the component devices.
We do this in DT by providing a "superdevice" node which specifies
the components, eg:
imx-drm {
compatible = "fsl,drm";
crtcs = <&ipu1>;
connectors = <&hdmi>;
};
The superdevice is declared into the component support, along with the
subcomponents. The superdevice receives callbacks to locate the
subcomponents, and identify when all components are present. At this
point, we bind the superdevice, which causes the appropriate subsystem
to be initialised in the conventional way.
When any of the components or superdevice are removed from the system,
we unbind the superdevice, thereby taking the subsystem down.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2014-01-11 07:23:37 +08:00
|
|
|
#ifndef COMPONENT_H
|
|
|
|
|
#define COMPONENT_H
|
|
|
|
|
|
2015-11-17 20:08:01 +08:00
|
|
|
#include <linux/stddef.h>
|
|
|
|
|
|
2019-02-08 07:27:56 +08:00
|
|
|
|
drivers/base: provide an infrastructure for componentised subsystems
Subsystems such as ALSA, DRM and others require a single card-level
device structure to represent a subsystem. However, firmware tends to
describe the individual devices and the connections between them.
Therefore, we need a way to gather up the individual component devices
together, and indicate when we have all the component devices.
We do this in DT by providing a "superdevice" node which specifies
the components, eg:
imx-drm {
compatible = "fsl,drm";
crtcs = <&ipu1>;
connectors = <&hdmi>;
};
The superdevice is declared into the component support, along with the
subcomponents. The superdevice receives callbacks to locate the
subcomponents, and identify when all components are present. At this
point, we bind the superdevice, which causes the appropriate subsystem
to be initialised in the conventional way.
When any of the components or superdevice are removed from the system,
we unbind the superdevice, thereby taking the subsystem down.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2014-01-11 07:23:37 +08:00
|
|
|
struct device;
|
|
|
|
|
|
2019-02-08 07:27:56 +08:00
|
|
|
/**
|
|
|
|
|
* struct component_ops - callbacks for component drivers
|
|
|
|
|
*
|
|
|
|
|
* Components are registered with component_add() and unregistered with
|
|
|
|
|
* component_del().
|
|
|
|
|
*/
|
drivers/base: provide an infrastructure for componentised subsystems
Subsystems such as ALSA, DRM and others require a single card-level
device structure to represent a subsystem. However, firmware tends to
describe the individual devices and the connections between them.
Therefore, we need a way to gather up the individual component devices
together, and indicate when we have all the component devices.
We do this in DT by providing a "superdevice" node which specifies
the components, eg:
imx-drm {
compatible = "fsl,drm";
crtcs = <&ipu1>;
connectors = <&hdmi>;
};
The superdevice is declared into the component support, along with the
subcomponents. The superdevice receives callbacks to locate the
subcomponents, and identify when all components are present. At this
point, we bind the superdevice, which causes the appropriate subsystem
to be initialised in the conventional way.
When any of the components or superdevice are removed from the system,
we unbind the superdevice, thereby taking the subsystem down.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2014-01-11 07:23:37 +08:00
|
|
|
struct component_ops {
|
2019-02-08 07:27:56 +08:00
|
|
|
/**
|
|
|
|
|
* @bind:
|
|
|
|
|
*
|
|
|
|
|
* Called through component_bind_all() when the aggregate driver is
|
|
|
|
|
* ready to bind the overall driver.
|
|
|
|
|
*/
|
2015-11-17 20:08:01 +08:00
|
|
|
int (*bind)(struct device *comp, struct device *master,
|
|
|
|
|
void *master_data);
|
2019-02-08 07:27:56 +08:00
|
|
|
/**
|
|
|
|
|
* @unbind:
|
|
|
|
|
*
|
|
|
|
|
* Called through component_unbind_all() when the aggregate driver is
|
|
|
|
|
* ready to bind the overall driver, or when component_bind_all() fails
|
|
|
|
|
* part-ways through and needs to unbind some already bound components.
|
|
|
|
|
*/
|
2015-11-17 20:08:01 +08:00
|
|
|
void (*unbind)(struct device *comp, struct device *master,
|
|
|
|
|
void *master_data);
|
drivers/base: provide an infrastructure for componentised subsystems
Subsystems such as ALSA, DRM and others require a single card-level
device structure to represent a subsystem. However, firmware tends to
describe the individual devices and the connections between them.
Therefore, we need a way to gather up the individual component devices
together, and indicate when we have all the component devices.
We do this in DT by providing a "superdevice" node which specifies
the components, eg:
imx-drm {
compatible = "fsl,drm";
crtcs = <&ipu1>;
connectors = <&hdmi>;
};
The superdevice is declared into the component support, along with the
subcomponents. The superdevice receives callbacks to locate the
subcomponents, and identify when all components are present. At this
point, we bind the superdevice, which causes the appropriate subsystem
to be initialised in the conventional way.
When any of the components or superdevice are removed from the system,
we unbind the superdevice, thereby taking the subsystem down.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2014-01-11 07:23:37 +08:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
int component_add(struct device *, const struct component_ops *);
|
2019-02-08 07:27:57 +08:00
|
|
|
int component_add_typed(struct device *dev, const struct component_ops *ops,
|
|
|
|
|
int subcomponent);
|
drivers/base: provide an infrastructure for componentised subsystems
Subsystems such as ALSA, DRM and others require a single card-level
device structure to represent a subsystem. However, firmware tends to
describe the individual devices and the connections between them.
Therefore, we need a way to gather up the individual component devices
together, and indicate when we have all the component devices.
We do this in DT by providing a "superdevice" node which specifies
the components, eg:
imx-drm {
compatible = "fsl,drm";
crtcs = <&ipu1>;
connectors = <&hdmi>;
};
The superdevice is declared into the component support, along with the
subcomponents. The superdevice receives callbacks to locate the
subcomponents, and identify when all components are present. At this
point, we bind the superdevice, which causes the appropriate subsystem
to be initialised in the conventional way.
When any of the components or superdevice are removed from the system,
we unbind the superdevice, thereby taking the subsystem down.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2014-01-11 07:23:37 +08:00
|
|
|
void component_del(struct device *, const struct component_ops *);
|
|
|
|
|
|
2015-11-17 20:08:01 +08:00
|
|
|
int component_bind_all(struct device *master, void *master_data);
|
|
|
|
|
void component_unbind_all(struct device *master, void *master_data);
|
drivers/base: provide an infrastructure for componentised subsystems
Subsystems such as ALSA, DRM and others require a single card-level
device structure to represent a subsystem. However, firmware tends to
describe the individual devices and the connections between them.
Therefore, we need a way to gather up the individual component devices
together, and indicate when we have all the component devices.
We do this in DT by providing a "superdevice" node which specifies
the components, eg:
imx-drm {
compatible = "fsl,drm";
crtcs = <&ipu1>;
connectors = <&hdmi>;
};
The superdevice is declared into the component support, along with the
subcomponents. The superdevice receives callbacks to locate the
subcomponents, and identify when all components are present. At this
point, we bind the superdevice, which causes the appropriate subsystem
to be initialised in the conventional way.
When any of the components or superdevice are removed from the system,
we unbind the superdevice, thereby taking the subsystem down.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2014-01-11 07:23:37 +08:00
|
|
|
|
|
|
|
|
struct master;
|
|
|
|
|
|
2019-02-08 07:27:56 +08:00
|
|
|
/**
|
|
|
|
|
* struct component_master_ops - callback for the aggregate driver
|
|
|
|
|
*
|
|
|
|
|
* Aggregate drivers are registered with component_master_add_with_match() and
|
|
|
|
|
* unregistered with component_master_del().
|
|
|
|
|
*/
|
drivers/base: provide an infrastructure for componentised subsystems
Subsystems such as ALSA, DRM and others require a single card-level
device structure to represent a subsystem. However, firmware tends to
describe the individual devices and the connections between them.
Therefore, we need a way to gather up the individual component devices
together, and indicate when we have all the component devices.
We do this in DT by providing a "superdevice" node which specifies
the components, eg:
imx-drm {
compatible = "fsl,drm";
crtcs = <&ipu1>;
connectors = <&hdmi>;
};
The superdevice is declared into the component support, along with the
subcomponents. The superdevice receives callbacks to locate the
subcomponents, and identify when all components are present. At this
point, we bind the superdevice, which causes the appropriate subsystem
to be initialised in the conventional way.
When any of the components or superdevice are removed from the system,
we unbind the superdevice, thereby taking the subsystem down.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2014-01-11 07:23:37 +08:00
|
|
|
struct component_master_ops {
|
2019-02-08 07:27:56 +08:00
|
|
|
/**
|
|
|
|
|
* @bind:
|
|
|
|
|
*
|
|
|
|
|
* Called when all components or the aggregate driver, as specified in
|
|
|
|
|
* the match list passed to component_master_add_with_match(), are
|
|
|
|
|
* ready. Usually there are 3 steps to bind an aggregate driver:
|
|
|
|
|
*
|
|
|
|
|
* 1. Allocate a structure for the aggregate driver.
|
|
|
|
|
*
|
|
|
|
|
* 2. Bind all components to the aggregate driver by calling
|
|
|
|
|
* component_bind_all() with the aggregate driver structure as opaque
|
|
|
|
|
* pointer data.
|
|
|
|
|
*
|
|
|
|
|
* 3. Register the aggregate driver with the subsystem to publish its
|
|
|
|
|
* interfaces.
|
|
|
|
|
*
|
|
|
|
|
* Note that the lifetime of the aggregate driver does not align with
|
|
|
|
|
* any of the underlying &struct device instances. Therefore devm cannot
|
|
|
|
|
* be used and all resources acquired or allocated in this callback must
|
|
|
|
|
* be explicitly released in the @unbind callback.
|
|
|
|
|
*/
|
2015-11-17 20:08:01 +08:00
|
|
|
int (*bind)(struct device *master);
|
2019-02-08 07:27:56 +08:00
|
|
|
/**
|
|
|
|
|
* @unbind:
|
|
|
|
|
*
|
|
|
|
|
* Called when either the aggregate driver, using
|
|
|
|
|
* component_master_del(), or one of its components, using
|
|
|
|
|
* component_del(), is unregistered.
|
|
|
|
|
*/
|
2015-11-17 20:08:01 +08:00
|
|
|
void (*unbind)(struct device *master);
|
drivers/base: provide an infrastructure for componentised subsystems
Subsystems such as ALSA, DRM and others require a single card-level
device structure to represent a subsystem. However, firmware tends to
describe the individual devices and the connections between them.
Therefore, we need a way to gather up the individual component devices
together, and indicate when we have all the component devices.
We do this in DT by providing a "superdevice" node which specifies
the components, eg:
imx-drm {
compatible = "fsl,drm";
crtcs = <&ipu1>;
connectors = <&hdmi>;
};
The superdevice is declared into the component support, along with the
subcomponents. The superdevice receives callbacks to locate the
subcomponents, and identify when all components are present. At this
point, we bind the superdevice, which causes the appropriate subsystem
to be initialised in the conventional way.
When any of the components or superdevice are removed from the system,
we unbind the superdevice, thereby taking the subsystem down.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2014-01-11 07:23:37 +08:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
void component_master_del(struct device *,
|
|
|
|
|
const struct component_master_ops *);
|
|
|
|
|
|
2014-04-19 18:18:01 +08:00
|
|
|
struct component_match;
|
|
|
|
|
|
|
|
|
|
int component_master_add_with_match(struct device *,
|
|
|
|
|
const struct component_master_ops *, struct component_match *);
|
2015-11-17 20:08:01 +08:00
|
|
|
void component_match_add_release(struct device *master,
|
|
|
|
|
struct component_match **matchptr,
|
|
|
|
|
void (*release)(struct device *, void *),
|
2014-04-19 18:18:01 +08:00
|
|
|
int (*compare)(struct device *, void *), void *compare_data);
|
2019-02-08 07:27:57 +08:00
|
|
|
void component_match_add_typed(struct device *master,
|
|
|
|
|
struct component_match **matchptr,
|
|
|
|
|
int (*compare_typed)(struct device *, int, void *), void *compare_data);
|
2014-04-19 18:18:01 +08:00
|
|
|
|
2019-02-08 07:27:56 +08:00
|
|
|
/**
|
2019-02-19 00:36:48 +08:00
|
|
|
* component_match_add - add a component match entry
|
2019-02-08 07:27:56 +08:00
|
|
|
* @master: device with the aggregate driver
|
|
|
|
|
* @matchptr: pointer to the list of component matches
|
|
|
|
|
* @compare: compare function to match against all components
|
|
|
|
|
* @compare_data: opaque pointer passed to the @compare function
|
|
|
|
|
*
|
|
|
|
|
* Adds a new component match to the list stored in @matchptr, which the @master
|
|
|
|
|
* aggregate driver needs to function. The list of component matches pointed to
|
2019-02-08 07:27:57 +08:00
|
|
|
* by @matchptr must be initialized to NULL before adding the first match. This
|
|
|
|
|
* only matches against components added with component_add().
|
2019-02-08 07:27:56 +08:00
|
|
|
*
|
|
|
|
|
* The allocated match list in @matchptr is automatically released using devm
|
|
|
|
|
* actions.
|
|
|
|
|
*
|
2019-02-08 07:27:57 +08:00
|
|
|
* See also component_match_add_release() and component_match_add_typed().
|
2019-02-08 07:27:56 +08:00
|
|
|
*/
|
2015-11-17 20:08:01 +08:00
|
|
|
static inline void component_match_add(struct device *master,
|
|
|
|
|
struct component_match **matchptr,
|
|
|
|
|
int (*compare)(struct device *, void *), void *compare_data)
|
|
|
|
|
{
|
|
|
|
|
component_match_add_release(master, matchptr, NULL, compare,
|
|
|
|
|
compare_data);
|
|
|
|
|
}
|
|
|
|
|
|
drivers/base: provide an infrastructure for componentised subsystems
Subsystems such as ALSA, DRM and others require a single card-level
device structure to represent a subsystem. However, firmware tends to
describe the individual devices and the connections between them.
Therefore, we need a way to gather up the individual component devices
together, and indicate when we have all the component devices.
We do this in DT by providing a "superdevice" node which specifies
the components, eg:
imx-drm {
compatible = "fsl,drm";
crtcs = <&ipu1>;
connectors = <&hdmi>;
};
The superdevice is declared into the component support, along with the
subcomponents. The superdevice receives callbacks to locate the
subcomponents, and identify when all components are present. At this
point, we bind the superdevice, which causes the appropriate subsystem
to be initialised in the conventional way.
When any of the components or superdevice are removed from the system,
we unbind the superdevice, thereby taking the subsystem down.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2014-01-11 07:23:37 +08:00
|
|
|
#endif
|
