Changes in Kconfig

864e898b - net: remove redundant 'depends on NET'

Mon, 25 Jan 2021 23:20:26 +0000

net: remove redundant 'depends on NET'These Kconfig files are included from net/Kconfig, inside theif NET ... endif.Remove 'depends on NET', which we know it is already met.Signed-off-by: Masahiro Yamada Link: https://lore.kernel.org/r/20210125232026.106855-1-masahiroy@kernel.orgSigned-off-by: Jakub Kicinski List of files: /linux-6.15/net/nfc/Kconfig

8354bcbe - net: sched: fix spelling mistake in Kconfig "trys" -> "tries"

Mon, 07 Dec 2020 16:12:31 +0000

net: sched: fix spelling mistake in Kconfig "trys" -> "tries"There is a spelling mistake in the Kconfig help text. Fix it.Signed-off-by: Colin Ian King Signed-off-by: David S. Miller List of files: /linux-6.15/net/nfc/Kconfig

ec8f24b7 - treewide: Add SPDX license identifier - Makefile/Kconfig

Sun, 19 May 2019 12:07:45 +0000

treewide: Add SPDX license identifier - Makefile/KconfigAdd SPDX license identifiers to all Make/Kconfig files which: - Have no license information of any formThese files fall under the project license, GPL v2 only. The resulting SPDXlicense identifier is: GPL-2.0-onlySigned-off-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/net/nfc/Kconfig

8c0695e4 - NFC Digital: Add NFC-F technology support

Thu, 19 Sep 2013 15:55:28 +0000

NFC Digital: Add NFC-F technology supportThis adds polling support for NFC-F technology at 212 kbits/s and 424kbits/s. A user space application like neard can send type 3 tagcommands through the NFC core.Process flow for NFC-F detection is as follow:1 - The digital stack sends the SENSF_REQ command to the NFC device.2 - A peer device replies with a SENSF_RES response.3 - The digital stack notifies the NFC core of the presence of a target in the operation field and passes the target NFCID2.This also adds support for CRC calculation of type CRC-F. The CRCcalculation is handled by the digital stack if the NFC device doesn'tsupport it.Signed-off-by: Thierry Escande Signed-off-by: Samuel Ortiz List of files: /linux-6.15/net/nfc/Kconfig

2c66daec - NFC Digital: Add NFC-A technology support

Thu, 19 Sep 2013 15:55:27 +0000

NFC Digital: Add NFC-A technology supportThis adds support for NFC-A technology at 106 kbits/s. The stack candetect tags of type 1 and 2. There is no support for collisiondetection. Tags can be read and written by using a user spaceapplication or a daemon like neard.The flow of polling operations for NFC-A detection is as follow:1 - The digital stack sends the SENS_REQ command to the NFC device.2 - The NFC device receives a SENS_RES response from a peer device and passes it to the digital stack.3 - If the SENS_RES response identifies a type 1 tag, detection ends. NFC core is notified through nfc_targets_found().4 - Otherwise, the digital stack sets the cascade level of NFCID1 to CL1 and sends the SDD_REQ command.5 - The digital stack selects SEL_CMD and SEL_PAR according to the cascade level and sends the SDD_REQ command.4 - The digital stack receives a SDD_RES response for the cascade level passed in the SDD_REQ command.5 - The digital stack analyses (part of) NFCID1 and verify BCC.6 - The digital stack sends the SEL_REQ command with the NFCID1 received in the SDD_RES.6 - The peer device replies with a SEL_RES response7 - Detection ends if NFCID1 is complete. NFC core notified of new target by nfc_targets_found().8 - If NFCID1 is not complete, the cascade level is incremented (up to and including CL3) and the execution continues at step 5 to get the remaining bytes of NFCID1.Once target detection is done, type 1 and 2 tag commands must behandled by a user space application (i.e neard) through the NFC core.Responses for type 1 tag are returned directly to user space via NFCcore.Responses of type 2 commands are handled differently. The digital stackdoesn't analyse the type of commands sent through im_transceive() andmust differentiate valid responses from error ones.The response process flow is as follow:1 - If the response length is 16 bytes, it is a valid response of a READ command. the packet is returned to the NFC core through the callback passed to im_transceive(). Processing stops.2 - If the response is 1 byte long and is a ACK byte (0x0A), it is a valid response of a WRITE command for example. First packet byte is set to 0 for no-error and passed back to the NFC core. Processing stops.3 - Any other response is treated as an error and -EIO error code is returned to the NFC core through the response callback.Moreover, since the driver can't differentiate success response from aNACK response, the digital stack has to handle CRC calculation.Thus, this patch also adds support for CRC calculation. If the driverdoesn't handle it, the digital stack will calculate CRC and will add itto sent frames. CRC will also be checked and removed from receivedframes. Pointers to the correct CRC calculation functions are stored inthe digital stack device structure when a target is detected. Thisavoids the need to check the current target type for every call toim_transceive() and for every response received from a peer device.Signed-off-by: Thierry Escande Signed-off-by: Samuel Ortiz List of files: /linux-6.15/net/nfc/Kconfig

4b10884e - NFC: Digital Protocol stack implementation

Thu, 19 Sep 2013 15:55:25 +0000

NFC: Digital Protocol stack implementationThis is the initial commit of the NFC Digital Protocol stackimplementation.It offers an interface for devices that don't have an embedded NFCDigital protocol stack. The driver instantiates the digital stack bycalling nfc_digital_allocate_device(). Within the nfc_digital_opsstructure, the driver specifies a set of function pointers for driveroperations. These functions must be implemented by the driver and are:in_configure_hw:Hardware configuration for RF technology and communication framing ininitiator mode. This is a synchronous function.in_send_cmd:Initiator mode data exchange using RF technology and framing previouslyset with in_configure_hw. The peer response is returned throughcallback cb. If an io error occurs or the peer didn't reply within thespecified timeout (ms), the error code is passed back through the resppointer. This is an asynchronous function.tg_configure_hw:Hardware configuration for RF technology and communication framing intarget mode. This is a synchronous function.tg_send_cmd:Target mode data exchange using RF technology and framing previouslyset with tg_configure_hw. The peer next command is returned throughcallback cb. If an io error occurs or the peer didn't reply within thespecified timeout (ms), the error code is passed back through the resppointer. This is an asynchronous function.tg_listen:Put the device in listen mode waiting for data from the peer device.This is an asynchronous function.tg_listen_mdaa:If supported, put the device in automatic listen mode with modedetection and automatic anti-collision. In this mode, the deviceautomatically detects the RF technology and executes theanti-collision detection using the command responses specified inmdaa_params. The mdaa_params structure contains SENS_RES, NFCID1, andSEL_RES for 106A RF tech. NFCID2 and system code (sc) for 212F and424F. The driver returns the NFC-DEP ATR_REQ command through cb. Thedigital stack deducts the RF tech by analyzing the SoD of the framecontaining the ATR_REQ command. This is an asynchronous function.switch_rf:Turns device radio on or off. The stack does not call explicitlyswitch_rf to turn the radio on. A call to in|tg_configure_hw must turnthe device radio on.abort_cmd:Discard the last sent command.Then the driver registers itself against the digital stack by usingnfc_digital_register_device() which in turn registers the digital stackagainst the NFC core layer. The digital stack implements common NFCoperations like dev_up(), dev_down(), start_poll(), stop_poll(), etc.This patch is only a skeleton and NFC operations are just stubs.Signed-off-by: Thierry Escande Signed-off-by: Samuel Ortiz List of files: /linux-6.15/net/nfc/Kconfig

c204ea09 - NFC: Add missing RFKILL dependency for Kconfig

Fri, 26 Apr 2013 23:02:46 +0000

NFC: Add missing RFKILL dependency for KconfigSince the NFC subsystem gained RFKILL support, it needs to be ableto build properly with whatever option for RFKILL has been selected.on i386:net/built-in.o: In function `nfc_unregister_device':(.text+0x6a36d): undefined reference to `rfkill_unregister'net/built-in.o: In function `nfc_unregister_device':(.text+0x6a378): undefined reference to `rfkill_destroy'net/built-in.o: In function `nfc_register_device':(.text+0x6a493): undefined reference to `rfkill_alloc'net/built-in.o: In function `nfc_register_device':(.text+0x6a4a4): undefined reference to `rfkill_register'net/built-in.o: In function `nfc_register_device':(.text+0x6a4b3): undefined reference to `rfkill_destroy'net/built-in.o: In function `nfc_dev_up':(.text+0x6a8e8): undefined reference to `rfkill_blocked'when CONFIG_RFKILL=m but NFC is builtin.Reported-by: Randy Dunlap Acked-by: Randy Dunlap Signed-off-by: Marcel Holtmann Signed-off-by: Samuel Ortiz List of files: /linux-6.15/net/nfc/Kconfig

30cc4587 - NFC: Move LLCP code to the NFC top level diirectory

Fri, 26 Apr 2013 09:49:40 +0000

NFC: Move LLCP code to the NFC top level diirectoryAnd stop making it optional. LLCP is a fundamental part of the NFCspecifications and making it optional does not make much sense.Signed-off-by: Samuel Ortiz List of files: /linux-6.15/net/nfc/Kconfig

deccb2a2 - NFC: Remove CONFIG_EXPERIMENTAL

Tue, 23 Oct 2012 20:04:09 +0000

NFC: Remove CONFIG_EXPERIMENTALThis config item has not carried much meaning for a while now and isalmost always enabled by default. As agreed during the Linux kernelsummit, remove it.Acked-by: David S. Miller Signed-off-by: Kees Cook Signed-off-by: Samuel Ortiz List of files: /linux-6.15/net/nfc/Kconfig

8b8d2e08 - NFC: HCI support

Tue, 10 Apr 2012 17:43:06 +0000

NFC: HCI supportThis is an implementation of ETSI TS 102 622 specification.Many NFC chipsets use HCI as the host <-> target protocol on top of aserial link like i2c.Signed-off-by: Eric Lapuyade Signed-off-by: Samuel Ortiz Signed-off-by: John W. Linville List of files: /linux-6.15/net/nfc/Kconfig

d646960f - NFC: Initial LLCP support

Wed, 14 Dec 2011 15:43:12 +0000

NFC: Initial LLCP supportThis patch is an initial implementation for the NFC Logical Link Controlprotocol. It's also known as NFC peer to peer mode.This is a basic implementation as it lacks SDP (services DiscoveryProtocol), frames aggregation support, and frame rejecion parsing.Follow up patches will implement those missing features.This code has been tested against a Nexus S phone implementing LLCP 1.0.Signed-off-by: Samuel Ortiz Signed-off-by: John W. Linville List of files: /linux-6.15/net/nfc/Kconfig

6a2968aa - NFC: basic NCI protocol implementation

Sun, 18 Sep 2011 08:19:35 +0000

NFC: basic NCI protocol implementationThe NFC Controller Interface (NCI) is a standardcommunication protocol between an NFC Controller (NFCC)and a Device Host (DH), defined by the NFC Forum.Signed-off-by: Ilan Elias Signed-off-by: John W. Linville List of files: /linux-6.15/net/nfc/Kconfig

3e256b8f - NFC: add nfc subsystem core

Fri, 01 Jul 2011 22:31:33 +0000

NFC: add nfc subsystem coreThe NFC subsystem core is responsible for providing the device driverinterface. It is also responsible for providing an interface to the controloperations and data exchange.Signed-off-by: Lauro Ramos Venancio Signed-off-by: Aloisio Almeida Jr Signed-off-by: Samuel Ortiz Signed-off-by: John W. Linville List of files: /linux-6.15/net/nfc/Kconfig