forked from Minki/linux
2c66daecc4
This adds support for NFC-A technology at 106 kbits/s. The stack can
detect tags of type 1 and 2. There is no support for collision
detection. Tags can be read and written by using a user space
application 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 response
7 - 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 be
handled by a user space application (i.e neard) through the NFC core.
Responses for type 1 tag are returned directly to user space via NFC
core.
Responses of type 2 commands are handled differently. The digital stack
doesn't analyse the type of commands sent through im_transceive() and
must 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 a
NACK response, the digital stack has to handle CRC calculation.
Thus, this patch also adds support for CRC calculation. If the driver
doesn't handle it, the digital stack will calculate CRC and will add it
to sent frames. CRC will also be checked and removed from received
frames. Pointers to the correct CRC calculation functions are stored in
the digital stack device structure when a target is detected. This
avoids the need to check the current target type for every call to
im_transceive() and for every response received from a peer device.
Signed-off-by: Thierry Escande <thierry.escande@linux.intel.com>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
34 lines
787 B
Plaintext
34 lines
787 B
Plaintext
#
|
|
# NFC sybsystem configuration
|
|
#
|
|
|
|
menuconfig NFC
|
|
depends on NET
|
|
depends on RFKILL || !RFKILL
|
|
tristate "NFC subsystem support"
|
|
default n
|
|
help
|
|
Say Y here if you want to build support for NFC (Near field
|
|
communication) devices.
|
|
|
|
To compile this support as a module, choose M here: the module will
|
|
be called nfc.
|
|
|
|
config NFC_DIGITAL
|
|
depends on NFC
|
|
select CRC_CCITT
|
|
tristate "NFC Digital Protocol stack support"
|
|
default n
|
|
help
|
|
Say Y if you want to build NFC digital protocol stack support.
|
|
This is needed by NFC chipsets whose firmware only implement
|
|
the NFC analog layer.
|
|
|
|
To compile this support as a module, choose M here: the module will
|
|
be called nfc_digital.
|
|
|
|
source "net/nfc/nci/Kconfig"
|
|
source "net/nfc/hci/Kconfig"
|
|
|
|
source "drivers/nfc/Kconfig"
|