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
|
2015-08-24 02:13:14 -06:00
|
|
|
#dmaengine debug flags
|
2014-07-14 14:47:26 -06:00
|
|
|
subdir-ccflags-$(CONFIG_DMADEVICES_DEBUG) := -DDEBUG
|
|
|
|
|
subdir-ccflags-$(CONFIG_DMADEVICES_VDEBUG) += -DVERBOSE_DEBUG
|
2010-02-09 14:34:54 -07:00
|
|
|
|
2015-08-24 02:13:14 -06:00
|
|
|
#core
|
2006-05-23 18:50:37 -06:00
|
|
|
obj-$(CONFIG_DMA_ENGINE) += dmaengine.o
|
2012-04-13 05:07:23 -06:00
|
|
|
obj-$(CONFIG_DMA_VIRTUAL_CHANNELS) += virt-dma.o
|
2013-04-09 05:05:43 -06:00
|
|
|
obj-$(CONFIG_DMA_ACPI) += acpi-dma.o
|
2013-02-12 10:15:02 -07:00
|
|
|
obj-$(CONFIG_DMA_OF) += of-dma.o
|
|
|
|
|
|
2015-08-24 02:13:14 -06:00
|
|
|
#dmatest
|
2008-07-08 12:58:45 -06:00
|
|
|
obj-$(CONFIG_DMATEST) += dmatest.o
|
2015-08-24 02:13:14 -06:00
|
|
|
|
|
|
|
|
#devices
|
2017-07-07 06:11:19 -06:00
|
|
|
obj-$(CONFIG_ALTERA_MSGDMA) += altera-msgdma.o
|
2015-08-24 02:13:14 -06:00
|
|
|
obj-$(CONFIG_AMBA_PL08X) += amba-pl08x.o
|
|
|
|
|
obj-$(CONFIG_AMCC_PPC440SPE_ADMA) += ppc4xx/
|
2009-07-03 11:24:33 -06:00
|
|
|
obj-$(CONFIG_AT_HDMAC) += at_hdmac.o
|
2014-10-22 09:22:18 -06:00
|
|
|
obj-$(CONFIG_AT_XDMAC) += at_xdmac.o
|
2015-08-24 02:13:14 -06:00
|
|
|
obj-$(CONFIG_AXI_DMAC) += dma-axi-dmac.o
|
2017-05-14 23:04:54 -06:00
|
|
|
obj-$(CONFIG_BCM_SBA_RAID) += bcm-sba-raid.o
|
2009-11-19 11:49:17 -07:00
|
|
|
obj-$(CONFIG_COH901318) += coh901318.o coh901318_lli.o
|
2015-08-24 02:13:14 -06:00
|
|
|
obj-$(CONFIG_DMA_BCM2835) += bcm2835-dma.o
|
|
|
|
|
obj-$(CONFIG_DMA_JZ4780) += dma-jz4780.o
|
|
|
|
|
obj-$(CONFIG_DMA_SA11X0) += sa11x0-dma.o
|
|
|
|
|
obj-$(CONFIG_DMA_SUN4I) += sun4i-dma.o
|
|
|
|
|
obj-$(CONFIG_DMA_SUN6I) += sun6i-dma.o
|
2018-03-06 04:46:14 -07:00
|
|
|
obj-$(CONFIG_DW_AXI_DMAC) += dw-axi-dmac/
|
2015-08-24 02:13:14 -06:00
|
|
|
obj-$(CONFIG_DW_DMAC_CORE) += dw/
|
dmaengine: Add Synopsys eDMA IP core driver
Add Synopsys PCIe Endpoint eDMA IP core driver to kernel.
This IP is generally distributed with Synopsys PCIe Endpoint IP (depends
of the use and licensing agreement).
This core driver, initializes and configures the eDMA IP using vma-helpers
functions and dma-engine subsystem.
This driver can be compile as built-in or external module in kernel.
To enable this driver just select DW_EDMA option in kernel configuration,
however it requires and selects automatically DMA_ENGINE and
DMA_VIRTUAL_CHANNELS option too.
In order to transfer data from point A to B as fast as possible this IP
requires a dedicated memory space containing linked list of elements.
All elements of this linked list are continuous and each one describes a
data transfer (source and destination addresses, length and a control
variable).
For the sake of simplicity, lets assume a memory space for channel write
0 which allows about 42 elements.
+---------+
| Desc #0 |-+
+---------+ |
V
+----------+
| Chunk #0 |-+
| CB = 1 | | +----------+ +-----+ +-----------+ +-----+
+----------+ +->| Burst #0 |->| ... |->| Burst #41 |->| llp |
| +----------+ +-----+ +-----------+ +-----+
V
+----------+
| Chunk #1 |-+
| CB = 0 | | +-----------+ +-----+ +-----------+ +-----+
+----------+ +->| Burst #42 |->| ... |->| Burst #83 |->| llp |
| +-----------+ +-----+ +-----------+ +-----+
V
+----------+
| Chunk #2 |-+
| CB = 1 | | +-----------+ +-----+ +------------+ +-----+
+----------+ +->| Burst #84 |->| ... |->| Burst #125 |->| llp |
| +-----------+ +-----+ +------------+ +-----+
V
+----------+
| Chunk #3 |-+
| CB = 0 | | +------------+ +-----+ +------------+ +-----+
+----------+ +->| Burst #126 |->| ... |->| Burst #129 |->| llp |
+------------+ +-----+ +------------+ +-----+
Legend:
- Linked list, also know as Chunk
- Linked list element*, also know as Burst *CB*, also know as Change Bit,
it's a control bit (and typically is toggled) that allows to easily
identify and differentiate between the current linked list and the
previous or the next one.
- LLP, is a special element that indicates the end of the linked list
element stream also informs that the next CB should be toggle
On every last Burst of the Chunk (Burst #41, Burst #83, Burst #125 or
even Burst #129) is set some flags on their control variable (RIE and
LIE bits) that will trigger the send of "done" interruption.
On the interruptions callback, is decided whether to recycle the linked
list memory space by writing a new set of Bursts elements (if still
exists Chunks to transfer) or is considered completed (if there is no
Chunks available to transfer).
On scatter-gather transfer mode, the client will submit a scatter-gather
list of n (on this case 130) elements, that will be divide in multiple
Chunks, each Chunk will have (on this case 42) a limited number of
Bursts and after transferring all Bursts, an interrupt will be
triggered, which will allow to recycle the all linked list dedicated
memory again with the new information relative to the next Chunk and
respective Burst associated and repeat the whole cycle again.
On cyclic transfer mode, the client will submit a buffer pointer, length
of it and number of repetitions, in this case each burst will correspond
directly to each repetition.
Each Burst can describes a data transfer from point A(source) to point
B(destination) with a length that can be from 1 byte up to 4 GB. Since
dedicated the memory space where the linked list will reside is limited,
the whole n burst elements will be organized in several Chunks, that
will be used later to recycle the dedicated memory space to initiate a
new sequence of data transfers.
The whole transfer is considered has completed when it was transferred
all bursts.
Currently this IP has a set well-known register map, which includes
support for legacy and unroll modes. Legacy mode is version of this
register map that has multiplexer register that allows to switch
registers between all write and read channels and the unroll modes
repeats all write and read channels registers with an offset between
them. This register map is called v0.
The IP team is creating a new register map more suitable to the latest
PCIe features, that very likely will change the map register, which this
version will be called v1. As soon as this new version is released by
the IP team the support for this version in be included on this driver.
According to the logic, patches 1, 2 and 3 should be squashed into 1
unique patch, but for the sake of simplicity of review, it was divided
in this 3 patches files.
Signed-off-by: Gustavo Pimentel <gustavo.pimentel@synopsys.com>
Cc: Vinod Koul <vkoul@kernel.org>
Cc: Dan Williams <dan.j.williams@intel.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Russell King <rmk+kernel@armlinux.org.uk>
Cc: Joao Pinto <jpinto@synopsys.com>
Signed-off-by: Vinod Koul <vkoul@kernel.org>
2019-06-04 07:29:22 -06:00
|
|
|
obj-$(CONFIG_DW_EDMA) += dw-edma/
|
2015-08-24 02:13:14 -06:00
|
|
|
obj-$(CONFIG_EP93XX_DMA) += ep93xx_dma.o
|
|
|
|
|
obj-$(CONFIG_FSL_DMA) += fsldma.o
|
2018-08-19 11:27:13 -06:00
|
|
|
obj-$(CONFIG_FSL_EDMA) += fsl-edma.o fsl-edma-common.o
|
2017-03-31 01:53:39 -06:00
|
|
|
obj-$(CONFIG_FSL_EDMA_V3) += fsl-edma-v3.o
|
2018-08-19 11:27:16 -06:00
|
|
|
obj-$(CONFIG_MCF_EDMA) += mcf-edma.o fsl-edma-common.o
|
2018-10-29 20:36:00 -06:00
|
|
|
obj-$(CONFIG_FSL_QDMA) += fsl-qdma.o
|
2015-08-24 02:13:14 -06:00
|
|
|
obj-$(CONFIG_FSL_RAID) += fsl_raid.o
|
|
|
|
|
obj-$(CONFIG_HSU_DMA) += hsu/
|
|
|
|
|
obj-$(CONFIG_IMG_MDC_DMA) += img-mdc-dma.o
|
2010-10-06 02:25:55 -06:00
|
|
|
obj-$(CONFIG_IMX_DMA) += imx-dma.o
|
2015-08-24 02:13:14 -06:00
|
|
|
obj-$(CONFIG_IMX_SDMA) += imx-sdma.o
|
2015-09-21 10:48:45 -06:00
|
|
|
obj-$(CONFIG_INTEL_IDMA64) += idma64.o
|
2015-08-24 02:13:14 -06:00
|
|
|
obj-$(CONFIG_INTEL_IOATDMA) += ioat/
|
|
|
|
|
obj-$(CONFIG_INTEL_IOP_ADMA) += iop-adma.o
|
|
|
|
|
obj-$(CONFIG_INTEL_MIC_X100_DMA) += mic_x100_dma.o
|
|
|
|
|
obj-$(CONFIG_K3_DMA) += k3dma.o
|
|
|
|
|
obj-$(CONFIG_LPC18XX_DMAMUX) += lpc18xx-dmamux.o
|
|
|
|
|
obj-$(CONFIG_MMP_PDMA) += mmp_pdma.o
|
|
|
|
|
obj-$(CONFIG_MMP_TDMA) += mmp_tdma.o
|
|
|
|
|
obj-$(CONFIG_MOXART_DMA) += moxart-dma.o
|
|
|
|
|
obj-$(CONFIG_MPC512X_DMA) += mpc512x_dma.o
|
|
|
|
|
obj-$(CONFIG_MV_XOR) += mv_xor.o
|
2016-06-16 06:28:34 -06:00
|
|
|
obj-$(CONFIG_MV_XOR_V2) += mv_xor_v2.o
|
2011-02-26 09:47:42 -07:00
|
|
|
obj-$(CONFIG_MXS_DMA) += mxs-dma.o
|
2015-08-24 02:13:14 -06:00
|
|
|
obj-$(CONFIG_MX3_IPU) += ipu/
|
|
|
|
|
obj-$(CONFIG_NBPFAXI_DMA) += nbpfaxi.o
|
2018-07-25 23:06:57 -06:00
|
|
|
obj-$(CONFIG_OWL_DMA) += owl-dma.o
|
2015-08-24 02:13:14 -06:00
|
|
|
obj-$(CONFIG_PCH_DMA) += pch_dma.o
|
|
|
|
|
obj-$(CONFIG_PL330_DMA) += pl330.o
|
|
|
|
|
obj-$(CONFIG_PPC_BESTCOMM) += bestcomm/
|
dmaengine: pxa: add pxa dmaengine driver
This is a new driver for pxa SoCs, which is also compatible with the former
mmp_pdma.
The rationale behind a new driver (as opposed to incremental patching) was :
- the new driver relies on virt-dma, which obsoletes all the internal
structures of mmp_pdma (sw_desc, hw_desc, ...), and by consequence all the
functions
- mmp_pdma allocates dma coherent descriptors containing not only hardware
descriptors but linked list information
The new driver only puts the dma hardware descriptors (ie. 4 u32) into the
dma pool allocated memory. This changes completely the way descriptors are
handled
- the architecture behind the interrupt/tasklet management was rewritten to be
more conforming to virt-dma
- the buffers alignment is handled differently
The former driver assumed that the DMA channel stopped between each
descriptor. The new one chains descriptors to let the channel running. This
is a necessary guarantee for real-time high bandwidth usecases such as video
capture on "old" architectures such as pxa.
- hot chaining / cold chaining / no chaining
Whenever possible, submitting a descriptor "hot chains" it to a running
channel. There is still no guarantee that the descriptor will be issued, as
the channel might be stopped just before the descriptor is submitted. Yet
this allows to submit several video buffers, and resubmit a buffer while
another is under handling.
As before, dma_async_issue_pending() is the only guarantee to have all the
buffers issued.
When an alignment issue is detected (ie. one address in a descriptor is not
a multiple of 8), if the already running channel is in "aligned mode", the
channel will stop, and restarted in "misaligned mode" to finished the issued
list.
- descriptors reusing
A submitted, issued and completed descriptor can be reused, ie resubmitted if
it was prepared with the proper flag (DMA_PREP_ACK). Only a channel
resources release will in this case release that buffer.
This allows a rolling ring of buffers to be reused, where there are several
thousands of hardware descriptors used (video buffer for example).
Additionally, a set of more casual features is introduced :
- debugging traces
- lockless way to know if a descriptor is terminated or not
The driver was tested on zylonite board (pxa3xx) and mioa701 (pxa27x),
with dmatest, pxa_camera and pxamci.
Signed-off-by: Robert Jarzmik <robert.jarzmik@free.fr>
Signed-off-by: Vinod Koul <vinod.koul@intel.com>
2015-05-25 15:29:20 -06:00
|
|
|
obj-$(CONFIG_PXA_DMA) += pxa_dma.o
|
2019-08-15 18:55:13 -06:00
|
|
|
obj-$(CONFIG_MXC_PXP_V2) += pxp/
|
|
|
|
|
obj-$(CONFIG_MXC_PXP_V3) += pxp/
|
2015-08-24 02:13:14 -06:00
|
|
|
obj-$(CONFIG_RENESAS_DMA) += sh/
|
2011-10-27 20:22:39 -06:00
|
|
|
obj-$(CONFIG_SIRF_DMA) += sirf-dma.o
|
2010-03-30 07:33:42 -06:00
|
|
|
obj-$(CONFIG_STE_DMA40) += ste_dma40.o ste_dma40_ll.o
|
2015-10-16 07:59:14 -06:00
|
|
|
obj-$(CONFIG_STM32_DMA) += stm32-dma.o
|
2017-09-22 01:31:30 -06:00
|
|
|
obj-$(CONFIG_STM32_DMAMUX) += stm32-dmamux.o
|
2017-09-28 09:36:41 -06:00
|
|
|
obj-$(CONFIG_STM32_MDMA) += stm32-mdma.o
|
2017-10-23 23:47:50 -06:00
|
|
|
obj-$(CONFIG_SPRD_DMA) += sprd-dma.o
|
2013-10-07 15:42:10 -06:00
|
|
|
obj-$(CONFIG_S3C24XX_DMAC) += s3c24xx-dma.o
|
2015-08-24 02:13:14 -06:00
|
|
|
obj-$(CONFIG_TXX9_DMAC) += txx9dmac.o
|
|
|
|
|
obj-$(CONFIG_TEGRA20_APB_DMA) += tegra20-apb-dma.o
|
2016-05-12 11:02:23 -06:00
|
|
|
obj-$(CONFIG_TEGRA210_ADMA) += tegra210-adma.o
|
2015-08-24 02:13:14 -06:00
|
|
|
obj-$(CONFIG_TIMB_DMA) += timb_dma.o
|
2018-10-11 10:41:03 -06:00
|
|
|
obj-$(CONFIG_UNIPHIER_MDMAC) += uniphier-mdmac.o
|
2015-03-18 07:47:34 -06:00
|
|
|
obj-$(CONFIG_XGENE_DMA) += xgene-dma.o
|
2016-12-15 07:03:35 -07:00
|
|
|
obj-$(CONFIG_ZX_DMA) += zx_dma.o
|
2016-10-18 03:39:11 -06:00
|
|
|
obj-$(CONFIG_ST_FDMA) += st_fdma.o
|
2018-10-11 02:49:41 -06:00
|
|
|
obj-$(CONFIG_CRYPTO_DEV_FSL_CAAM_DMA) += caam_dma.o
|
2019-03-04 00:45:56 -07:00
|
|
|
obj-$(CONFIG_FSL_DPAA2_QDMA) += fsl-dpaa2-qdma/
|
2015-08-24 02:13:14 -06:00
|
|
|
|
2018-03-15 01:40:36 -06:00
|
|
|
obj-y += mediatek/
|
2016-02-04 21:34:32 -07:00
|
|
|
obj-y += qcom/
|
2018-04-25 02:45:03 -06:00
|
|
|
obj-y += ti/
|
2015-08-24 02:13:14 -06:00
|
|
|
obj-y += xilinx/
|