summaryrefslogtreecommitdiff
path: root/drivers
diff options
context:
space:
mode:
authorLinux Build Service Account <lnxbuild@localhost>2018-10-16 13:39:19 -0700
committerGerrit - the friendly Code Review server <code-review@localhost>2018-10-16 13:39:17 -0700
commit14ca49a1a44c4c07b8040fcfdb9671d21d5df06d (patch)
tree734db24da7c513ad1eb97459113d7556a8dd29d0 /drivers
parent78e9e3713fec5b12fbb35d12c565212de3b64cf5 (diff)
parentc0517fff87ff495136bb7d9a5e2588cb4f0c4ac1 (diff)
Merge "msm-auto: defconfig: Enable USB_QCOM_IPC_BRIDGE config"
Diffstat (limited to 'drivers')
-rw-r--r--drivers/usb/misc/Kconfig6
1 files changed, 4 insertions, 2 deletions
diff --git a/drivers/usb/misc/Kconfig b/drivers/usb/misc/Kconfig
index 278df845f066..b8f3e4199e20 100644
--- a/drivers/usb/misc/Kconfig
+++ b/drivers/usb/misc/Kconfig
@@ -287,12 +287,14 @@ config USB_QCOM_IPC_BRIDGE
Say Y here if you have a QTI modem device connected via USB that
will be bridged in kernel space. This driver works as a transport
layer for IPC router module that enables communication between
- APPS processor and MODEM processor.
+ APPS processor and MODEM processor. This config depends on
+ USB_QCOM_DIAG_BRIDGE because the core USB support for the transports
+ of both diag and IPC messages is in the same driver. Select this
+ config manually if you want to compile HSIC transport IPC router.
config USB_QCOM_DIAG_BRIDGE
tristate "USB QTI diagnostic bridge driver"
depends on USB
- select USB_QCOM_IPC_BRIDGE
help
Say Y here if you have a QTI modem device connected via USB that
will be bridged in kernel space. This driver communicates with the