linux.git/drivers/nfc/pn533, branch v5.8

treewide: replace '---help---' in Kconfig files with 'help'

2020-06-13T16:57:21+00:00

Since commit 84af7a6194e4 ("checkpatch: kconfig: prefer 'help' over
'---help---'"), the number of '---help---' has been gradually
decreasing, but there are still more than 2400 instances.

This commit finishes the conversion. While I touched the lines,
I also fixed the indentation.

There are a variety of indentation styles found.

  a) 4 spaces + '---help---'
  b) 7 spaces + '---help---'
  c) 8 spaces + '---help---'
  d) 1 space + 1 tab + '---help---'
  e) 1 tab + '---help---'    (correct indentation)
  f) 1 tab + 1 space + '---help---'
  g) 1 tab + 2 spaces + '---help---'

In order to convert all of them to 1 tab + 'help', I ran the
following commend:

  $ find . -name 'Kconfig*' | xargs sed -i 's/^[[:space:]]*---help---/\thelp/'

Signed-off-by: Masahiro Yamada

Merge ra.kernel.org:/pub/scm/linux/kernel/git/netdev/net

2020-01-19T21:10:04+00:00

nfc: No need to set .owner platform_driver_register

2020-01-14T19:58:11+00:00

the i2c_add_driver will set the .owner to THIS_MODULE

Signed-off-by: Tian Tao 
Signed-off-by: David S. Miller

NFC: pn533: fix bulk-message timeout

2020-01-14T02:50:18+00:00

The driver was doing a synchronous uninterruptible bulk-transfer without
using a timeout. This could lead to the driver hanging on probe due to a
malfunctioning (or malicious) device until the device is physically
disconnected. While sleeping in probe the driver prevents other devices
connected to the same hub from being added to (or removed from) the bus.

An arbitrary limit of five seconds should be more than enough.

Fixes: dbafc28955fa ("NFC: pn533: don't send USB data off of the stack")
Signed-off-by: Johan Hovold 
Reviewed-by: Greg Kroah-Hartman 
Signed-off-by: Jakub Kicinski

nfc: pn533: pn533_phy_ops dev_[up, down] return int

2019-11-13T20:15:03+00:00

Change dev_up and dev_down functions of struct pn533_phy_ops to return
int. This way the pn533 core can report errors in the phy layer to upper
layers.
The only user of this is currently uart.c and it is changed to report
the error of a possibly failing call to serdev_device_open.

Reported-by: coverity-bot 
Addresses-Coverity-ID: 1487395 ("Error handling issues")
Fixes: c656aa4c27b1 ("nfc: pn533: add UART phy driver")
Signed-off-by: Lars Poeschel 
Signed-off-by: David S. Miller

nfc: pn532_uart: Make use of pn532 autopoll

2019-10-30T04:05:26+00:00

This switches the pn532 UART phy driver from manually polling to the new
autopoll mechanism.

Cc: Johan Hovold 
Signed-off-by: Lars Poeschel 
Signed-off-by: David S. Miller

nfc: pn533: Add autopoll capability

2019-10-30T04:05:26+00:00

pn532 devices support an autopoll command, that lets the chip
automatically poll for selected nfc technologies instead of manually
looping through every single nfc technology the user is interested in.
This is faster and less cpu and bus intensive than manually polling.
This adds this autopoll capability to the pn533 driver.

Cc: Johan Hovold 
Cc: David Miller 
Signed-off-by: Lars Poeschel 
Signed-off-by: David S. Miller

nfc: pn533: add UART phy driver

2019-10-30T04:05:26+00:00

This adds the UART phy interface for the pn533 driver.
The pn533 driver can be used through UART interface this way.
It is implemented as a serdev device.

Cc: Johan Hovold 
Cc: Claudiu Beznea 
Cc: David Miller 
Signed-off-by: Lars Poeschel 
Signed-off-by: David S. Miller

nfc: pn533: Split pn533 init & nfc_register

2019-10-30T04:05:26+00:00

There is a problem in the initialisation and setup of the pn533: It
registers with nfc too early. It could happen, that it finished
registering with nfc and someone starts using it. But setup of the pn533
is not yet finished. Bad or at least unintended things could happen.
So I split out nfc registering (and unregistering) to seperate functions
that have to be called late in probe then.
i2c requires a bit more love: i2c requests an irq in it's probe
function. 'Commit 32ecc75ded72 ("NFC: pn533: change order operations in
dev registation")' shows, this can not happen too early. An irq can be
served before structs are fully initialized. The way chosen to prevent
this is to request the irq after nfc_alloc_device initialized the
structs, but before nfc_register_device. So there is now this
pn532_i2c_nfc_alloc function.

Cc: Johan Hovold 
Cc: Claudiu Beznea 
Cc: Jakub Kicinski 
Signed-off-by: Lars Poeschel 
Signed-off-by: David S. Miller

nfc: pn533: Add dev_up/dev_down hooks to phy_ops

2019-10-30T04:05:26+00:00

This adds hooks for dev_up and dev_down to the phy_ops. They are
optional.
The idea is to inform the phy driver when the nfc chip is really going
to be used. When it is not used, the phy driver can suspend it's
interface to the nfc chip to save some power. The nfc chip is considered
not in use before dev_up and after dev_down.

Cc: Johan Hovold 
Signed-off-by: Lars Poeschel 
Signed-off-by: David S. Miller