blob: 631a6242b0112aec566b9df0916eb9b1d1552be5 [file] [log] [blame]
Sjur Braendeland9b271052010-03-30 13:56:30 +00001#
2# CAIF physical drivers
3#
4
Sjur Braendeland9b271052010-03-30 13:56:30 +00005comment "CAIF transport drivers"
6
7config CAIF_TTY
8 tristate "CAIF TTY transport driver"
Sjur Braendeland01eebb52010-06-26 11:31:28 +00009 depends on CAIF
Sjur Braendeland9b271052010-03-30 13:56:30 +000010 default n
11 ---help---
12 The CAIF TTY transport driver is a Line Discipline (ldisc)
13 identified as N_CAIF. When this ldisc is opened from user space
14 it will redirect the TTY's traffic into the CAIF stack.
Sjur Braendeland529d6da2010-06-29 00:08:21 -070015
16config CAIF_SPI_SLAVE
17 tristate "CAIF SPI transport driver for slave interface"
18 depends on CAIF
19 default n
20 ---help---
21 The CAIF Link layer SPI Protocol driver for Slave SPI interface.
22 This driver implements a platform driver to accommodate for a
23 platform specific SPI device. A sample CAIF SPI Platform device is
24 provided in Documentation/networking/caif/spi_porting.txt
25
26config CAIF_SPI_SYNC
27 bool "Next command and length in start of frame"
28 depends on CAIF_SPI_SLAVE
29 default n
30 ---help---
31 Putting the next command and length in the start of the frame can
32 help to synchronize to the next transfer in case of over or under-runs.
33 This option also needs to be enabled on the modem.