Home
last modified time | relevance | path

Searched full:xhci (Results 1 – 25 of 162) sorted by relevance

1234567

/freebsd-src/sys/contrib/device-tree/Bindings/usb/
H A Drenesas,usb-xhci.yaml4 $id: http://devicetree.org/schemas/usb/renesas,usb-xhci.yaml#
7 title: Renesas USB xHCI controllers
18 - renesas,xhci-r8a7742 # RZ/G1H
19 - renesas,xhci-r8a7743 # RZ/G1M
20 - renesas,xhci-r8a7744 # RZ/G1N
21 - renesas,xhci-r8a7790 # R-Car H2
22 - renesas,xhci-r8a7791 # R-Car M2-W
23 - renesas,xhci-r8a7793 # R-Car M2-N
24 - const: renesas,rcar-gen2-xhci # R-Car Gen2 and RZ/G1
27 - renesas,xhci-r8a774a1 # RZ/G2M
[all …]
H A Dgeneric-xhci.yaml4 $id: http://devicetree.org/schemas/usb/generic-xhci.yaml#
7 title: USB xHCI Controller
15 - description: Generic xHCI device
16 const: generic-xhci
20 - marvell,armada3700-xhci
21 - marvell,armada-375-xhci
22 - marvell,armada-380-xhci
23 - marvell,armada-8k-xhci
24 - const: generic-xhci
28 - brcm,bcm2711-xhci
[all …]
H A Dmediatek,mtk-xhci.yaml5 $id: http://devicetree.org/schemas/usb/mediatek,mtk-xhci.yaml#
8 title: MediaTek USB3 xHCI
14 - $ref: usb-xhci.yaml
18 case 1: only supports xHCI driver;
19 case 2: supports dual-role mode, and the host is based on xHCI driver.
26 - mediatek,mt2701-xhci
27 - mediatek,mt2712-xhci
28 - mediatek,mt7622-xhci
29 - mediatek,mt7623-xhci
30 - mediatek,mt7629-xhci
[all...]
H A Dusb-xhci.txt1 USB xHCI controllers
6 - "generic-xhci" for generic XHCI device
7 - "marvell,armada3700-xhci" for Armada 37xx SoCs
8 - "marvell,armada-375-xhci" for Armada 375 SoCs
9 - "marvell,armada-380-xhci" for Armada 38x SoCs
10 - "brcm,bcm7445-xhci" for Broadcom STB SoCs with XHCI
11 - "xhci-platform" (deprecated)
17 - reg: should contain address and length of the standard XHCI
19 - interrupts: one XHCI interrupt should be described here.
38 compatible = "generic-xhci";
H A Dmediatek,mtk-xhci.txt1 MT8173 xHCI
5 There are two scenarios: the first one only supports xHCI driver;
6 the second one supports dual-role mode, and the host is based on xHCI
10 1st: only supports xHCI driver
14 - compatible : should be "mediatek,<soc-model>-xhci", "mediatek,mtk-xhci",
16 "mediatek,mtk-xhci" compatible string, you need SoC specific ones in
18 - "mediatek,mt8173-xhci"
20 - reg-names: should be "mac" for xHCI MAC and "ippc" for IP port control
41 of the USB wakeup glue layer between xHCI and SPM; it depends on
61 compatible = "mediatek,mt8173-xhci";
[all …]
H A Dnvidia,tegra234-xusb.yaml7 title: NVIDIA Tegra234 xHCI controller
14 The Tegra xHCI controller supports both USB2 and USB3 interfaces exposed by
15 the Tegra XUSB pad controller. The xHCI controller controls up to eight
24 - description: xHCI host registers
36 - description: xHCI host interrupt
79 the USB pads used by the XHCI controller
112 - $ref: usb-xhci.yaml
H A Dmediatek,mtu3.yaml18 based on xHCI.
174 layer between xHCI and SPM, the field should always be 3 cells long.
208 $ref: /schemas/usb/mediatek,mtk-xhci.yaml#
210 The xhci should be added as subnode to mtu3 as shown in the following
257 xhci: usb@11270000 {
258 compatible = "mediatek,mt8173-xhci", "mediatek,mtk-xhci";
290 compatible = "mediatek,mt2712-xhci", "mediatek,mtk-xhci";
327 compatible = "mediatek,mt8183-xhci", "mediate
[all...]
H A Dcdns,usb3.yaml19 - description: XHCI Host controller registers
25 - const: xhci
31 - description: XHCI host controller interrupt
35 cleared by xhci core, this interrupt is optional
103 reg-names = "otg", "xhci", "dev";
H A Dnvidia,tegra194-xusb.yaml7 title: NVIDIA Tegra194 xHCI controller
13 description: The Tegra xHCI controller supports both USB2 and USB3 interfaces
22 - description: base and length of the xHCI host registers
32 - description: xHCI host interrupt
75 the USB pads used by the XHCI controller
127 - $ref: usb-xhci.yaml
H A Dnvidia,tegra186-xusb.yaml7 title: NVIDIA Tegra186 xHCI controller
13 description: The Tegra xHCI controller supports both USB2 and USB3 interfaces
22 - description: base and length of the xHCI host registers
32 - description: xHCI host interrupt
75 the USB pads used by the XHCI controller
126 - $ref: usb-xhci.yaml
H A Dhisilicon,histb-xhci.txt1 HiSilicon STB xHCI
3 The device node for HiSilicon STB xHCI host controller
6 - compatible: should be "hisilicon,hi3798cv200-xhci"
33 compatible = "hisilicon,hi3798cv200-xhci";
H A Dnvidia,tegra124-xusb.yaml7 title: NVIDIA Tegra124 xHCI controller
13 description: The Tegra xHCI controller supports both USB2 and USB3 interfaces
30 - description: base and length of the xHCI host registers
42 - description: xHCI host interrupt
88 the USB pads used by the XHCI controller
133 - $ref: usb-xhci.yaml
H A Dnvidia,tegra210-xusb.yaml7 title: NVIDIA Tegra210 xHCI controller
13 description: The Tegra xHCI controller supports both USB2 and USB3 interfaces
22 - description: base and length of the xHCI host registers
34 - description: xHCI host interrupt
80 the USB pads used by the XHCI controller
133 - $ref: usb-xhci.yaml
H A Dnvidia,tegra124-xusb.txt1 NVIDIA Tegra xHCI controller
4 The Tegra xHCI controller supports both USB2 and USB3 interfaces exposed by
14 - reg: Must contain the base and length of the xHCI host registers, XUSB FPCI
20 - interrupts: Must contain the xHCI host interrupt and the mailbox interrupt.
43 configure the USB pads used by the XHCI controller
66 used by the xHCI controller. This list must comprise of a specifier for the
H A Dmediatek,mtu3.txt67 The xhci should be added as subnode to mtu3 as shown in the following example
68 if host mode is enabled. The DT binding details of xhci can be found in:
69 Documentation/devicetree/bindings/usb/mediatek,mtk-xhci.txt
98 usb_host: xhci@11270000 {
99 compatible = "mediatek,mt8173-xhci";
/freebsd-src/sys/contrib/device-tree/Bindings/phy/
H A Drealtek,usb2phy.yaml15 The USB 2.0 PHY driver is designed to support the XHCI controller. The SoCs
16 support multiple XHCI controllers. One PHY device node maps to one XHCI
20 The USB architecture includes three XHCI controllers.
21 Each XHCI maps to one USB 2.0 PHY and map one USB 3.0 PHY on some
23 XHCI controller#0 -- usb2phy -- phy#0
25 XHCI controller#1 -- usb2phy -- phy#0
26 XHCI controller#2 -- usb2phy -- phy#0
30 The USB architecture includes two XHCI controllers.
33 XHCI controller#0 -- usb2phy -- phy#0
34 XHCI controller#1 -- usb2phy -- phy#0
[all …]
H A Drealtek,usb3phy.yaml15 The USB 3.0 PHY driver is designed to support the XHCI controller. The SoCs
16 support multiple XHCI controllers. One PHY device node maps to one XHCI
20 The USB architecture includes three XHCI controllers.
21 Each XHCI maps to one USB 2.0 PHY and map one USB 3.0 PHY on some
23 XHCI controller#0 -- usb2phy -- phy#0
25 XHCI controller#1 -- usb2phy -- phy#0
26 XHCI controller#2 -- usb2phy -- phy#0
30 The USB architecture includes three XHCI controllers.
31 Each XHCI maps to one USB 2.0 PHY and map one USB 3.0 PHY on controllers#2.
32 XHCI controller#0 -- usb2phy -- phy#0
[all …]
H A Dbrcm,brcmstb-usb-phy.yaml9 description: Broadcom's PHY that handles EHCI/OHCI and/or XHCI
27 - description: XHCI EC register
28 - description: XHCI GBL register
87 brcm,has-xhci:
88 description: Indicates the PHY has an XHCI PHY.
108 - brcm,has-xhci
166 brcm,has-xhci;
192 brcm,has-xhci;
H A Dbrcm,brcmstb-usb-phy.txt44 - brcm,has-xhci: Boolean indicating the phy has an XHCI phy.
58 brcm,has-xhci;
82 brcm,has-xhci;
/freebsd-src/share/man/man4/
H A Dxhci.429 .Nm xhci
33 .Cd "device xhci"
47 .Tn XHCI
56 .Tn XHCI
58 subclass 3 (USB) and programming interface 48 (XHCI).
66 .It Va hw.usb.xhci.debug
70 .It Va hw.usb.xhci.dcepquirk
73 .It Va hw.usb.xhci.ctlquirk
78 .It Va hw.usb.xhci.streams
81 .It Va hw.usb.xhci.route
[all …]
/freebsd-src/sys/dev/usb/controller/
H A Dxhcireg.h32 /* XHCI PCI config registers */
43 /* XHCI capability registers */
47 #define XHCI_HCIVERSION_0_9 0x0090 /* xHCI version 0.9 */
48 #define XHCI_HCIVERSION_1_0 0x0100 /* xHCI version 1.0 */
75 /* XHCI operational registers. Offset given by XHCI_CAPLENGTH register */
76 #define XHCI_USBCMD 0x00 /* XHCI command */
86 #define XHCI_USBSTS 0x04 /* XHCI status */
96 #define XHCI_PAGESIZE 0x08 /* XHCI page size mask */
102 #define XHCI_DNCTRL 0x14 /* XHCI device notification control */
104 #define XHCI_CRCR_LO 0x18 /* XHCI command ring control */
[all …]
H A Dgeneric_xhci_fdt.c49 #include <dev/usb/controller/xhci.h>
63 {"marvell,armada-380-xhci", XHCI_FDT_MATCH},
64 {"marvell,armada3700-xhci", XHCI_FDT_MATCH},
65 {"marvell,armada-8k-xhci", XHCI_FDT_MATCH},
66 {"generic-xhci", XHCI_FDT_MATCH},
132 DEFINE_CLASS_1(xhci, xhci_fdt_driver, xhci_fdt_methods,
135 DRIVER_MODULE(xhci, simplebus, xhci_fdt_driver, 0, 0);
136 MODULE_DEPEND(xhci, usb, 1, 1, 1);
H A Dxhci_pci.c59 #include <dev/usb/controller/xhci.h>
85 DEFINE_CLASS_0(xhci, xhci_pci_driver, xhci_device_methods,
88 DRIVER_MODULE(xhci, pci, xhci_pci_driver, NULL, NULL);
89 MODULE_DEPEND(xhci, usb, 1, 1, 1);
228 return ("XHCI (generic) USB 3.0 controller"); in xhci_pci_match()
247 TUNABLE_INT("hw.usb.xhci.msi", &xhci_use_msi);
249 TUNABLE_INT("hw.usb.xhci.msix", &xhci_use_msix);
306 case 0x10091b73: /* Fresco Logic FL1009 USB3.0 xHCI Controller */ in xhci_pci_attach()
307 case 0x8241104c: /* TUSB73x0 USB3.0 xHCI Controller */ in xhci_pci_attach()
326 * On Intel chipsets, reroute ports from EHCI to XHCI in xhci_pci_attach()
[all...]
H A Dgeneric_xhci_acpi.c47 #include <dev/usb/controller/xhci.h>
78 DEFINE_CLASS_1(xhci, xhci_acpi_driver, xhci_acpi_methods,
81 DRIVER_MODULE(xhci, acpi, xhci_acpi_driver, 0, 0);
82 MODULE_DEPEND(xhci, usb, 1, 1, 1);
/freebsd-src/sys/arm/broadcom/bcm2835/
H A Dbcm2838_xhci.c23 * The VL805 is a generic xhci controller. However, in the newer hardware
27 * handing control to the xhci generic driver.
61 #include <dev/usb/controller/xhci.h>
123 device_printf(dev, "warning: xhci firmware not found.\n"); in bcm_xhci_check_firmware()
125 device_printf(dev, "note: xhci firmware not found.\n"); in bcm_xhci_check_firmware()
128 "note: xhci firmware detected; firmware is revision %x.\n", in bcm_xhci_check_firmware()
147 * possible to reload already-installed xhci firmware. in bcm_xhci_install_xhci_firmware()
153 * Notify the VideoCore gpu processor that it needs to reload the xhci in bcm_xhci_install_xhci_firmware()
154 * firmware into the xhci controller. This needs to happen after the pci in bcm_xhci_install_xhci_firmware()
158 device_printf(dev, "note: installing xhci firmware.\n"); in bcm_xhci_install_xhci_firmware()
[all …]

1234567