From: Shikha Singh <shikha.singh@st.com>
To: <sameo@linux.intel.com>, <aloisio.almeida@openbossa.org>,
<lauro.venancio@openbossa.org>, <linux-wireless@vger.kernel.org>,
<linux-nfc@lists.01.org>
Cc: <raunaque.quaiser@st.com>, <manoj.kumar@st.com>,
<sylvain.fidelis@st.com>, <patrick.sohn@st.com>,
<shikha.singh@st.com>, <MMS_MMY_Applications_SW@list.st.com>
Subject: [[linux-nfc] PATCH v4 1/3] NFC: digital: Add Type4A tags support
Date: Fri, 20 Nov 2015 04:49:55 -0500 [thread overview]
Message-ID: <1448012997-6000-2-git-send-email-shikha.singh@st.com> (raw)
In-Reply-To: <1448012997-6000-1-git-send-email-shikha.singh@st.com>
The definition of DIGITAL_PROTO_NFCA_RF_TECH is modified to support
ISO14443 Type4A tags. Without this change it is not possible to start
polling for ISO14443 Type4A tags from the initiator side.
Signed-off-by: Shikha Singh <shikha.singh@st.com>
---
net/nfc/digital_core.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/net/nfc/digital_core.c b/net/nfc/digital_core.c
index 23c2a11..dd9003f 100644
--- a/net/nfc/digital_core.c
+++ b/net/nfc/digital_core.c
@@ -20,7 +20,8 @@
#include "digital.h"
#define DIGITAL_PROTO_NFCA_RF_TECH \
- (NFC_PROTO_JEWEL_MASK | NFC_PROTO_MIFARE_MASK | NFC_PROTO_NFC_DEP_MASK)
+ (NFC_PROTO_JEWEL_MASK | NFC_PROTO_MIFARE_MASK | \
+ NFC_PROTO_NFC_DEP_MASK | NFC_PROTO_ISO14443_MASK)
#define DIGITAL_PROTO_NFCB_RF_TECH NFC_PROTO_ISO14443_B_MASK
--
1.8.2.1
next prev parent reply other threads:[~2015-11-20 9:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 9:49 [[linux-nfc] PATCH v4 0/3] *** ST95HF driver v4 *** Shikha Singh
2015-11-20 9:49 ` Shikha Singh [this message]
2015-11-20 9:49 ` [[linux-nfc] PATCH v4 2/3] driver: nfc: Add ST95HF NFC Transceiver support Shikha Singh
2015-11-20 9:49 ` [[linux-nfc] PATCH v4 3/3] DT: bindings: net: nfc: Add ST95HF binding doc Shikha Singh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1448012997-6000-2-git-send-email-shikha.singh@st.com \
--to=shikha.singh@st.com \
--cc=MMS_MMY_Applications_SW@list.st.com \
--cc=aloisio.almeida@openbossa.org \
--cc=lauro.venancio@openbossa.org \
--cc=linux-nfc@lists.01.org \
--cc=linux-wireless@vger.kernel.org \
--cc=manoj.kumar@st.com \
--cc=patrick.sohn@st.com \
--cc=raunaque.quaiser@st.com \
--cc=sameo@linux.intel.com \
--cc=sylvain.fidelis@st.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).