Changes in Makefile

134d9c52 - dmaengine: dw: dmamux: Introduce RZN1 DMA router support

Wed, 27 Apr 2022 09:56:49 +0000

dmaengine: dw: dmamux: Introduce RZN1 DMA router supportThe Renesas RZN1 DMA IP is based on a DW core, with eg. an additionaldmamux register located in the system control area which can take up to32 requests (16 per DMA controller). Each DMA channel can be wired totwo different peripherals.We need two additional information from the 'dmas' property: the channel(bit in the dmamux register) that must be accessed and the value of themux for this channel.Signed-off-by: Miquel Raynal Reviewed-by: Andy Shevchenko Reviewed-by: Ilpo Järvinen Link: https://lore.kernel.org/r/20220427095653.91804-6-miquel.raynal@bootlin.comSigned-off-by: Vinod Koul List of files: /linux-6.15/drivers/dma/dw/Makefile

0658e5a8 - dmaengine: dw: Replace 'objs' by 'y'

Tue, 26 May 2020 18:24:16 +0000

dmaengine: dw: Replace 'objs' by 'y'`-objs` is fitted for building host programs, change to `-y`,more straightforward for device drivers.Signed-off-by: Andy Shevchenko Link: https://lore.kernel.org/r/20200526182416.52805-2-andriy.shevchenko@linux.intel.comSigned-off-by: Vinod Koul List of files: /linux-6.15/drivers/dma/dw/Makefile

38e4fb66 - dmaengine: dw: Register ACPI DMA controller for PCI that has companion

Tue, 26 May 2020 18:24:15 +0000

dmaengine: dw: Register ACPI DMA controller for PCI that has companionIf PCI enumerated controller has a companion device,register it in the ACPI DMA controllers as well.Fixes: f7c799e950f9 ("dmaengine: dw: we do support Merrifield SoC in PCI mode")Depends-on: b685fe26e9af ("dmaengine: dw: platform: Split ACPI helpers to separate module")Signed-off-by: Andy Shevchenko Link: https://lore.kernel.org/r/20200526182416.52805-1-andriy.shevchenko@linux.intel.comSigned-off-by: Vinod Koul List of files: /linux-6.15/drivers/dma/dw/Makefile

f5e84eae - dmaengine: dw: platform: Split OF helpers to separate module

Tue, 20 Aug 2019 13:15:46 +0000

dmaengine: dw: platform: Split OF helpers to separate moduleFor better maintenance split OF helpers to the separate module.Signed-off-by: Andy Shevchenko Link: https://lore.kernel.org/r/20190820131546.75744-11-andriy.shevchenko@linux.intel.comSigned-off-by: Vinod Koul List of files: /linux-6.15/drivers/dma/dw/Makefile

b685fe26 - dmaengine: dw: platform: Split ACPI helpers to separate module

Tue, 20 Aug 2019 13:15:45 +0000

dmaengine: dw: platform: Split ACPI helpers to separate moduleFor better maintenance split ACPI helpers to the separate module.Signed-off-by: Andy Shevchenko Link: https://lore.kernel.org/r/20190820131546.75744-10-andriy.shevchenko@linux.intel.comSigned-off-by: Vinod Koul List of files: /linux-6.15/drivers/dma/dw/Makefile

69da8be9 - dmaengine: dw: Split DW and iDMA 32-bit operations

Mon, 07 Jan 2019 11:07:38 +0000

dmaengine: dw: Split DW and iDMA 32-bit operationsHere is a kinda big refactoring that should have been donein the first place, when Intel iDMA 32-bit support appeared.It splits operations which are different to Synopsys DesignWare andIntel iDMA 32-bit controllers.No functional change intended.Signed-off-by: Andy Shevchenko Signed-off-by: Vinod Koul List of files: /linux-6.15/drivers/dma/dw/Makefile

b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license

Wed, 01 Nov 2017 14:07:57 +0000

License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense 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 bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe 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 caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode & Windriver) producing SPDXtag:value files created by Philippe Ombredanne. Philippe prepared thebase 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 filesassessed. Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately 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 licenseidentifiers 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 thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights. TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion 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 correctThis produced a worksheet with 20 files needing minor correction. Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg. Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected. This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.) Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart Reviewed-by: Philippe Ombredanne Reviewed-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/dma/dw/Makefile

fed42c19 - dma: dw: add PCI part of the driver

Wed, 05 Jun 2013 12:26:46 +0000

dma: dw: add PCI part of the driverThis is the PCI part of the DesignWare DMAC driver. The controller is usuallyused in the Intel hardware such as Intel Medfield.Signed-off-by: Andy Shevchenko Acked-by: Arnd Bergmann Acked-by: Viresh Kumar Signed-off-by: Vinod Koul List of files: /linux-6.15/drivers/dma/dw/Makefile

9cade1a4 - dma: dw: split driver to library part and platform code

Wed, 05 Jun 2013 12:26:45 +0000

dma: dw: split driver to library part and platform codeTo simplify the driver development let's split driver to library and platformcode parts. It helps us to add PCI driver in future.Signed-off-by: Andy Shevchenko Acked-by: Arnd Bergmann Acked-by: Viresh Kumar [Fixed compile error and few checkpatch issues]Signed-off-by: Vinod Koul List of files: /linux-6.15/drivers/dma/dw/Makefile

61a76496 - dma: move dw_dmac driver to an own directory

Wed, 05 Jun 2013 12:26:44 +0000

dma: move dw_dmac driver to an own directoryThe dw_dmac driver is going to be split into multiple files. To make this moreconvenient move it to an own directory.Signed-off-by: Andy Shevchenko Acked-by: Viresh Kumar Acked-by: Arnd Bergmann Signed-off-by: Vinod Koul List of files: /linux-6.15/drivers/dma/dw/Makefile