Home
last modified time | relevance | path

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

12345678910>>...40

/kernel/linux/linux-6.6/Documentation/ABI/testing/
Dsysfs-class-typec1 USB Type-C port devices (eg. /sys/class/typec/port0/)
7 The supported USB data roles. This attribute can be used for
16 Valid values: host, device
31 Valid values: source, sink
42 Valid values:
47 dual (The port will behave as dual-role-data and
48 dual-role-power port)
57 when both the port and the partner support USB Power Delivery.
64 Valid values:
66 - "no" when the port is not the VCONN Source
[all …]
Dsysfs-class-power5 Contact: linux-pm@vger.kernel.org
10 Valid values: Represented as string
14 Contact: linux-pm@vger.kernel.org
19 Valid values: Represented as string
23 Contact: linux-pm@vger.kernel.org
28 Valid values: Represented as string
32 Contact: linux-pm@vger.kernel.org
37 Valid values: "Battery", "UPS", "Mains", "USB", "Wireless"
39 **Battery and USB properties**
43 Contact: linux-pm@vger.kernel.org
[all …]
Dsysfs-driver-typec-displayport6 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
44 Note. As of VESA DisplayPort Alt Mode on USB Type-C Standard
47 USB SuperSpeed protocol. From user perspective pin assignments C
55 VESA DisplayPort Alt Mode on USB Type-C Standard defines how
[all …]
Dsysfs-driver-toshiba_acpi5 Description: This file controls the keyboard backlight operation mode, valid
8 * 0x1 -> FN-Z
9 * 0x2 -> AUTO (also called TIMER)
10 * 0x8 -> ON
11 * 0x10 -> OFF
14 parameters, kernel 3.15 only accepts the first two (FN-Z and
26 valid values range from 0-60.
29 type and the range accepted for type 2 is 1-60.
37 Description: This file shows the absolute position of the built-in
45 stick (if available), valid values are:
[all …]
/kernel/linux/linux-5.10/Documentation/ABI/testing/
Dsysfs-class-power5 Contact: linux-pm@vger.kernel.org
10 Valid values: Represented as string
14 Contact: linux-pm@vger.kernel.org
19 Valid values: Represented as string
23 Contact: linux-pm@vger.kernel.org
28 Valid values: Represented as string
32 Contact: linux-pm@vger.kernel.org
37 Valid values: "Battery", "UPS", "Mains", "USB", "Wireless"
39 **Battery and USB properties**
43 Contact: linux-pm@vger.kernel.org
[all …]
Dsysfs-class-typec1 USB Type-C port devices (eg. /sys/class/typec/port0/)
7 The supported USB data roles. This attribute can be used for
16 Valid values: host, device
31 Valid values: source, sink
42 Valid values:
47 dual (The port will behave as dual-role-data and
48 dual-role-power port)
57 when both the port and the partner support USB Power Delivery.
64 Valid values:
66 - "no" when the port is not the VCONN Source
[all …]
Dsysfs-driver-toshiba_acpi5 Description: This file controls the keyboard backlight operation mode, valid
8 * 0x1 -> FN-Z
9 * 0x2 -> AUTO (also called TIMER)
10 * 0x8 -> ON
11 * 0x10 -> OFF
14 parameters, kernel 3.15 only accepts the first two (FN-Z and
26 valid values range from 0-60.
29 type and the range accepted for type 2 is 1-60.
37 Description: This file shows the absolute position of the built-in
45 stick (if available), valid values are:
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/usb/
Dgeneric.txt1 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 …]
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 …]
Ddwc3.txt3 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 …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/phy/
Dnvidia,tegra124-xusb-padctl.txt11 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 …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/power/supply/
Dqcom,pm8941-charger.yaml1 # 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 …]
Dmaxim,max8903.yaml1 # 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 …]
/kernel/linux/linux-6.6/sound/usb/
Dvalidate.c1 // SPDX-License-Identifier: GPL-2.0-or-later
3 // Validation of USB-audio class descriptors
7 #include <linux/usb.h>
8 #include <linux/usb/audio.h>
9 #include <linux/usb/audio-v2.h>
10 #include <linux/usb/audio-v3.h>
11 #include <linux/usb/midi.h>
22 #define UAC_VERSION_ALL (unsigned char)(-1)
30 return d->bLength >= sizeof(*d) && in validate_uac1_header()
31 d->bLength >= sizeof(*d) + d->bInCollection; in validate_uac1_header()
[all …]
/kernel/linux/linux-5.10/sound/usb/
Dvalidate.c1 // SPDX-License-Identifier: GPL-2.0-or-later
3 // Validation of USB-audio class descriptors
7 #include <linux/usb.h>
8 #include <linux/usb/audio.h>
9 #include <linux/usb/audio-v2.h>
10 #include <linux/usb/audio-v3.h>
11 #include <linux/usb/midi.h>
22 #define UAC_VERSION_ALL (unsigned char)(-1)
30 return d->bLength >= sizeof(*d) && in validate_uac1_header()
31 d->bLength >= sizeof(*d) + d->bInCollection; in validate_uac1_header()
[all …]
/kernel/linux/linux-6.6/Documentation/ABI/obsolete/
Dsysfs-driver-hid-roccat-ryos1 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
9 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
21 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
31 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
41 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
51 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
61 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
71 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
81 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
92 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
[all …]
/kernel/linux/linux-5.10/Documentation/ABI/obsolete/
Dsysfs-driver-hid-roccat-ryos1 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
9 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
21 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
31 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
41 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
51 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
61 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
71 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
81 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
92 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
[all …]
/kernel/linux/linux-5.10/include/linux/power/
Dmax8903_charger.h1 /* SPDX-License-Identifier: GPL-2.0-or-later */
3 * max8903_charger.h - Maxim 8903 USB/Adapter Charger Driver
21 int uok; /* USB Power OK output */
24 int dcm; /* Current-Limit Mode input (1: DC, 2: USB) */
25 int usus; /* USB Suspend Input (1: suspended) */
30 * dok should be valid.
36 * USB is wired
38 * uok should be valid.
/kernel/linux/linux-5.10/Documentation/driver-api/usb/
Ddma.rst1 USB DMA
4 In Linux 2.5 kernels (and later), USB device drivers have additional control
6 in the kernel usb programming guide (kerneldoc, from the source code).
11 The big picture is that USB drivers can continue to ignore most DMA issues,
12 though they still must provide DMA-ready buffers (see
13 :doc:`/core-api/dma-api-howto`). That's how they've worked through
14 the 2.4 (and earlier) kernels, or they can now be DMA-aware.
16 DMA-aware usb drivers:
18 - New calls enable DMA-aware drivers, letting them allocate dma buffers and
19 manage dma mappings for existing dma-ready buffers (see below).
[all …]
/kernel/linux/linux-6.6/Documentation/driver-api/usb/
Ddma.rst1 USB DMA
4 In Linux 2.5 kernels (and later), USB device drivers have additional control
6 in the kernel usb programming guide (kerneldoc, from the source code).
11 The big picture is that USB drivers can continue to ignore most DMA issues,
12 though they still must provide DMA-ready buffers (see
13 Documentation/core-api/dma-api-howto.rst). That's how they've worked through
14 the 2.4 (and earlier) kernels, or they can now be DMA-aware.
16 DMA-aware usb drivers:
18 - New calls enable DMA-aware drivers, letting them allocate dma buffers and
19 manage dma mappings for existing dma-ready buffers (see below).
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/power/supply/
Dmax8903-charger.txt4 - 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 …]
/kernel/linux/linux-6.6/drivers/usb/dwc2/
Dparams.c1 // SPDX-License-Identifier: (GPL-2.0+ OR BSD-3-Clause)
3 * Copyright (C) 2004-2016 Synopsys, Inc.
9 #include <linux/usb/of.h>
20 struct dwc2_core_params *p = &hsotg->params; in dwc2_set_bcm_params()
22 p->host_rx_fifo_size = 774; in dwc2_set_bcm_params()
23 p->max_transfer_size = 65535; in dwc2_set_bcm_params()
24 p->max_packet_count = 511; in dwc2_set_bcm_params()
25 p->ahbcfg = 0x10; in dwc2_set_bcm_params()
30 struct dwc2_core_params *p = &hsotg->params; in dwc2_set_his_params()
32 p->otg_caps.hnp_support = false; in dwc2_set_his_params()
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/phy/
Dnvidia,tegra194-xusb-padctl.yaml1 # 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 …]
/kernel/linux/linux-5.10/drivers/usb/dwc2/
Dparams.c1 // SPDX-License-Identifier: (GPL-2.0+ OR BSD-3-Clause)
3 * Copyright (C) 2004-2016 Synopsys, Inc.
14 * 3. The names of the above-listed copyright holders may not be used
44 struct dwc2_core_params *p = &hsotg->params; in dwc2_set_bcm_params()
46 p->host_rx_fifo_size = 774; in dwc2_set_bcm_params()
47 p->max_transfer_size = 65535; in dwc2_set_bcm_params()
48 p->max_packet_count = 511; in dwc2_set_bcm_params()
49 p->ahbcfg = 0x10; in dwc2_set_bcm_params()
54 struct dwc2_core_params *p = &hsotg->params; in dwc2_set_his_params()
56 p->otg_cap = DWC2_CAP_PARAM_NO_HNP_SRP_CAPABLE; in dwc2_set_his_params()
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/usb/
Dsnps,dwc3.yaml1 # 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-specific
18 - $ref: usb-drd.yaml#
19 - if:
25 - dr_mode
27 $ref: usb.yaml#
[all …]

12345678910>>...40