summaryrefslogtreecommitdiff
path: root/net/nfc/hci/Kconfig
diff options
context:
space:
mode:
authorEric Lapuyade <eric.lapuyade@intel.com>2012-04-10 19:43:07 +0200
committerJohn W. Linville <linville@tuxdriver.com>2012-04-12 15:10:35 -0400
commiteb738fe535ae8e44402c372ecc1321eee0552a09 (patch)
treee0308123ef489ed65ef52db74f52c3e0f6541a6f /net/nfc/hci/Kconfig
parent8b8d2e08bf0d50193931afd27482a59376b66b2b (diff)
NFC: SHDLC implementation
Most NFC HCI chipsets actually use a simplified HDLC link layer to carry HCI payloads. This implementation registers itself as an HCI device on behalf of the NFC driver. Signed-off-by: Eric Lapuyade <eric.lapuyade@intel.com> Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'net/nfc/hci/Kconfig')
-rw-r--r--net/nfc/hci/Kconfig8
1 files changed, 8 insertions, 0 deletions
diff --git a/net/nfc/hci/Kconfig b/net/nfc/hci/Kconfig
index c32d2d4a9635..17213a6362b4 100644
--- a/net/nfc/hci/Kconfig
+++ b/net/nfc/hci/Kconfig
@@ -6,3 +6,11 @@ config NFC_HCI
Say Y here if you want to build support for a kernel NFC HCI
implementation. This is mostly needed for devices that only process
HCI frames, like for example the NXP pn544.
+
+config NFC_SHDLC
+ depends on NFC_HCI
+ bool "SHDLC link layer for HCI based NFC drivers"
+ default n
+ ---help---
+ Say yes if you use an NFC HCI driver that requires SHDLC link layer.
+ If unsure, say N here.