Changes in Makefile

9e4c596b - Input: synaptics-rmi4 - add support for F3A

Mon, 05 Oct 2020 02:42:24 +0000

Input: synaptics-rmi4 - add support for F3ARMI4 F3A supports the touchpad GPIO function, it's designed tosupport more GPIOs and used on newer touchpads. This patch addssupport of the touchpad buttons.Signed-off-by: Vincent Huang Reviewed-by: Hans de Goede Tested-by: Hans de Goede Reviewed-by: Andrew Duggan Link: https://lore.kernel.org/r/20200930094147.635556-3-vincent.huang@tw.synaptics.comSigned-off-by: Dmitry Torokhov List of files: /linux-6.15/drivers/input/rmi4/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/input/rmi4/Makefile

5191d88a - Input: synaptics-rmi4 - add support for F34 V7 bootloader

Sun, 11 Dec 2016 07:27:32 +0000

Input: synaptics-rmi4 - add support for F34 V7 bootloaderPort firmware update code from Samsung Galaxy S7 driver intomainline framework.This patch has been tested on Synaptics S7813.Signed-off-by: Nick Dyer Tested-by: Chris Healy Signed-off-by: Dmitry Torokhov List of files: /linux-6.15/drivers/input/rmi4/Makefile

c5e8848f - Input: synaptics-rmi4 - add support for F03

Sat, 03 Dec 2016 00:59:07 +0000

Input: synaptics-rmi4 - add support for F03This adds basic functionality for PS/2 passthrough on SynapticsTouchpads using RMI4 through smbus.Reviewed-by: Andrew Duggan Signed-off-by: Lyude Paul Signed-off-by: Benjamin Tissoires Signed-off-by: Dmitry Torokhov List of files: /linux-6.15/drivers/input/rmi4/Makefile

6adba43f - Input: synaptics-rmi4 - add support for F55 sensor tuning

Wed, 23 Nov 2016 01:53:26 +0000

Input: synaptics-rmi4 - add support for F55 sensor tuningSensor tuning support is needed to determine the number of enabledtx and rx electrodes for use in F54 functions.The number of enabled electrodes is not identical to the total numberof electrodes as reported with F55:Query0 and F55:Query1. It has to becalculated by analyzing F55:Ctrl1 (sensor receiver assignment) andF55:Ctrl2 (sensor transmitter assignment).Support for additional sensor tuning functions may be added later.Fixes: 3a762dbd5347 ("[media] Input: synaptics-rmi4 - add support for F54 ...")Signed-off-by: Guenter Roeck Tested-by: Nick Dyer Signed-off-by: Dmitry Torokhov List of files: /linux-6.15/drivers/input/rmi4/Makefile

29fd0ec2 - Input: synaptics-rmi4 - add support for F34 device reflash

Wed, 23 Nov 2016 01:44:12 +0000

Input: synaptics-rmi4 - add support for F34 device reflashAdd support for updating firmware, triggered by a sysfs attribute.This patch has been tested on Synaptics S7300.Signed-off-by: Nick Dyer Tested-by: Chris Healy Signed-off-by: Dmitry Torokhov List of files: /linux-6.15/drivers/input/rmi4/Makefile

82264d0c - Input: synaptics-rmi4 - add SMBus support

Wed, 09 Nov 2016 01:05:58 +0000

Input: synaptics-rmi4 - add SMBus supportCode obtained from https://raw.githubusercontent.com/mightybigcar/synaptics-rmi4/jf/drivers/input/rmi4/rmi_smbus.cand updated to match upstream. And fixed to make it work.Signed-off-by: Benjamin Tissoires Signed-off-by: Andrew Duggan Signed-off-by: Dmitry Torokhov List of files: /linux-6.15/drivers/input/rmi4/Makefile

3a762dbd - [media] Input: synaptics-rmi4 - add support for F54 diagnostics

Mon, 18 Jul 2016 21:10:37 +0000

[media] Input: synaptics-rmi4 - add support for F54 diagnosticsFunction 54 implements access to various RMI4 diagnostic features.This patch adds support for retrieving this data. It registers a V4L2device to output the data to user space.Signed-off-by: Nick Dyer Tested-by: Andrew Duggan Tested-by: Chris Healy Signed-off-by: Hans Verkuil Signed-off-by: Mauro Carvalho Chehab Acked-by: Dmitry Torokhov List of files: /linux-6.15/drivers/input/rmi4/Makefile

8d99758d - Input: synaptics-rmi4 - add SPI transport driver

Thu, 10 Mar 2016 23:58:12 +0000

Input: synaptics-rmi4 - add SPI transport driverAdd the transport driver for devices using RMI4 over SPI.Signed-off-by: Andrew Duggan Tested-by: Benjamin Tissoires Tested-by: Linus Walleij Tested-by: Bjorn Andersson Signed-off-by: Dmitry Torokhov List of files: /linux-6.15/drivers/input/rmi4/Makefile

562b42d3 - Input: synaptics-rmi4 - add support for F30

Thu, 10 Mar 2016 23:56:58 +0000

Input: synaptics-rmi4 - add support for F30RMI4 F30 supports input from clickpad buttons and controls LEDs locatedon the touchpad PCB. This patch adds support of the clickpad buttons anddefers supporting LEDs for the future.Signed-off-by: Andrew Duggan Signed-off-by: Benjamin Tissoires Tested-by: Benjamin Tissoires Tested-by: Linus Walleij Tested-by: Bjorn Andersson Signed-off-by: Dmitry Torokhov List of files: /linux-6.15/drivers/input/rmi4/Makefile

b43d2c1e - Input: synaptics-rmi4 - add support for F12

Thu, 10 Mar 2016 23:55:29 +0000

Input: synaptics-rmi4 - add support for F12Function 12 implements 2D touch position sensor for newer Synaptics touchdevices. It replaces F11 and no device will contain both functions.Signed-off-by: Andrew Duggan Signed-off-by: Christopher Heiny Tested-by: Benjamin Tissoires Tested-by: Linus Walleij Tested-by: Bjorn Andersson Signed-off-by: Dmitry Torokhov List of files: /linux-6.15/drivers/input/rmi4/Makefile

ff8f8370 - Input: synaptics-rmi4 - add support for 2D sensors and F11

Thu, 10 Mar 2016 23:47:28 +0000

Input: synaptics-rmi4 - add support for 2D sensors and F11RMI4 currently defines two functions for reporting data for 2D sensors(F11 and F12). This patch adds the common functionality which is sharedby devices with 2D reporting along with implementing functionality forF11.Signed-off-by: Andrew Duggan Signed-off-by: Christopher Heiny Tested-by: Benjamin Tissoires Tested-by: Linus Walleij Tested-by: Bjorn Andersson Signed-off-by: Dmitry Torokhov List of files: /linux-6.15/drivers/input/rmi4/Makefile

fdf51604 - Input: synaptics-rmi4 - add I2C transport driver

Thu, 10 Mar 2016 23:44:27 +0000

Input: synaptics-rmi4 - add I2C transport driverAdd the transport driver for devices using RMI4 over I2C.Signed-off-by: Andrew Duggan Signed-off-by: Christopher Heiny Tested-by: Benjamin Tissoires Tested-by: Linus Walleij Tested-by: Bjorn Andersson Signed-off-by: Dmitry Torokhov List of files: /linux-6.15/drivers/input/rmi4/Makefile

2b6a321d - Input: synaptics-rmi4 - add support for Synaptics RMI4 devices

Thu, 10 Mar 2016 23:35:49 +0000

Input: synaptics-rmi4 - add support for Synaptics RMI4 devicesSynaptics uses the Register Mapped Interface (RMI) protocol as acommunications interface for their devices. This driver adds the corefunctionality needed to interface with RMI4 devices.RMI devices can be connected to the host via several transport protocolsand can supports a wide variety of functionality defined by RMI functions.Support for transport protocols and RMI functions are implemented inindividual drivers. The RMI4 core driver uses a bus architecture tofacilitate the various combinations of transport and function driversneeded by a particular device.Signed-off-by: Andrew Duggan Signed-off-by: Christopher Heiny Tested-by: Benjamin Tissoires Tested-by: Linus Walleij Tested-by: Bjorn Andersson Signed-off-by: Dmitry Torokhov List of files: /linux-6.15/drivers/input/rmi4/Makefile