diff options
| author | OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> | 2017-02-04 10:15:55 +0900 |
|---|---|---|
| committer | Samuel Ortiz <sameo@linux.intel.com> | 2017-04-01 23:04:29 +0200 |
| commit | 85a2566d70a851c85806f687b93a9559bb8a3b11 (patch) | |
| tree | 124a1b187a6a8833b4960c675c7246070fe6bb53 /drivers/nfc | |
| parent | 9728ee92f740acc65d54e6c62b9124cd0676cba9 (diff) | |
| download | linux-85a2566d70a851c85806f687b93a9559bb8a3b11.tar.gz linux-85a2566d70a851c85806f687b93a9559bb8a3b11.tar.bz2 linux-85a2566d70a851c85806f687b93a9559bb8a3b11.zip | |
nfc: Send same info for both of NFC_CMD_GET_DEVICE and NFC_EVENT_DEVICE_ADDED
Now, NFC_EVENT_DEVICE_ADDED doesn't send NFC_ATTR_RF_MODE. But
NFC_CMD_GET_DEVICE send.
To get NFC_ATTR_RF_MODE, we have to call NFC_CMD_GET_DEVICE just for
NFC_ATTR_RF_MODE when get NFC_EVENT_DEVICE_ADDED.
This fixes those inconsistent.
Signed-off-by: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
Diffstat (limited to 'drivers/nfc')
0 files changed, 0 insertions, 0 deletions