Changes in Makefile

e624e6c3 - nfc: Add a virtual nci device driver

Wed, 27 Jan 2021 13:08:28 +0000

nfc: Add a virtual nci device driverNCI virtual device simulates a NCI device to the user. It can be used tovalidate the NCI module and applications. This driver supportscommunication between the virtual NCI device and NCI module.Signed-off-by: Bongsu Jeon Signed-off-by: Jakub Kicinski List of files: /linux-6.15/drivers/nfc/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/nfc/Makefile

0b73ef79 - NFC: remove TI nfcwilink driver

Wed, 25 Jan 2017 22:23:07 +0000

NFC: remove TI nfcwilink driverIt appears that TI WiLink devices including NFC (WL185x/WL189x) nevershipped. The only information I found were announcements in Feb2012 about the parts. There's been no activity on this driver besidedcommon changes since initially added in Jan 2012. There's also no inusers that instantiate the platform device (nor DT bindings).This is a first step in removing TI ST (shared transport) driver infavor of extending the BT hci_ll driver to support WL183x chips.Cc: Ilan Elias Cc: Marcel Holtmann Cc: Samuel Ortiz Cc: Lauro Ramos Venancio Cc: Aloisio Almeida Jr Cc: linux-wireless@vger.kernel.orgSigned-off-by: Rob Herring Signed-off-by: Samuel Ortiz List of files: /linux-6.15/drivers/nfc/Makefile

9815c7cf - NFC: pn533: Separate physical layer from the core implementation

Fri, 25 Mar 2016 14:46:53 +0000

NFC: pn533: Separate physical layer from the core implementationThe driver now has all core stuff isolated in one file, and allthe hardware link specifics in another. Writing a pn533 driveron top of another hardware link is now just a matter of adding anew file for that new hardware specifics.The first user of this separation will be the i2c based pn532driver that reuses pn533 core implementation on top of an i2clayer.Signed-off-by: Michael Thalmeier Signed-off-by: Samuel Ortiz List of files: /linux-6.15/drivers/nfc/Makefile

cab47333 - NFC: Add STMicroelectronics ST95HF driver

Mon, 21 Dec 2015 23:03:30 +0000

NFC: Add STMicroelectronics ST95HF driverThis driver supports STMicroelectronics NFC Transceiver"ST95HF", in in initiator role to read/write ISO14443 Type 4A,ISO14443 Type 4B and ISO15693 Type5 tags.The ST95HF datasheet is available here:http://www.st.com/web/en/resource/technical/document/datasheet/DM00102056.pdfSigned-off-by: Shikha Singh Signed-off-by: Samuel Ortiz List of files: /linux-6.15/drivers/nfc/Makefile

a06347c0 - NFC: Add Intel Fields Peak NFC solution driver

Thu, 22 Oct 2015 09:11:42 +0000

NFC: Add Intel Fields Peak NFC solution driverFields Peak complies with the ISO/IEC 14443A/B, 15693, 18092,and JIS X 6319-4. It is an NCI based controller.RF Protocols supported: - NFC Forum Type 1 Tags (Jewel, Topaz) - NFC Forum Type 2 Tags (Mifare UL) - NFC Forum Type 3 Tags (FeliCa) - NFC Forum Type 4A (ISO/IEC 14443 A-4 106kbps to 848kbps) - NFC Forum Type 4B (ISO/IEC 14443 B-4 106kbps to 848kbps) - NFCIP in passive and active modes (ISO/IEC 18092 106kbps to 424kbps) - B’ (based on ISO/IEC 14443 B-2) - iCLASS (based on ISO/IEC 15693-2) - Vicinity cards (ISO/IEC 15693-3) - Kovio tags (NFC Forum Type 2)The device can be enumerated using ACPI using the id INT339A.The 1st GPIO is the IRQ and the 2nd is the RESET pin.Signed-off-by: Robert Dolca Signed-off-by: Samuel Ortiz List of files: /linux-6.15/drivers/nfc/Makefile

c04c674f - nfc: s3fwrn5: Add driver for Samsung S3FWRN5 NFC Chip

Thu, 20 Aug 2015 15:26:02 +0000

nfc: s3fwrn5: Add driver for Samsung S3FWRN5 NFC ChipAdd driver for Samsung S3FWRN5 NFC controller.S3FWRN5 is using NCI protocol and I2C communication interface.Signed-off-by: Robert Baldyga Signed-off-by: Samuel Ortiz List of files: /linux-6.15/drivers/nfc/Makefile

ed06aeef - nfc: st-nci: Rename st21nfcb to st-nci

Tue, 09 Jun 2015 20:26:05 +0000

nfc: st-nci: Rename st21nfcb to st-nciSTMicroelectronics NFC NCI chips family is extendingwith the new ST21NFCC using the AMS AS39230 RF booster.The st21nfcb driver is relevant for this solution andmight be with future products.Signed-off-by: Christophe Ricard Signed-off-by: Samuel Ortiz List of files: /linux-6.15/drivers/nfc/Makefile

71fa6fba - NFC: Remove obsolete setting of DEBUG

Tue, 28 Apr 2015 09:08:47 +0000

NFC: Remove obsolete setting of DEBUGCONFIG_DYNAMIC_DEBUG is the right toggle to enable pr_debug().Signed-off-by: Valentin Rothberg Signed-off-by: Samuel Ortiz List of files: /linux-6.15/drivers/nfc/Makefile

dece4585 - NFC: nxp-nci: Add support for NXP NCI chips

Mon, 09 Mar 2015 10:12:04 +0000

NFC: nxp-nci: Add support for NXP NCI chipsAdd support for NXP NCI NFC controllers such as the NPC100 or PN7150families.Signed-off-by: Clément Perrochaud Signed-off-by: Samuel Ortiz List of files: /linux-6.15/drivers/nfc/Makefile

35630df6 - NFC: st21nfcb: Add driver for STMicroelectronics ST21NFCB NFC chip

Sun, 25 May 2014 20:35:38 +0000

NFC: st21nfcb: Add driver for STMicroelectronics ST21NFCB NFC chipAdd driver for STMicroelectronics ST21NFCB NFC controller.ST21NFCB is using NCI protocol and a proprietary low level transportprotocol called NDLC used on top.NDLC:The protocol defines 2 types of frame:- One type carrying NCI data (referred as DATAFRAME frames).- One type carrying protocol information used for flow control and errorcontrol mechanisms (referred as SUPERVISOR frames).After each frame transmission to the NFC controller, the device hostSHALL waitfor an ACK (SUPERVISOR frame) reception before sending anew frame.The NFC controller MAY send a frame at anytime to the device host.The NFC controller MAY send a specific WAIT supervisor frame to indicateto device host that a NCI data packet has been received but that it couldtake significant time before the NFC controller sends an ACK and thusallows next data reception.Signed-off-by: Christophe Ricard Signed-off-by: Samuel Ortiz List of files: /linux-6.15/drivers/nfc/Makefile

68957303 - NFC: ST21NFCA: Add driver for STMicroelectronics ST21NFCA NFC Chip

Tue, 25 Mar 2014 05:51:47 +0000

NFC: ST21NFCA: Add driver for STMicroelectronics ST21NFCA NFC ChipAdd driver for STMicroelectronics ST21NFCA NFC controller.ST21NFCA is using HCI protocol, shdlc as LLC layer & I2C ascommunication protocol.Adding support for Reader/Writer mode with Tag type 1/2/3/4 A & B.It is using proprietary gate 15 for ISO14443-3 such as type 1 &type 2 tags. It is using proprietary gate 14 for type F tags.ST21NFCA_DEVICE_MGNT_GATE gives access to proprietary CLF configuration.Standard gate for ISO14443-4 A (13) & B (11) are also used.ST21NFCA specific mecanism:One particular point to notice for the data handling is that framedoes not contain any length value. Therefore the i2c part of this driveris managing the reception with a read length sequence until the end offrame (0x7e) is reached.In order to avoid conflict between sof & eof a mecanismcalled byte stuffing concist of an escape byte (0x7d) insertion beforespecial byte (0x7e, 0x7d). The special byte is then xored with 0x20.In this driver, When data are available in the CLF, the interruptgpio is driven to active state and triggered an interrupt.Once the i2c_master_recv start, the interrupt gpio is driven to idlestate until its complete. If the frame is incomplete or data are stillavailable, interrupts will be triggered again.Signed-off-by: Christophe Ricard Signed-off-by: Samuel Ortiz List of files: /linux-6.15/drivers/nfc/Makefile

165063f1 - NFC: trf7970a: Add driver with ISO/IEC 14443 Type 2 Tag Support

Mon, 10 Mar 2014 18:56:22 +0000

NFC: trf7970a: Add driver with ISO/IEC 14443 Type 2 Tag SupportAdd a driver for the Texas Instruments TRF7970a RFID/NFC/15693transceiver. The driver currently supports ISO/IEC 14443 Type 2tags only (MIFARE Ultralight and Ultralight C but not Classic).CC: Erick Macias CC: Felipe Balbi Signed-off-by: Mark A. Greer Signed-off-by: Samuel Ortiz List of files: /linux-6.15/drivers/nfc/Makefile

f26e30cc - NFC: nfcmrvl: Initial commit for Marvell NFC driver

Mon, 06 Jan 2014 20:58:19 +0000

NFC: nfcmrvl: Initial commit for Marvell NFC driverThis patch adds NFC support for Marvell 8897 NFC-over-USB chipset.Signed-off-by: Amitkumar Karwar Signed-off-by: Bing Zhao Signed-off-by: Samuel Ortiz List of files: /linux-6.15/drivers/nfc/Makefile

562d4d59 - NFC: Sony Port-100 Series driver

Fri, 04 Oct 2013 10:12:00 +0000

NFC: Sony Port-100 Series driverThis adds support for the Sony NFC USB dongle RC-S380, based on thePort-100 chip. This dongle is an analog frontend and does not implementthe digital layer. This driver uses the nfc_digital module which is animplementation of the NFC Digital Protocol stack.This patch is a skeleton. It only registers the dongle against the NFCdigital protocol stack. All NFC digital operation functions are stubbedout.Signed-off-by: Thierry Escande Cc: Stephen Tiedemann Tested-by: Cho, Yu-Chen Signed-off-by: Samuel Ortiz List of files: /linux-6.15/drivers/nfc/Makefile

7cbe0ff3 - NFC: Add a nfc hardware simulation driver

Thu, 06 Jun 2013 14:23:23 +0000

NFC: Add a nfc hardware simulation driverThis driver declares two virtual NFC devices supporting NFC-DEP protocol.An LLCP connection can be established between them and all packets sentfrom one device is sent back to the other, acting as loopback devices.Once established, the LLCP link can be disconnected by disabling the targetdevice (with rfkill, nfctool, or neard disable-adapter test script).Signed-off-by: Thierry Escande Signed-off-by: Samuel Ortiz List of files: /linux-6.15/drivers/nfc/Makefile

4912e2fe - NFC: mei: Add a common mei bus API for NFC drivers

Mon, 15 Apr 2013 09:19:20 +0000

NFC: mei: Add a common mei bus API for NFC driversThis isolates the common code that is required to use an mei bus nfcdevice from an NFC HCI drivers. This prepares for future drivers forNFC chips connected behind an Intel Management Engine controller.The microread_mei HCI driver is also modified to use that common code.Signed-off-by: Eric Lapuyade Signed-off-by: Samuel Ortiz List of files: /linux-6.15/drivers/nfc/Makefile

cfad1ba8 - NFC: Initial support for Inside Secure microread

Tue, 18 Dec 2012 13:53:53 +0000

NFC: Initial support for Inside Secure microreadInside Secure microread is an HCI based NFC chipset.This initial support includes reader and p2p (Target and initiator) modes.Signed-off-by: Eric Lapuyade Signed-off-by: Samuel Ortiz List of files: /linux-6.15/drivers/nfc/Makefile

aa741030 - NFC: pn544: Separate the core code and the i2c one into different modules

Tue, 18 Dec 2012 15:26:23 +0000

NFC: pn544: Separate the core code and the i2c one into different modulesAs we may need to support other physical layers, we can avoid linking thecore part into each and every pn544 module.Signed-off-by: Samuel Ortiz List of files: /linux-6.15/drivers/nfc/Makefile

97f18414 - NFC: Separate pn544 hci driver in HW dependant and independant parts

Tue, 02 Oct 2012 16:44:06 +0000

NFC: Separate pn544 hci driver in HW dependant and independant partsThe driver now has all HCI stuff isolated in one file, and all thehardware link specifics in another. Writing a pn544 driver on top ofanother hardware link is now just a matter of adding a new file for thatnew hardware specifics.Signed-off-by: Eric Lapuyade Signed-off-by: Samuel Ortiz List of files: /linux-6.15/drivers/nfc/Makefile