blob: e309241e22d8c4809290d6e89c8cb7134fa61f57 [file] [log] [blame]
Sreelakshmi Gownipallicb8893d2016-10-19 16:02:34 -07001menu "Diag Support"
2
3config DIAG_CHAR
4 tristate "DIAG CHAR Interface Core"
5 default m
6 depends on USB_CONFIGFS_F_DIAG || USB_FUNCTION_DIAG || USB_QCOM_MAEMO
7 depends on ARCH_QCOM
8 depends on POWER_RESET_QCOM
9 select CRC_CCITT
10 help
11 Char driver interface for SoC Diagnostic information. The DIAG Char
12 driver provides diag forwarding to user space and SoC Peripherals.
13 This enables diagchar for maemo usb gadget or android usb gadget
14 based on config selected.
15
16config DIAG_OVER_USB
17 bool "Enable DIAG traffic to go over USB"
18 depends on DIAG_CHAR
19 depends on ARCH_QCOM
20 default y
21 help
22 Diag over USB enables sending DIAG traffic over a USB transport. When
23 the USB endpoints become available, the DIAG driver will enable Diag
24 traffic over USB. This allows for host side tools to parse and display
25 Diag traffic from the USB endpoint.
26
27config DIAGFWD_BRIDGE_CODE
28 bool "Enable QSC/9K DIAG traffic over SMUX/HSIC"
29 depends on DIAG_CHAR
30 depends on USB_QCOM_DIAG_BRIDGE || MSM_MHI
31 default y
32 help
33 SMUX/HSIC Transport Layer for DIAG Router. When the MHI/SMUX endpoints
34 become available, this bridge driver enables DIAG traffic over MHI
35 and SMUX.
36
37endmenu