| /freebsd/sys/contrib/device-tree/Bindings/usb/ |
| H A 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
11 particular mode. Valid arguments are "host",
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
[all …]
|
| H A 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 …]
|
| H A D | dwc3.txt | 3 DWC3- USB3 CONTROLLER. Complies to the generic USB binding properties
4 as described in 'usb/generic.txt'
7 - compatible: must be "snps,dwc3"
8 - reg : Address and length of the register set for the device
9 - interrupts: Interrupts used by the dwc3 controller.
10 - clock-names: list of clock names. Ideally should be "ref",
12 - clocks: list of phandle and clock specifier pairs corresponding to
13 entries in the clock-names property.
16 clocks are optional if the parent node (i.e. glue-layer) is compatible to
18 "cavium,octeon-7130-usb-uctl"
[all …]
|
| H A D | snps,dwc3.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/usb/snps,dwc3.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Felipe Balbi <balbi@kernel.org>
14 be presented as a standalone DT node with an optional vendor-specifi
[all...] |
| H A D | dwc3-st.txt | 3 This file documents the parameters for the dwc3-st driver.
8 - compatible : must be "st,stih407-dwc3"
9 - reg : glue logic base address and USB syscfg ctrl register offset
10 - reg-names : should be "reg-glue" and "syscfg-reg"
11 - st,syscon : should be phandle to system configuration node which
13 - resets : list of phandle and reset specifier pairs. There should be two entries, one
15 - reset-names : list of reset signal names. Names should be "powerdown" and "softreset"
16 See: Documentation/devicetree/bindings/reset/st,stih407-powerdown.yaml
19 - #address-cells, #size-cells : should be '1' if the device has sub-nodes
22 - pinctl-names : A pinctrl state named "default" must be defined
[all …]
|
| H A D | mediatek,mtu3.yaml | 1 # 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
23 - enum:
24 - mediatek,mt2712-mtu3
25 - mediatek,mt8173-mtu3
26 - mediatek,mt8183-mtu3
[all …]
|
| H A D | exynos-usb.txt | 1 Samsung Exynos SoC USB controller
3 The USB devices interface with USB controllers on Exynos SOCs.
8 - compatible: should be "samsung,exynos4210-ehci" for USB 2.0
10 - reg: physical base address of the controller and length of memory mapped
12 - interrupts: interrupt number to the cpu.
13 - clocks: from common clock binding: handle to usb clock.
14 - clock-names: from common clock binding: Shall be "usbhost".
15 - phys: from the *Generic PHY* bindings; array specifying phy(s) used
17 - phy-names: from the *Generic PHY* bindings; array of the names for
22 - samsung,vbus-gpio: if present, specifies the GPIO that
[all …]
|
| /freebsd/lib/libusb/ |
| H A D | libusb20.3 | 2 .\" Copyright (c) 2008-2019 Hans Petter Selasky
33 .Nd "USB access library"
39 USB access library (libusb -lusb)
231 USB through the USB file system interface.
241 .Sh USB TRANSFER OPERATIONS
245 will release all kernel resources associated with an USB
250 Non-zero return values indicate a LIBUSB20_ERROR value.
259 associated with an USB
281 This flag is only valid for ISOCHRONOUS transfers and has no effect
288 Non-zero return values indicate a LIBUSB20_ERROR value.
[all …]
|
| H A D | libusb.3 | 30 .Nd "USB access library"
32 USB access library
33 .Pq libusb, -lusb
39 library contains interfaces for directly managing a usb device.
49 initialise a valid libusb v1.0 context.
52 argument is non-NULL, a pointer to the libusb context is stored at
59 initialise a valid libusb v1.0 context.
62 argument is non-NULL, a pointer to the libusb context is stored at
64 Additional options, like the USB debug level, may be given using the
79 This function will return non-zer
[all...] |
| /freebsd/sys/contrib/device-tree/Bindings/phy/ |
| H A D | nvidia,tegra124-xusb-padctl.txt | 11 Some of the lanes are high-speed lanes, which can be used for PCIe, SATA or
12 super-speed USB. Other lanes are for various types of low-speed, full-speed
13 or high-speed USB (such as UTMI, ULPI and HSIC). The XUSB pad controller
14 contains a software-configurable mux that sits between the I/O controller
17 In addition to per-lane configuration, USB 3.0 ports may require additional
18 settings on a per-board basis.
20 Pads will be represented as children of the top-level XUSB pad controller
23 PHY bindings, as described by the phy-bindings.txt file in this directory.
27 "port" is typically used to denote the physical USB receptacle. The device
29 abstraction of the signals that are routed to a USB receptacle (i.e. a PHY
[all …]
|
| H A D | nvidia,tegra194-xusb-padctl.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/phy/nvidia,tegra194-xusb-padctl.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Thierry Reding <thierry.reding@gmail.com>
11 - Jon Hunter <jonathanh@nvidia.com>
21 Some of the lanes are high-speed lanes, which can be used for PCIe, SATA or
22 super-speed USB. Other lanes are for various types of low-speed, full-speed
23 or high-speed USB (such as UTMI, ULPI and HSIC). The XUSB pad controller
24 contains a software-configurable mux that sits between the I/O controller
[all …]
|
| H A D | nvidia,tegra186-xusb-padctl.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/phy/nvidia,tegra186-xusb-padctl.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Thierry Reding <thierry.reding@gmail.com>
11 - Jon Hunter <jonathanh@nvidia.com>
21 Some of the lanes are high-speed lanes, which can be used for PCIe, SATA or
22 super-speed USB. Other lanes are for various types of low-speed, full-speed
23 or high-speed USB (such as UTMI, ULPI and HSIC). The XUSB pad controller
24 contains a software-configurable mux that sits between the I/O controller
[all …]
|
| H A D | nvidia,tegra210-xusb-padctl.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/phy/nvidia,tegra210-xus
[all...] |
| H A D | pistachio-usb-phy.txt | 1 IMG Pistachio USB PHY
5 ---------
[all...] |
| /freebsd/sys/contrib/device-tree/Bindings/power/supply/ |
| H A D | qcom,pm8941-charger.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/power/supply/qcom,pm8941-charger.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Qualcomm Switch-Mode Battery Charger and Boost
10 - Sebastian Reichel <sre@kernel.org>
15 - qcom,pm8226-charger
16 - qcom,pm8941-charger
23 - description: charge done
24 - description: charge fast mode
[all …]
|
| H A D | max8903-charger.txt | 4 - compatible: "maxim,max8903" for MAX8903 Battery Charger
5 - dok-gpios: Valid DC power has been detected (active low, input), optional if uok-gpios is provided
6 - uok-gpios: Valid USB power has been detected (active low, input), optional if dok-gpios is provid…
9 - cen-gpios: Charge enable pin (active low, output)
10 - chg-gpios: Charger status pin (active low, input)
11 - flt-gpios: Fault pin (active low, output)
12 - dcm-gpios: Current limit mode setting (DC=1 or USB=0, output)
13 - usus-gpios: USB suspend pin (active high, output)
18 max8903-charger {
20 dok-gpios = <&gpio2 3 GPIO_ACTIVE_LOW>;
[all …]
|
| H A D | maxim,max8903.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Sebastian Reichel <sre@kernel.org>
13 - $ref: power-supply.yaml#
19 dok-gpios:
21 description: Valid DC power has been detected (active low, input)
23 uok-gpios:
25 description: Valid USB power has been detected (active low, input)
27 cen-gpios:
[all …]
|
| H A D | qcom_smbb.txt | 1 Qualcomm Switch-Mode Battery Charger and Boost
4 - compatible:
8 - "qcom,pm8941-charger"
10 - reg:
12 Value type: <prop-encoded-array>
15 - interrupts:
17 Value type: <prop-encoded-array>
21 - charge done
22 - charge fast mode
23 - charge trickle mode
[all …]
|
| /freebsd/tools/tools/usbtest/ |
| H A D | usb_control_ep_test.c | 1 /*-
2 * Copyright (c) 2007-2022 Hans Petter Selasky
40 #include <dev/usb/usb_endian.h>
41 #include <dev/usb/usb.h>
42 #include <dev/usb/usb_cdc.h>
51 error = sysctlbyname("hw.usb.ctrl_bus_fail", NULL, NULL, in set_ctrl_ep_fail()
56 error = sysctlbyname("hw.usb.ctrl_dev_fail", NULL, NULL, in set_ctrl_ep_fail()
61 error = sysctlbyname("hw.usb.ctrl_ds_fail", NULL, NULL, in set_ctrl_ep_fail()
66 error = sysctlbyname("hw.usb.ctrl_ss_fail", NULL, NULL, in set_ctrl_ep_fail()
73 printf("Cannot set USB sysctl, missing USB_REQ_DEBUG option?\n"); in set_ctrl_ep_fail()
[all …]
|
| /freebsd/share/man/man9/ |
| H A D | usbdi.9 | 113 The Universal Serial Bus (USB) driver programming interface provides
115 controlling and communicating with USB peripherals.
117 .Nm usb
118 module supports both USB Host and USB Device side mode.
119 .Sh USB TRANSFER MANAGEMENT FUNCTIONS
120 The USB standard defines four types of USB transfers.
130 This function will allocate memory for and initialise an array of USB
141 is a pointer to an array of USB transfer pointers that are initialized
142 to NULL, and then pointed to allocated USB transfers.
144 is a pointer to an array of USB config structures.
[all …]
|
| /freebsd/sys/dev/usb/ |
| H A D | usb_parse.c | 1 /*-
2 * SPDX-License-Identifier: BSD-2-Clause
4 * Copyright (c) 2008-2020 Hans Petter Selasky. All rights reserved.
50 #include <dev/usb/usb.h>
51 #include <dev/usb/usbdi.h>
52 #include <dev/usb/usbdi_util.h>
56 #include <dev/usb/usb_core.h>
57 #include <dev/usb/usb_debug.h>
60 /*------------------------------------------------------------------------*
63 * This function is the safe way to iterate across the USB config
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/leds/ |
| H A D | leds-bcm6328.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/leds/leds-bcm6328.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Álvaro Fernández Rojas <noltari@gmail.com>
17 as spi-gpio. See
21 exporting the 74x164 as spi-gpio prevents those LEDs to be hardware
29 explained later in brcm,link-signal-sources). Even if a LED is hardware
34 Each LED is represented as a sub-node of the brcm,bcm6328-leds device.
38 const: brcm,bcm6328-leds
[all …]
|
| H A D | leds-bcm6328.txt | 7 as spi-gpio. See Documentation/devicetree/bindings/gpio/fairchild,74hc595.yaml),
10 exporting the 74x164 as spi-gpio prevents those LEDs to be hardware
18 explained later in brcm,link-signal-sources). Even if a LED is hardware
24 - compatible : should be "brcm,bcm6328-leds".
25 - #address-cells : must be 1.
26 - #size-cells : must be 0.
27 - reg : BCM6328 LED controller address and size.
30 - brcm,serial-leds : Boolean, enables Serial LEDs.
32 - brcm,serial-mux : Boolean, enables Serial LEDs multiplexing.
34 - brcm,serial-clk-low : Boolean, makes clock signal active low.
[all …]
|
| /freebsd/sys/cam/ |
| H A D | README.quirks | 4 Nate Lawson - njl at freebsd org
19 CAM provides a generic transport for SCSI-like devices. Many different
21 (1394), USB UMASS, fibre channel, and ATAPI. For block devices (i.e.
23 and RBC. SCSI hard drives are usually SBC-compliant and smaller
24 devices like flash drives are usually RBC-compliant. Multimedia
25 devices including CDROMs and DVD-RW are usually MMC-compliant.
39 o CAM_QUIRK_NOLUNS - do not probe luns other than 0 since device
42 o CAM_QUIRK_NOSERIAL - do not send an inquiry for serial number.
44 o CAM_QUIRK_HILUNS - probe all luns even if some respond "not present"
49 o DA_Q_NO_SYNC_CACHE - The sync cache command is used to force a
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/mfd/ |
| H A D | max14577.txt | 1 Maxim MAX14577/77836 Multi-Function Device
3 MAX14577 is a Multi-Function Device with Micro-USB Interface Circuit, Li+
4 Battery Charger and SFOUT LDO output for powering USB devices. It is
13 - compatible : Must be "maxim,max14577" or "maxim,max77836".
14 - reg : I2C slave address for the max14577 chip (0x25 for max14577/max77836)
15 - interrupts : IRQ line for the chip.
19 - charger :
22 - compatible : "maxim,max14577-charger"
23 or "maxim,max77836-charger"
24 - maxim,fast-charge-uamp : Current in uA for Fast Charge;
[all …]
|