Home
last modified time | relevance | path

Searched +full:usb +full:- +full:a +full:- +full:connector (Results 1 – 25 of 290) sorted by relevance

12345678910>>...12

/Linux-v6.1/Documentation/devicetree/bindings/connector/
Dusb-connector.yaml1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/connector/usb-connector.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: USB Connector
10 - Rob Herring <robh@kernel.org>
13 A USB connector node represents a physical USB connector. It should be a child
14 of a USB interface controller or a separate node when it is attached to both
15 MUX and USB interface controller.
20 - enum:
[all …]
/Linux-v6.1/Documentation/devicetree/bindings/usb/
Dmediatek,musb.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/usb/mediatek,musb.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Min Guo <min.guo@mediatek.com>
15 pattern: '^usb@[0-9a-f]+$'
19 - enum:
20 - mediatek,mt8516-musb
21 - mediatek,mt2701-musb
22 - mediatek,mt7623-musb
[all …]
Dmediatek,mtu3.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/usb/mediatek,mtu3.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Chunfeng Yun <chunfeng.yun@mediatek.com>
14 - $ref: "usb-drd.yaml"
17 The DRD controller has a glue layer IPPC (IP Port Control), and its host is
23 - enum:
24 - mediatek,mt2712-mtu3
25 - mediatek,mt8173-mtu3
[all …]
Dwillsemi,wusb3801.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/usb/willsemi,wusb3801.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: WUSB3801 Type-C port controller DT bindings
10 The Will Semiconductor WUSB3801 is a USB Type-C port controller which
12 compatible with the USB Type-C Cable and Connector Specification v1.2.
15 - Samuel Holland <samuel@sholland.org>
20 - willsemi,wusb3801
28 connector:
[all …]
Drichtek,rt1719.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: "http://devicetree.org/schemas/usb/richtek,rt1719.yaml#"
5 $schema: "http://devicetree.org/meta-schemas/core.yaml#"
7 title: Richtek RT1719 sink-only Type-C PD controller bindings
10 - ChiYuan Huang <cy_huang@richtek.com>
13 The RT1719 is a sink-only USB Type-C contoller that complies with the latest
14 USB Type-C and PD standards. It does the USB Type-C detection including attach
15 and orientation. It integrates the physical layer of the USB BMC power
17 support for alternative interfaces of the Type-C specification.
[all …]
Dst,typec-stm32g0.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/usb/st,typec-stm32g0.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: STMicroelectronics STM32G0 USB Type-C PD controller
10 The STM32G0 MCU can be programmed to control Type-C connector(s) through I2C
11 typically using the UCSI protocol over I2C, with a dedicated alert
15 - Fabrice Gasnier <fabrice.gasnier@foss.st.com>
19 const: st,stm32g0-typec
27 connector:
[all …]
Drichtek,rt1711h.txt4 - compatible : Must be "richtek,rt1711h".
5 - reg : Must be 0x4e, it's slave address of RT1711H.
6 - interrupts : <a b> where a is the interrupt number and b represents an
9 Required sub-node:
10 - connector: The "usb-c-connector" attached to the tcpci chip, the bindings
11 of connector node are specified in
12 Documentation/devicetree/bindings/connector/usb-connector.yaml
18 interrupt-parent = <&gpio26>;
21 usb_con: connector {
22 compatible = "usb-c-connector";
[all …]
Drichtek,rt1711h.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: "http://devicetree.org/schemas/usb/richtek,rt1711h.yaml#"
5 $schema: "http://devicetree.org/meta-schemas/core.yaml#"
7 title: Richtek RT1711H Type-C Port Switch and Power Delivery controller
10 - Gene Chen <gene_chen@richtek.com>
13 The RT1711H is a USB Type-C controller that complies with the latest
14 USB Type-C and PD standards. It does the USB Type-C detection including attach
15 and orientation. It integrates the physical layer of the USB BMC power
17 support for alternative interfaces of the Type-C specification.
[all …]
Dmsm-hsusb.txt6 - compatible: Should contain "qcom,ehci-host"
7 - regs: offset and length of the register set in the memory map
8 - usb-phy: phandle for the PHY device
13 compatible = "qcom,ehci-host";
15 usb-phy = <&usb_otg>;
18 USB PHY with optional OTG:
21 - compatible: Should contain:
22 "qcom,usb-otg-ci" for chipsets with ChipIdea 45nm PHY
23 "qcom,usb-otg-snps" for chipsets with Synopsys 28nm PHY
25 - regs: Offset and length of the register set in the memory map
[all …]
Dmediatek,mt6360-tcpc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: "http://devicetree.org/schemas/usb/mediatek,mt6360-tcpc.yaml#"
5 $schema: "http://devicetree.org/meta-schemas/core.yaml#"
7 title: Mediatek MT6360 Type-C Port Switch and Power Delivery controller DT bindings
10 - ChiYuan Huang <cy_huang@richtek.com>
13 Mediatek MT6360 is a multi-functional device. It integrates charger, ADC, flash, RGB indicators,
15 This document only describes MT6360 Type-C Port Switch and Power Delivery controller.
20 - mediatek,mt6360-tcpc
25 interrupt-names:
[all …]
Dusb-drd.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/usb/usb-drd.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Generic USB OTG Controller
10 - Greg Kroah-Hartman <gregkh@linuxfoundation.org>
13 otg-rev:
15 Tells usb driver the release number of the OTG and EH supplement with
16 which the device and its descriptors are compliant, in binary-coded
18 features (HNP/SRP/ADP) is enabled. If ADP is required, otg-rev should be
[all …]
Dci-hdrc-usb2.txt1 * USB2 ChipIdea USB controller for ci13xxx
4 - compatible: should be one of:
5 "fsl,imx23-usb"
6 "fsl,imx27-usb"
7 "fsl,imx28-usb"
8 "fsl,imx6q-usb"
9 "fsl,imx6sl-usb"
10 "fsl,imx6sx-usb"
11 "fsl,imx6ul-usb"
12 "fsl,imx7d-usb"
[all …]
/Linux-v6.1/Documentation/driver-api/usb/
Dtypec.rst3 USB Type-C connector class
7 ------------
9 The typec class is meant for describing the USB Type-C ports in a system to the
14 The platforms are expected to register every USB Type-C port they have with the
15 class. In a normal case the registration will be done by a USB Type-C or PD PHY
16 driver, but it may be a driver for firmware interface such as UCSI, driver for
17 USB PD controller or even driver for Thunderbolt3 controller. This document
18 considers the component registering the USB Type-C ports with the class as "port
26 attributes are described in Documentation/ABI/testing/sysfs-class-typec.
29 --------------------
[all …]
Dtypec_bus.rst2 API for USB Type-C Alternate Mode drivers
6 ------------
9 Messages (VDM) as defined in USB Type-C and USB Power Delivery Specifications.
11 every alternate mode, so every alternate mode will need a custom driver.
13 USB Type-C bus allows binding a driver to the discovered partner alternate
16 :ref:`USB Type-C Connector Class <typec>` provides a device for every alternate
17 mode a port supports, and separate device for every alternate mode the partner
22 When a new partner alternate mode device is registered, it is linked to the
27 The port alternate mode devices are used as a proxy between the partner and the
36 ------
[all …]
/Linux-v6.1/drivers/usb/typec/
DKconfig1 # SPDX-License-Identifier: GPL-2.0
4 tristate "USB Type-C Support"
6 USB Type-C Specification defines a cable and connector for USB where
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
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.
16 USB Power Delivery Specification defines a protocol that can be used
[all …]
Dport-mapper.c1 // SPDX-License-Identifier: GPL-2.0
3 * USB Type-C Connector Class Port Mapping Utility
45 con_adev = ACPI_COMPANION(&arg->port->dev); in typec_port_match()
49 if (con_adev->pld_crc == adev->pld_crc) in typec_port_match()
50 component_match_add(&arg->port->dev, &arg->match, typec_port_compare, in typec_port_match()
59 if (!has_acpi_companion(&con->dev)) in typec_link_ports()
67 * REVISIT: Now each connector can have only a single component master. in typec_link_ports()
68 * So far only the USB ports connected to the USB Type-C connector share in typec_link_ports()
71 * the connector, every one of those needs to have its own component in typec_link_ports()
73 * the connector independently of the other components. That requires in typec_link_ports()
[all …]
/Linux-v6.1/drivers/extcon/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
3 tristate "External Connector Class (extcon) support"
5 Say Y here to enable external connector class (extcon) support.
9 cables attached. For example, an external connector of a device
10 may be used to connect an HDMI cable and a AC adaptor, and to
11 host USB ports. Many of 30-pin connectors including PDMI are
25 tristate "X-Power AXP288 EXTCON support"
29 Say Y here to enable support for USB peripheral detection
30 and USB MUX switching by X-Power AXP288 PMIC.
39 FSA9480 microUSB switch and accessory detector chip. The FSA9480 is a USB
[all …]
/Linux-v6.1/include/linux/
Dextcon.h1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * External Connector (extcon) framework
4 * - linux/include/linux/extcon.h for extcon consumer device driver.
26 #define EXTCON_TYPE_USB BIT(0) /* USB connector */
27 #define EXTCON_TYPE_CHG BIT(1) /* Charger connector */
28 #define EXTCON_TYPE_JACK BIT(2) /* Jack connector */
29 #define EXTCON_TYPE_DISP BIT(3) /* Display connector */
30 #define EXTCON_TYPE_MISC BIT(4) /* Miscellaneous connector */
37 /* USB external connector */
42 * Charging external connector
[all …]
/Linux-v6.1/Documentation/firmware-guide/acpi/
Dintel-pmc-mux.rst1 .. SPDX-License-Identifier: GPL-2.0
4 Intel North Mux-Agent
10 North Mux-Agent is a function of the Intel PMC firmware that is supported on
12 configuring the various USB Multiplexer/DeMultiplexers on the system. The
13 platforms that allow the mux-agent to be configured from the operating system
16 The North Mux-Agent (aka. Intel PMC Mux Control, or just mux-agent) driver
18 (drivers/platform/x86/intel_scu_ipc.c). The driver registers with the USB Type-C
19 Mux Class which allows the USB Type-C Controller and Interface drivers to
21 also registers with the USB Role Class in order to support both USB Host and
22 Device modes. The driver is located here: drivers/usb/typec/mux/intel_pmc_mux.c.
[all …]
/Linux-v6.1/Documentation/ABI/testing/
Dsysfs-driver-typec-displayport5 Shows the current DisplayPort configuration for the connector.
6 Valid values are USB, source and sink. Source means DisplayPort
14 USB [source] sink
18 Note. USB configuration does not equal to Exit Mode. It is
20 USB Type-C Standard. Functionally it equals to the situation
22 Documentation/ABI/testing/sysfs-bus-typec, and use file
29 VESA DisplayPort Alt Mode on USB Type-C Standard defines six
30 different pin assignments for USB Type-C connector that are
31 labeled A, B, C, D, E, and F. The supported pin assignments are
42 connector is actually configured.
[all …]
/Linux-v6.1/drivers/usb/roles/
DKconfig1 # SPDX-License-Identifier: GPL-2.0
4 tristate "USB Role Switch Support"
6 USB Role Switch is a device that can select the USB role - host or
7 device - for a USB port (connector). In most cases dual-role capable
8 USB controller will also represent the switch, but on some platforms
10 the USB connector between separate USB host and device controllers.
12 Say Y here if your USB connectors support both device and host roles.
19 tristate "Intel XHCI USB Role Switch"
22 Driver for the internal USB role switch for switching the USB data
26 To compile the driver as a module, choose M here: the module will
[all …]
/Linux-v6.1/include/linux/usb/
Dtypec_altmode.h1 /* SPDX-License-Identifier: GPL-2.0 */
7 #include <linux/usb/typec.h>
15 * struct typec_altmode - USB Type-C alternate mode device
19 * @vdo: VDO returned by Discover Modes USB PD command
40 dev_set_drvdata(&altmode->dev, data); in typec_altmode_set_drvdata()
45 return dev_get_drvdata(&altmode->dev); in typec_altmode_get_drvdata()
49 * struct typec_altmode_ops - Alternate mode specific operations vector
79 * These are the connector states (USB, Safe and Alt Mode) defined in USB Type-C
80 * Specification. SVID specific connector states are expected to follow and
84 TYPEC_STATE_SAFE, /* USB Safe State */
[all …]
/Linux-v6.1/Documentation/devicetree/bindings/phy/
Dphy-stm32-usbphyc.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/phy/phy-stm32-usbphyc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: STMicroelectronics STM32 USB HS PHY controller binding
11 The STM32 USBPHYC block contains a dual port High Speed UTMI+ PHY and a UTMI
22 |_ PHY port#2 ----| |________________
27 - Amelie Delaunay <amelie.delaunay@foss.st.com>
31 const: st,stm32mp1-usbphyc
42 "#address-cells":
[all …]
/Linux-v6.1/arch/arm/boot/dts/
Dstih410-b2260.dts1 // SPDX-License-Identifier: GPL-2.0-only
6 /dts-v1/;
8 #include <dt-bindings/gpio/gpio.h>
12 compatible = "st,stih410-b2260", "st,stih410";
15 stdout-path = &uart1;
29 compatible = "gpio-leds";
33 linux,default-trigger = "heartbeat";
34 default-state = "off";
40 default-state = "off";
46 default-state = "off";
[all …]
/Linux-v6.1/Documentation/devicetree/bindings/chrome/
Dgoogle,cros-ec-typec.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/chrome/google,cros-ec-typec.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Benson Leung <bleung@chromium.org>
11 - Prashant Malani <pmalani@chromium.org>
16 control the Type C ports. The node for this device should be under a
17 cros-ec node like google,cros-ec-spi.
21 const: google,cros-ec-typec
23 '#address-cells':
[all …]

12345678910>>...12