diff options
author | Fabio Estevam <fabio.estevam@freescale.com> | 2015-11-04 08:13:00 -0200 |
---|---|---|
committer | Samuel Ortiz <sameo@linux.intel.com> | 2015-11-18 02:30:49 +0100 |
commit | 59df9bb25cf8a13443b8335a7a9013817c050b88 (patch) | |
tree | 0a06192ae1da3cc488f44039a4ea8d7891c2449a /drivers/nfc/s3fwrn5/i2c.c | |
parent | 7f151f1d8abb7d5930b49d4796b463dca1673cb7 (diff) | |
download | linux-next-59df9bb25cf8a13443b8335a7a9013817c050b88.tar.gz |
nxp-nci: i2c: Do not check specifically for -EREMOTEIO error
Function nxp_nci_i2c_write currently assumes in case of
I2C bus NACK that the NFC device is in stand-by mode and
will retry the I2C transaction after a pause. This assumes
that the first failed I2C transaction will wake-up the device.
This is done by checking on EREMOTEIO, which is wrong. According
to Documentation/i2c/fault-codes ENXIO shall be used. Unfortunately
the NOACK return code is currently inconsistent across various I2C
host controller drivers. So only check for the generic error case
instead.
This is a temporary fix. As soon as all I2C bus master drivers are
fixed to consistently return 'ENXIO', then we can do the specific
error check again.
Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
Diffstat (limited to 'drivers/nfc/s3fwrn5/i2c.c')
0 files changed, 0 insertions, 0 deletions