Searched +full:usb +full:- +full:a +full:- +full:connector (Results 1 – 25 of 214) sorted by relevance
123456789
/Linux-v5.10/Documentation/devicetree/bindings/connector/ |
D | usb-connector.yaml | 1 # 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-v5.10/Documentation/devicetree/bindings/usb/ |
D | mediatek,musb.txt | 2 ------------------------------------------- 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 …]
|
D | richtek,rt1711h.txt | 4 - 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 …]
|
D | msm-hsusb.txt | 6 - 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 …]
|
D | generic.txt | 1 Generic USB Properties 4 - maximum-speed: tells USB controllers we want to work up to a certain 5 speed. Valid arguments are "super-speed-plus", 6 "super-speed", "high-speed", "full-speed" and 7 "low-speed". In case this isn't passed via DT, USB 10 - dr_mode: tells Dual-Role USB controllers that we want to work on a 13 passed via DT, USB DRD controllers should default to 15 - phy_type: tells USB controllers that we want to configure the core to support 16 a UTMI+ PHY with an 8- or 16-bit interface if UTMI+ is 18 In case this isn't passed via DT, USB controllers should [all …]
|
D | mediatek,mt6360-tcpc.yaml | 1 # 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 …]
|
D | mediatek,mtu3.txt | 4 - 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 …]
|
D | ti,hd3ss3220.yaml | 1 # 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 15 HD3SS3220 can be configured as a Downstream Facing Port (DFP), Upstream Facing Port (UFP) or a 30 SS data bus to the SS capable connector. [all …]
|
D | ci-hdrc-usb2.txt | 1 * 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-v5.10/Documentation/driver-api/usb/ |
D | typec.rst | 3 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 …]
|
D | typec_bus.rst | 2 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-v5.10/drivers/usb/typec/ |
D | Kconfig | 1 # 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 …]
|
D | mux.c | 1 // SPDX-License-Identifier: GPL-2.0 3 * USB Type-C Multiplexer/DeMultiplexer Switch support 16 #include <linux/usb/typec_mux.h> 29 return strcmp(name + (name_len - suffix_len), suffix) == 0; in dev_name_ends_with() 34 return dev_fwnode(dev) == fwnode && dev_name_ends_with(dev, "-switch"); in switch_fwnode_match() 48 return dev ? to_typec_switch(dev) : ERR_PTR(-EPROBE_DEFER); in typec_switch_match() 52 * fwnode_typec_switch_get - Find USB Type-C orientation switch 55 * Finds a switch linked with @dev. Returns a reference to the switch on 57 * ERR_PTR(-EPROBE_DEFER) when a connection was found but the switch 64 sw = fwnode_connection_find_match(fwnode, "orientation-switch", NULL, in fwnode_typec_switch_get() [all …]
|
/Linux-v5.10/include/linux/ |
D | extcon.h | 1 /* 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-v5.10/Documentation/ABI/testing/ |
D | sysfs-driver-typec-displayport | 5 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-v5.10/drivers/extcon/ |
D | Kconfig | 1 # 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 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 [all …]
|
/Linux-v5.10/Documentation/firmware-guide/acpi/ |
D | intel-pmc-mux.rst | 1 .. 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-v5.10/drivers/usb/roles/ |
D | Kconfig | 1 # 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-v5.10/include/linux/usb/ |
D | typec_altmode.h | 1 /* 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-v5.10/arch/arm/boot/dts/ |
D | stih410-b2260.dts | 1 // 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 …]
|
/Linux-v5.10/drivers/usb/typec/ucsi/ |
D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0 4 tristate "USB Type-C Connector System Software Interface driver" 7 USB Type-C Connector System Software Interface (UCSI) is a 9 control the USB Type-C ports. On UCSI system the USB Type-C ports 13 that are equipped with Embedded Controller and USB Type-C ports. 21 https://www.intel.com/content/www/us/en/io/universal-serial-bus/usb-type-c-ucsi-spec.html 23 To compile the driver as a module, choose M here: the module will be 32 This driver enables UCSI support on platforms that expose a 33 Cypress CCGx Type-C controller over I2C interface. 35 To compile the driver as a module, choose M here: the module will be [all …]
|
/Linux-v5.10/Documentation/devicetree/bindings/chrome/ |
D | google,cros-ec-typec.yaml | 1 # 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 connector: [all …]
|
/Linux-v5.10/Documentation/input/devices/ |
D | xpad.rst | 2 xpad - Linux USB driver for Xbox compatible controllers 5 This driver exposes all first-party and third-party Xbox compatible 6 controllers. It has a long history and has enjoyed considerable usage 25 - if you are using a known controller 26 - if you are using a known dance pad 27 - if using an unknown device (one not listed below), what you set in the 28 module configuration for "Map D-PAD to buttons rather than axes for unknown 33 If you said Y it will map the d-pad to buttons, which is needed for dance 36 dpad_to_buttons has no effect for known pads. A erroneous commit message 43 ------------------ [all …]
|
/Linux-v5.10/Documentation/x86/ |
D | earlyprintk.rst | 1 .. SPDX-License-Identifier: GPL-2.0 7 Mini-HOWTO for using the earlyprintk=dbgp boot option with a 8 USB2 Debug port key and a debug cable, on x86 systems. 10 You need two computers, the 'USB debug key' special gadget and 11 two USB cables, connected like this:: 13 [host/target] <-------> [USB debug key] <-------> [client/console] 18 a) Host/target system needs to have USB debug port capability. 20 You can check this capability by looking at a 'Debug port' bit in 21 the lspci -vvv output:: 23 # lspci -vvv [all …]
|
/Linux-v5.10/drivers/usb/core/ |
D | hub.h | 1 /* SPDX-License-Identifier: GPL-2.0 */ 3 * usb hub driver head file 14 #include <linux/usb.h> 15 #include <linux/usb/ch11.h> 16 #include <linux/usb/hcd.h> 17 #include "usb.h" 39 unsigned long removed_bits[1]; /* ports with a "removed" 48 #if USB_MAXCHILDREN > 31 /* 8*sizeof(unsigned long) - 1 */ 79 * struct usb port - kernel's representation of a usb port 80 * @child: usb device attached to the port [all …]
|
123456789