Changes in Makefile

5d0c3533 - dmaengine: qcom: Add GPI dma driver

Mon, 09 Nov 2020 08:54:50 +0000

dmaengine: qcom: Add GPI dma driverThis controller provides DMAengine capabilities for a variety of peripheralbuses such as I2C, UART, and SPI. By using GPI dmaengine driver, busdrivers can use a standardize interface that is protocol independent totransfer data between memory and peripheral.Link: https://lore.kernel.org/r/20201109085450.24843-4-vkoul@kernel.orgSigned-off-by: Vinod Koul List of files: /linux-6.15/drivers/dma/qcom/Makefile

5c9f8c2d - dmaengine: qcom: Add ADM driver

Sat, 14 Nov 2020 14:02:33 +0000

dmaengine: qcom: Add ADM driverAdd the DMA engine driver for the QCOM Application Data Mover (ADM) DMAcontroller found in the MSM8x60 and IPQ/APQ8064 platforms.The ADM supports both memory to memory transactions and memoryto/from peripheral device transactions. The controller also providesflow control capabilities for transactions to/from peripheral devices.The initial release of this driver supports slave transfers to/fromperipherals and also incorporates CRCI (client rate control interface)flow control.The hardware only supports a 32 bit physical address, so specifying!PHYS_ADDR_T_64BIT gives maximum COMPILE_TEST coverage without having tospend effort on kludging things in the code that will never actually beneeded on real hardware.Signed-off-by: Andy Gross Signed-off-by: Thomas Pedersen Signed-off-by: Jonathan McDowell Link: https://lore.kernel.org/r/20201114140233.GM32650@earth.liSigned-off-by: Vinod Koul List of files: /linux-6.15/drivers/dma/qcom/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/qcom/Makefile

570d0176 - dmaengine: qcom_hidma: add debugfs hooks

Sun, 01 May 2016 04:25:27 +0000

dmaengine: qcom_hidma: add debugfs hooksAdd debugfs hooks for debugging the execution behavior of the DMAchannel. The debugfs hooks get initialized by the probe function anduninitialized by the remove function.A stats file is created in debugfs. The stats file will show theinformation about each HIDMA channel as well as each asynchronous jobqueued and completed at a given time.Signed-off-by: Sinan Kaya Signed-off-by: Vinod Koul List of files: /linux-6.15/drivers/dma/qcom/Makefile

d1615ca2 - dmaengine: qcom_hidma: implement lower level hardware interface

Sun, 01 May 2016 04:25:26 +0000

dmaengine: qcom_hidma: implement lower level hardware interfaceThis patch implements the hardware hooks for the HIDMA channel driver.The main functions of interest are:- hidma_ll_init- hidma_ll_request- hidma_ll_queue_request- hidma_ll_hw_startOS layer calls the hidma_ll_init function during probe to set up thehardware. At this moment, the number of supported descriptors are alsogiven. On each request, a descriptor is allocated from the free pool andfilled in with the transfer parameters. Multiple requests can be queuedinto the hardware via the OS interface. When client is ready for requeststo be executed, start method is called.Completions are delivered via callbacks via tasklet.Signed-off-by: Sinan Kaya Signed-off-by: Vinod Koul List of files: /linux-6.15/drivers/dma/qcom/Makefile

7f8f209f - dmaengine: add Qualcomm Technologies HIDMA management driver

Fri, 05 Feb 2016 04:34:34 +0000

dmaengine: add Qualcomm Technologies HIDMA management driverThe Qualcomm Technologies HIDMA device has been designed to supportvirtualization technology. The driver has been divided into two to followthe hardware design.1. HIDMA Management driver2. HIDMA Channel driverEach HIDMA HW consists of multiple channels. These channels share some setof common parameters. These parameters are initialized by the managementdriver during power up. Same management driver is used for monitoring theexecution of the channels. Management driver can change the performancebehavior dynamically such as bandwidth allocation and prioritization.The management driver is executed in host context and is the mainmanagement entity for all channels provided by the device.Signed-off-by: Sinan Kaya Reviewed-by: Andy Shevchenko Signed-off-by: Vinod Koul List of files: /linux-6.15/drivers/dma/qcom/Makefile

d9b31efc - dmaengine: qcom_bam_dma: move to qcom directory

Fri, 05 Feb 2016 04:34:32 +0000

dmaengine: qcom_bam_dma: move to qcom directoryCreating a QCOM directory for all QCOM DMA source files.Signed-off-by: Sinan Kaya Reviewed-by: Andy Gross Signed-off-by: Vinod Koul List of files: /linux-6.15/drivers/dma/qcom/Makefile