Home
last modified time | relevance | path

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

12345678910>>...17

/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/connector/
H A 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 …]
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/usb/
H A Dmediatek,musb.txt2 -------------------------------------------
5 - compatible : should be one of:
6 "mediatek,mt2701-musb"
8 followed by "mediatek,mtk-musb"
9 - reg : specifies physical base address and size of
11 - interrupts : interrupt used by musb controller
12 - interrupt-names : must be "mc"
13 - phys : PHY specifier for the OTG phy
14 - dr_mode : should be one of "host", "peripheral" or "otg",
15 refer to usb/generic.txt
[all …]
H A Detek,et7303.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: "http://devicetree.org/schemas/usb/etek,et7303.yaml#"
5 $schema: "http://devicetree.org/meta-schemas/core.yaml#"
7 title: Etek ET7303 Type-C Port controller DT bindings
10 - Wang Jie <dave.wang@rock-chips.com>
27 description: TCPC connected to USB controller to support dual-role switch.
30 - port@0
32 connector:
34 $ref: ../connector/usb-connector.yaml#
[all …]
H A Dhynetek,husb311.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: "http://devicetree.org/schemas/usb/hynetek,husb311.yaml#"
5 $schema: "http://devicetree.org/meta-schemas/core.yaml#"
7 title: Hynetek HUSB311 Type-C Port controller DT bindings
10 - Guenter Roeck <linux@roeck-us.net>
11 - Heikki Krogerus <heikki.krogerus@linux.intel.com>
28 description: TCPC connected to USB controller to support dual-role switch.
31 - port@0
33 connector:
[all …]
H A Dmaxim,max33359.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: "http://devicetree.org/schemas/usb/maxim,max33359.yaml#"
5 $schema: "http://devicetree.org/meta-schemas/core.yaml#"
7 title: Maxim TCPCI Type-C PD controller DT bindings
10 - Badhri Jagan Sridharan <badhri@google.com>
12 description: Maxim TCPCI Type-C PD controller
17 - maxim,max33359
25 connector:
27 $ref: ../connector/usb-connector.yaml#
[all …]
H A Dtypec-tcpci.txt2 ---------------------------------------------
5 - compatible: should be set one of following:
6 - "nxp,ptn5110" for NXP USB PD TCPC PHY IC ptn5110.
8 - reg: the i2c slave address of typec port controller device.
9 - interrupt-parent: the phandle to the interrupt controller which provides
11 - interrupts: interrupt specification for tcpci alert.
13 Required sub-node:
14 - connector: The "usb-c-connector" attached to the tcpci chip, the bindings
15 of connector node are specified in
16 Documentation/devicetree/bindings/connector/usb-connector.yaml
[all …]
H A Dfcs,fusb302.txt1 Fairchild FUSB302 Type-C Port controllers
4 - compatible : "fcs,fusb302"
5 - reg : I2C slave address
6 - interrupts : Interrupt specifier
8 Required sub-node:
9 - connector : The "usb-c-connector" attached to the FUSB302 IC. The bindings
10 of the connector node are specified in:
12 Documentation/devicetree/bindings/connector/usb-connector.yaml
17 fusb302: typec-portc@54 {
20 interrupt-parent = <&nmi_intc>;
[all …]
H A 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 …]
H A 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 …]
H A 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 …]
H A Dmediatek,mtu3.txt4 - compatible : should be "mediatek,<soc-model>-mtu3", "mediatek,mtu3",
5 soc-model is the name of SoC, such as mt8173, mt2712 etc,
8 - "mediatek,mt8173-mtu3"
9 - reg : specifies physical base address and size of the registers
10 - reg-names: should be "mac" for device IP and "ippc" for IP port control
11 - interrupts : interrupt used by the device IP
12 - power-domains : a phandle to USB power domain node to control USB's
14 - vusb33-supply : regulator of USB avdd3.3v
15 - clocks : a list of phandle + clock-specifier pairs, one for each
16 entry in clock-names
[all …]
H A 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 Device Tree Bindings
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 …]
H A Dti,hd3ss3220.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/usb/ti,hd3ss3220.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Biju Das <biju.das.jz@bp.renesas.com>
12 description: |-
13 HD3SS3220 is a USB SuperSpeed (SS) 2:1 mux with DRP port controller. The device provides Channel
14 Configuration (CC) logic and 5V VCONN sourcing for ecosystems implementing USB Type-C. The
30 SS data bus to the SS capable connector.
35 description: Super Speed (SS) MUX inputs connected to SS capable connector.
[all …]
H A 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 …]
/OK3568_Linux_fs/kernel/include/linux/
H A 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 */
43 * Charging external connector
[all …]
/OK3568_Linux_fs/kernel/Documentation/driver-api/usb/
H A 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
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 --------------------
36 "port0-partner". Full path to the device would be
[all …]
H A 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.
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
36 ------
43 space (See Documentation/ABI/testing/sysfs-class-typec). Port drivers should not
46 ``->vdm`` is the most important callback in the operation callbacks vector. It
52 in need to reconfigure the pins on the connector, the alternate mode driver
55 parameter. The bus driver will then configure the mux behind the connector using
[all …]
/OK3568_Linux_fs/kernel/Documentation/ABI/testing/
H A 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
42 connector is actually configured.
44 Note. As of VESA DisplayPort Alt Mode on USB Type-C Standard
[all …]
/OK3568_Linux_fs/kernel/drivers/usb/typec/
H A 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 …]
/OK3568_Linux_fs/kernel/Documentation/firmware-guide/acpi/
H A 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 …]
/OK3568_Linux_fs/kernel/drivers/extcon/
H A 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
11 host USB ports. Many of 30-pin connectors including PDMI are
33 tristate "X-Power AXP288 EXTCON support"
37 Say Y here to enable support for USB peripheral detection
38 and USB MUX switching by X-Power AXP288 PMIC.
47 FSA9480 microUSB switch and accessory detector chip. The FSA9480 is a USB
49 I2C and enables USB data, stereo and mono audio, video, microphone
[all …]
/OK3568_Linux_fs/kernel/arch/arm/boot/dts/
H A 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";
16 stdout-path = &uart1;
30 compatible = "gpio-leds";
34 linux,default-trigger = "heartbeat";
35 default-state = "off";
41 default-state = "off";
47 default-state = "off";
[all …]
/OK3568_Linux_fs/u-boot/arch/arm/dts/
H A Dstih410-b2260.dts9 /dts-v1/;
11 #include <dt-bindings/gpio/gpio.h>
15 compatible = "st,stih410-b2260", "st,stih410";
19 linux,stdout-path = &uart1;
20 stdout-path = &uart1;
36 compatible = "gpio-leds";
40 linux,default-trigger = "heartbeat";
41 default-state = "off";
47 default-state = "off";
53 default-state = "off";
[all …]
/OK3568_Linux_fs/kernel/include/linux/usb/
H A 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
41 dev_set_drvdata(&altmode->dev, data); in typec_altmode_set_drvdata()
46 return dev_get_drvdata(&altmode->dev); in typec_altmode_get_drvdata()
50 * struct typec_altmode_ops - Alternate mode specific operations vector
81 * These are the connector states (USB, Safe and Alt Mode) defined in USB Type-C
82 * Specification. SVID specific connector states are expected to follow and
86 TYPEC_STATE_SAFE, /* USB Safe State */
[all …]
/OK3568_Linux_fs/kernel/drivers/usb/roles/
H A 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
27 be called intel-xhci-usb-role-switch.

12345678910>>...17