Kconfig 4.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105
  1. # SPDX-License-Identifier: GPL-2.0
  2. menuconfig TYPEC
  3. tristate "USB Type-C Support"
  4. help
  5. USB Type-C Specification defines a cable and connector for USB where
  6. only one type of plug is supported on both ends, i.e. there will not
  7. be Type-A plug on one end of the cable and Type-B plug on the other.
  8. Determination of the host-to-device relationship happens through a
  9. specific Configuration Channel (CC) which goes through the USB Type-C
  10. cable. The Configuration Channel may also be used to detect optional
  11. Accessory Modes - Analog Audio and Debug - and if USB Power Delivery
  12. is supported, the Alternate Modes, where the connector is used for
  13. something else then USB communication.
  14. USB Power Delivery Specification defines a protocol that can be used
  15. to negotiate the voltage and current levels with the connected
  16. partners. USB Power Delivery allows higher voltages then the normal
  17. 5V, up to 20V, and current up to 5A over the cable. The USB Power
  18. Delivery protocol is also used to negotiate the optional Alternate
  19. Modes when they are supported. USB Power Delivery does not depend on
  20. USB Type-C connector, however it is mostly used together with USB
  21. Type-C connectors.
  22. USB Type-C and USB Power Delivery Specifications define a set of state
  23. machines that need to be implemented in either software or firmware.
  24. Simple USB Type-C PHYs, for example USB Type-C Port Controller
  25. Interface Specification compliant "Port Controllers" need the state
  26. machines to be handled in the OS, but stand-alone USB Type-C and Power
  27. Delivery controllers handle the state machines inside their firmware.
  28. The USB Type-C and Power Delivery controllers usually function
  29. autonomously, and do not necessarily require drivers.
  30. Enable this configurations option if you have USB Type-C connectors on
  31. your system and 1) you know your USB Type-C hardware requires OS
  32. control (a driver) to function, or 2) if you need to be able to read
  33. the status of the USB Type-C ports in your system, or 3) if you need
  34. to be able to swap the power role (decide are you supplying or
  35. consuming power over the cable) or data role (host or device) when
  36. both roles are supported.
  37. For more information, see the kernel documentation for USB Type-C
  38. Connector Class API (Documentation/driver-api/usb/typec.rst)
  39. <https://www.kernel.org/doc/html/latest/driver-api/usb/typec.html>
  40. and ABI (Documentation/ABI/testing/sysfs-class-typec).
  41. if TYPEC
  42. source "drivers/usb/typec/tcpm/Kconfig"
  43. source "drivers/usb/typec/ucsi/Kconfig"
  44. config TYPEC_HD3SS3220
  45. tristate "TI HD3SS3220 Type-C DRP Port controller driver"
  46. depends on I2C
  47. depends on USB_ROLE_SWITCH
  48. help
  49. Say Y or M here if your system has TI HD3SS3220 Type-C DRP Port
  50. controller driver.
  51. If you choose to build this driver as a dynamically linked module, the
  52. module will be called hd3ss3220.ko.
  53. config TYPEC_TPS6598X
  54. tristate "TI TPS6598x USB Power Delivery controller driver"
  55. depends on I2C
  56. depends on REGMAP_I2C
  57. depends on USB_ROLE_SWITCH || !USB_ROLE_SWITCH
  58. help
  59. Say Y or M here if your system has TI TPS65982 or TPS65983 USB Power
  60. Delivery controller.
  61. If you choose to build this driver as a dynamically linked module, the
  62. module will be called tps6598x.ko.
  63. config TYPEC_STUSB160X
  64. tristate "STMicroelectronics STUSB160x Type-C controller driver"
  65. depends on USB_ROLE_SWITCH || !USB_ROLE_SWITCH
  66. depends on I2C
  67. select REGMAP_I2C
  68. help
  69. Say Y or M here if your system has STMicroelectronics STUSB160x
  70. Type-C port controller.
  71. If you choose to build this driver as a dynamically linked module, the
  72. module will be called stusb160x.ko.
  73. config TYPEC_QCOM_PMIC
  74. tristate "Qualcomm PMIC USB Type-C driver"
  75. depends on ARCH_QCOM || COMPILE_TEST
  76. depends on USB_ROLE_SWITCH || !USB_ROLE_SWITCH
  77. help
  78. Driver for supporting role switch over the Qualcomm PMIC. This will
  79. handle the USB Type-C role and orientation detection reported by the
  80. QCOM PMIC if the PMIC has the capability to handle USB Type-C
  81. detection.
  82. It will also enable the VBUS output to connected devices when a
  83. DFP connection is made.
  84. source "drivers/usb/typec/mux/Kconfig"
  85. source "drivers/usb/typec/altmodes/Kconfig"
  86. endif # TYPEC