Changes in 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/iio/trigger/Makefile

b01ced2b - iio: trigger: Add STM32 LPTimer trigger driver

Mon, 28 Aug 2017 10:04:11 +0000

iio: trigger: Add STM32 LPTimer trigger driverAdd support for LPTIMx_OUT triggers that can be found on some STM32devices. These triggers can be used then by ADC or DAC.Typical usage is to configure LPTimer as PWM output (via pwm-stm32-lp)and have synchronised analog conversions with these triggers.Signed-off-by: Fabrice Gasnier Reviewed-by: Jonathan Cameron Signed-off-by: Lee Jones List of files: /linux-6.15/drivers/iio/trigger/Makefile

93fbe91b - iio: Add STM32 timer trigger driver

Fri, 20 Jan 2017 09:15:07 +0000

iio: Add STM32 timer trigger driverTimers IPs can be used to generate triggers for other IPs likeDAC or ADC.Each trigger may result of timer internals signals like counter enable,reset or edge, this configuration could be done through "master_mode"device attribute.Since triggers could be used by DAC or ADC their names are definedin include/ nux/iio/timer/stm32-timer-trigger.h and is_stm32_iio_timer_triggerfunction could be used to check if the trigger is valid or not."trgo" trigger have a "sampling_frequency" attribute which allow to configuretimer sampling frequency.version 8:- change kernel version from 4.10 to 4.11 in ABI documentationversion 7:- remove all iio_device related code- move driver into trigger directoryversion 5:- simplify tables of triggers- only create an IIO device when neededversion 4:- get triggers configuration from "reg" in DT- add tables of triggers- sampling frequency is enable/disable when writing in trigger sampling_frequency attribute- no more use of interruptionsversion 3:- change compatible to "st,stm32-timer-trigger"- fix attributes access right- use string instead of int for master_mode and slave_mode- document device attributes in sysfs-bus-iio-timer-stm32version 2:- keep only one compatible- use st,input-triggers-names and st,output-triggers-names to know which triggers are accepted and/or create by the deviceSigned-off-by: Benjamin Gaignard Acked-by: Jonathan Cameron Signed-off-by: Lee Jones List of files: /linux-6.15/drivers/iio/trigger/Makefile

bc2e1126 - iio:trigger: Experimental kthread tight loop trigger (thread only)

Sun, 06 Mar 2016 20:02:56 +0000

iio:trigger: Experimental kthread tight loop trigger (thread only)This patch is in response to that ofGregor Boirie who proposed using a tight kthread within a device driver (be it with thesupport factored out into a helper library) in order to basically spin asfast as possible.It is meant as a talking point rather than a formal proposal of the code(though we are heading towards that I think).Also gives people some working code to mess around with.I proposed that this could be done with a trigger with a few constraintsand this is the proof (be it ugly) of that.There are some constraints though, some of which we would want to relaxif this were to move forward.* Will only run the thread part of the registered pollfunc. This is to avoid the overhead of jumping in and out of interrupt context. Is the overhead significant? Not certain but feels like it should be!* This limitation precludes any device that 'must' do some work in interrupt context. However, that is true of few if any drivers and I suspect that any that do will be restricted to using triggers they provide themselves. Usually we have a top half mainly to grab a timestamp as soon after the dataready type signal as possible.Signed-off-by: Jonathan Cameron Acked-by: Daniel Baluta List of files: /linux-6.15/drivers/iio/trigger/Makefile

ac5006a2 - iio: trigger: Introduce IIO hrtimer based trigger

Mon, 09 Nov 2015 07:14:01 +0000

iio: trigger: Introduce IIO hrtimer based triggerThis patch registers a new IIO software trigger interrupt sourcebased on high resolution timers.Notice that if configfs is enabled we create sampling_frequencyattribute allowing users to change hrtimer period (1/sampling_frequency).The IIO hrtimer trigger has a long history, this patch is based onan older version from Marten and Lars-Peter.Signed-off-by: Marten Svanfeldt Signed-off-by: Lars-Peter Clausen Signed-off-by: Daniel Baluta Signed-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/trigger/Makefile

3edc84e6 - iio: Add a comment to about alphabetical order to Kconfigs and Makefiles

Mon, 15 Jul 2013 07:45:00 +0000

iio: Add a comment to about alphabetical order to Kconfigs and MakefilesKeeping Makefile and Kconfig entries in alphabetical order usually works betterthan just appending new entries at the end, since it reduces the amount ofconflicts. This patch adds a comment to the IIO Kconfig and Makefile files todocument that the entries should be kept in alphabetical order.Also reorder those entries which weren't in alphabetical order yet.Signed-off-by: Lars-Peter Clausen Signed-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/trigger/Makefile

c7a8be08 - iio:triggers:interrupt trigger - move out of staging.

Sun, 02 Jun 2013 19:00:00 +0000

iio:triggers:interrupt trigger - move out of staging.This is now a very simple trigger indeed but useful in many common cases.Signed-off-by: Jonathan Cameron Reviewed-by: Lars-Peter Clausen List of files: /linux-6.15/drivers/iio/trigger/Makefile

e64e7d5c - iio:trigger:sysfs Move out of staging.

Sun, 14 Apr 2013 11:54:00 +0000

iio:trigger:sysfs Move out of staging.This simple driver is rather useful. No issues about its interfacehave been raised for some time hence the proposal to move it outof staging.Signed-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/trigger/Makefile