| 1 | # |
| 2 | # CAIF physical drivers |
| 3 | # |
| 4 | |
| 5 | comment "CAIF transport drivers" |
| 6 | |
| 7 | config CAIF_TTY |
| 8 | tristate "CAIF TTY transport driver" |
| 9 | depends on CAIF && TTY |
| 10 | 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. |
| 15 | |
| 16 | config CAIF_SPI_SLAVE |
| 17 | tristate "CAIF SPI transport driver for slave interface" |
| 18 | depends on CAIF && HAS_DMA |
| 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 | |
| 26 | config 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. |
| 34 | |
| 35 | config CAIF_HSI |
| 36 | tristate "CAIF HSI transport driver" |
| 37 | depends on CAIF |
| 38 | default n |
| 39 | ---help--- |
| 40 | The caif low level driver for CAIF over HSI. |
| 41 | Be aware that if you enable this then you also need to |
| 42 | enable a low-level HSI driver. |
| 43 | |
| 44 | config CAIF_VIRTIO |
| 45 | tristate "CAIF virtio transport driver" |
| 46 | depends on CAIF && HAS_DMA |
| 47 | select VHOST_RING |
| 48 | select VIRTIO |
| 49 | select GENERIC_ALLOCATOR |
| 50 | default n |
| 51 | ---help--- |
| 52 | The caif driver for CAIF over Virtio. |
| 53 | |
| 54 | if CAIF_VIRTIO |
| 55 | source "drivers/vhost/Kconfig" |
| 56 | endif |