kernel.git/drivers/nfc/trf7970a.c, branch linux-4.2.y

NFC: trf7970a: Handle extra byte in response to Type 5 RMB commands

2015-06-08T21:16:31Z

The current versions of the trf7970a has an erratum where it returns an extra byte in the response to 'Read Multiple Block' (RMB) commands. This command is issued to Type 5 tags (i.e., ISO/IEC 15693 tags) by the neard daemon. To handle this, define a new Device Tree property, 't5t-rmb-extra-byte-quirk', which indicates that the associated trf7970a device has this erratum. The trf7970a device driver will then ensure that the response length to RMB commands is reduced by one byte (for devices with the erratum). Signed-off-by: Mark A. Greer Signed-off-by: Samuel Ortiz

NFC / PM: Replace CONFIG_PM_RUNTIME with CONFIG_PM

2014-12-15T14:12:21Z

After commit b2b49ccbdd54 (PM: Kconfig: Set PM_RUNTIME if PM_SLEEP is selected) PM_RUNTIME is always set if PM is set, so #ifdef blocks depending on CONFIG_PM_RUNTIME may now be changed to depend on CONFIG_PM. Replace CONFIG_PM_RUNTIME with CONFIG_PM in drivers/nfc/trf7970a.c. Signed-off-by: Rafael J. Wysocki

NFC: trf7970a: Unlock mutex before exiting _trf7970a_tg_listen()

2014-09-23T22:28:23Z

The recently added _trf7970a_tg_listen() routine has some return paths that don't unlock the mutex that is locked when the routine is entered. Fix this by always unlocking the mutex before returning. Signed-off-by: Mark A. Greer Signed-off-by: Samuel Ortiz

NFC: trf7970a: Unlock mutex before exiting trf7970a_irq()

2014-09-23T22:28:23Z

Recent changes to trf7970a_irq() added a couple return paths that don't unlock the mutex that is locked when the routine is entered. Fix this by ensuring the mutex is always unlocked before returning. Signed-off-by: Mark A. Greer Signed-off-by: Samuel Ortiz

NFC: trf7970a: Remove unnecessary local variable initialization

2014-09-23T22:28:23Z

There is no need to initialize the 'ret' variable in trf7970a_resume(). Signed-off-by: Mark A. Greer Signed-off-by: Samuel Ortiz

NFC: trf7970a: Remove useless local variable

2014-09-23T22:28:22Z

The trf7970a_suspend() routine always returns zero so don't use a local return variable to hold the return value. This fixes up a smatch warning. Signed-off-by: Mark A. Greer Signed-off-by: Samuel Ortiz

NFC: trf7970a: Add Target Mode Detection Support

2014-09-07T21:13:45Z

Add the ability to detect the mode (i.e., RF technology) used by the initiator. The RF technology that was detected can be retrieved by calling the 'tg_get_rf_tech' driver hook. Signed-off-by: Mark A. Greer Signed-off-by: Samuel Ortiz

NFC: trf7970a: Add Target Mode Support

2014-09-07T21:13:45Z

Add target mode support to the trf7970a NFC driver. This effectively enables full Peer-to-Peer support. To handle changing framing between sending a response frame and receiving the subsequent request frame, most of the framing changes take effect in the interrupt handler and not in trf7970a_tg_config_framing(). Signed-off-by: Mark A. Greer Signed-off-by: Samuel Ortiz

NFC: trf7970a: Handle timeout values of zero

2014-09-07T21:13:45Z

The digital layer can try to send a command with a timeout value of zero (e.g., digital_tg_send_psl_res(). The zero value is used as a flag to indicate that the driver should not expect a response. To handle this, the driver sets an internal timer because it should still get an interrupt with the TX bit set in the IRQ Status Register. When it gets that interrupt, it returns a return value of '0'. If it doesn't get the interrupt before timing out, it returns ETIMEDOUT as usual. Signed-off-by: Mark A. Greer Signed-off-by: Samuel Ortiz

NFC: trf7970a: Cancel timer when error encountered

2014-09-07T21:13:45Z

Some paths leave a timer still running when trf7970a_send_err_upstream() is called. This can cause a timeout to occur in a subsequent transaction making it fail. Fix this by ensuring there is no timer running before sending an error upstream. Signed-off-by: Mark A. Greer Signed-off-by: Samuel Ortiz