Kconfig 4.1 KB

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