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

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