Searched +full:en +full:- +full:usb (Results 1 – 25 of 28) sorted by relevance
12
| /Documentation/devicetree/bindings/usb/ |
| D | maxim,max3421.txt | 1 Maxim Integrated SPI-based USB 2.0 host controller MAX3421E
4 - compatible: Should be "maxim,max3421"
5 - spi-max-frequency: maximum frequency for this device must not exceed 26 MHz.
6 - reg: chip select number to which this device is connected.
7 - maxim,vbus-en-pin: <GPOUTx ACTIVE_LEVEL>
8 GPOUTx is the number (1-8) of the GPOUT pin of MAX3421E to drive Vbus.
10 - interrupts: the interrupt line description for the interrupt controller.
16 usb@0 {
19 maxim,vbus-en-pin = <3 1>;
20 spi-max-frequency = <26000000>;
[all …]
|
| D | maxim,max3420-udc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/usb/maxim,max3420-udc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: MAXIM MAX3420/1 USB Peripheral Controller
10 - Jassi Brar <jaswinder.singh@linaro.org>
17 http://datasheets.maximintegrated.com/en/ds/MAX3420E.pdf
22 - maxim,max3420-udc
23 - maxim,max3421-udc
30 - description: usb irq from max3420
[all …]
|
| /Documentation/usb/ |
| D | linux.inf | 2 ; <https://msdn.microsoft.com/en-us/library/ff570620.aspx>
6 ; <http://msdn.microsoft.com/en-us/cc300389.aspx#MLPL>.
12 ClassGUID = {4d36e972-e325-11ce-bfc1-08002be10318}
21 %LinuxDevice% = RNDIS.NT.5.1, USB\VID_0525&PID_a4a2, USB\VID_1d6b&PID_0104&MI_00
25 %LinuxDevice% = RNDIS.NT.5.1, USB\VID_0525&PID_a4a2, USB\VID_1d6b&PID_0104&MI_00
29 %LinuxDevice% = RNDIS.NT.5.1, USB\VID_0525&PID_a4a2, USB\VID_1d6b&PID_0104&MI_00
36 ; References the in-build Netrndis.inf
59 ; No sys copyfiles - the sys files are already in-build
61 ; We do not support XP SP1-, 2003 SP1-, ME, 9x.
65 LinuxDevice = "Linux USB Ethernet/RNDIS Gadget"
|
| D | gadget_multi.rst | 12 In its standard configuration it provides a single USB configuration
13 with RNDIS[1] (that is Ethernet), USB CDC[2] ACM (that is serial) and
14 USB Mass Storage functions.
18 have two configurations -- one with RNDIS and another with CDC ECM[3].
20 Please note that if you use non-standard configuration (that is enable
26 To make use of the gadget one needs to make it work on host side --
31 ------------------
38 This is also true for two configuration set-up with RNDIS
43 --------------------
50 First of all, Windows need to detect the gadget as an USB composite
[all …]
|
| D | linux-cdc-acm.inf | 1 ; Windows USB CDC ACM Setup File
7 ; <http://msdn.microsoft.com/en-us/cc300389.aspx#MLPL>.
13 ClassGuid={4D36E978-E325-11CE-BFC1-08002BE10318}
24 ;------------------------------------------------------------------------------
25 ; Windows 2000/XP/Vista-32bit Sections
26 ;------------------------------------------------------------------------------
51 ;------------------------------------------------------------------------------
52 ; Vista-64bit Sections
53 ;------------------------------------------------------------------------------
79 ;------------------------------------------------------------------------------
[all …]
|
| D | gadget_uvc.rst | 6 --------
7 The UVC Gadget driver is a driver for hardware on the *device* side of a USB
8 connection. It is intended to run on a Linux system that has USB device-side
14 On the host side (once connected via USB cable), a device running the UVC Gadget
18 queue image buffers from a variety of sources to be transmitted via the USB
24 -----------------------------
29 ---------------------------------------
35 see Documentation/ABI/testing/configfs-usb-gadget-uvc
47 .. code-block:: bash
54 mkdir -p $FUNCTION
[all …]
|
| /Documentation/arch/arm/stm32/ |
| D | stm32f429-overview.rst | 6 ------------
8 The STM32F429 is a Cortex-M4 MCU aimed at various applications.
11 - ARM Cortex-M4 up to 180MHz with FPU
12 - 2MB internal Flash Memory
13 - External memory support through FMC controller (PSRAM, SDRAM, NOR, NAND)
14 - I2C, SPI, SAI, CAN, USB OTG, Ethernet controllers
15 - LCD controller & Camera interface
16 - Cryptographic processor
19 ---------
23 .. _STM32F429: http://www.st.com/web/en/catalog/mmc/FM141/SC1169/SS1577/LN1806?ecmp=stm32f429-439_p…
|
| D | stm32h750-overview.rst | 6 ------------
8 The STM32H750 is a Cortex-M7 MCU aimed at various applications.
11 - Cortex-M7 core running up to @480MHz
12 - 128K internal flash, 1MBytes internal RAM
13 - FMC controller to connect SDRAM, NOR and NAND memories
14 - Dual mode QSPI
15 - SD/MMC/SDIO support
16 - Ethernet controller
17 - USB OTFG FS & HS controllers
18 - I2C, SPI, CAN busses support
[all …]
|
| D | stm32h743-overview.rst | 6 ------------
8 The STM32H743 is a Cortex-M7 MCU aimed at various applications.
11 - Cortex-M7 core running up to @400MHz
12 - 2MB internal flash, 1MBytes internal RAM
13 - FMC controller to connect SDRAM, NOR and NAND memories
14 - Dual mode QSPI
15 - SD/MMC/SDIO support
16 - Ethernet controller
17 - USB OTFG FS & HS controllers
18 - I2C, SPI, CAN busses support
[all …]
|
| D | stm32f746-overview.rst | 6 ------------
8 The STM32F746 is a Cortex-M7 MCU aimed at various applications.
11 - Cortex-M7 core running up to @216MHz
12 - 1MB internal flash, 320KBytes internal RAM (+4KB of backup SRAM)
13 - FMC controller to connect SDRAM, NOR and NAND memories
14 - Dual mode QSPI
15 - SD/MMC/SDIO support
16 - Ethernet controller
17 - USB OTFG FS & HS controllers
18 - I2C, SPI, CAN busses support
[all …]
|
| D | stm32f769-overview.rst | 6 ------------
8 The STM32F769 is a Cortex-M7 MCU aimed at various applications.
11 - Cortex-M7 core running up to @216MHz
12 - 2MB internal flash, 512KBytes internal RAM (+4KB of backup SRAM)
13 - FMC controller to connect SDRAM, NOR and NAND memories
14 - Dual mode QSPI
15 - SD/MMC/SDIO support*2
16 - Ethernet controller
17 - USB OTFG FS & HS controllers
18 - I2C*4, SPI*6, CAN*3 busses support
[all …]
|
| /Documentation/devicetree/bindings/gpio/ |
| D | gpio-pca95xx.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/gpio/gpio-pca95xx.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Krzysztof Kozlowski <krzk@kernel.org>
19 - items:
20 - const: diodes,pi4ioe5v6534q
21 - const: nxp,pcal6534
22 - items:
23 - enum:
[all …]
|
| /Documentation/admin-guide/media/ |
| D | cec.rst | 1 .. SPDX-License-Identifier: GPL-2.0
12 - Exynos4
13 - Exynos5
14 - STIH4xx HDMI CEC
15 - V4L2 adv7511 (same HW, but a different driver from the drm adv7511)
16 - stm32
17 - Allwinner A10 (sun4i)
18 - Raspberry Pi
19 - dw-hdmi (Synopsis IP)
20 - amlogic (meson ao-cec and ao-cec-g12a)
[all …]
|
| D | bttv.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 ----------------------
12 ./scripts/config -e PCI
13 ./scripts/config -m I2C
14 ./scripts/config -m INPUT
15 ./scripts/config -m MEDIA_SUPPORT
16 ./scripts/config -e MEDIA_PCI_SUPPORT
17 ./scripts/config -e MEDIA_ANALOG_TV_SUPPORT
18 ./scripts/config -e MEDIA_DIGITAL_TV_SUPPORT
19 ./scripts/config -e MEDIA_RADIO_SUPPORT
[all …]
|
| /Documentation/driver-api/usb/ |
| D | anchors.rst | 1 USB Anchors
7 A USB driver needs to support some callbacks requiring
42 --------------------------------
49 ----------------------------------
60 -----------------------------------
62 All URBs of an anchor are unanchored en masse.
65 ---------------------------------------
72 --------------------------
78 -----------------------------
|
| /Documentation/devicetree/bindings/mfd/ |
| D | x-powers,axp152.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/mfd/x-powers,axp152.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: X-Powers AXP PMIC
10 - Chen-Yu Tsai <wens@csie.org>
13 - if:
18 - x-powers,axp152
19 - x-powers,axp202
20 - x-powers,axp209
[all …]
|
| /Documentation/devicetree/bindings/phy/ |
| D | phy-rockchip-typec.txt | 1 * ROCKCHIP type-c PHY
2 ---------------------
5 - compatible : must be "rockchip,rk3399-typec-phy"
6 - reg: Address and length of the usb phy control register set
7 - rockchip,grf : phandle to the syscon managing the "general
9 - clocks : phandle + clock specifier for the phy clocks
10 - clock-names : string, clock name, must be "tcpdcore", "tcpdphy-ref";
11 - assigned-clocks: main clock, should be <&cru SCLK_UPHY0_TCPDCORE> or
13 - assigned-clock-rates : the phy core clk frequency, shall be: 50000000
14 - resets : a list of phandle + reset specifier pairs
[all …]
|
| /Documentation/arch/x86/ |
| D | iommu.rst | 7 - Intel: http://www.intel.com/content/dam/www/public/us/en/documents/product-specifications/vt-dire…
8 - AMD: https://www.amd.com/content/dam/amd/en/documents/processor-tech-docs/specifications/48882_3_…
13 -----------
21 - DMAR - Intel DMA Remapping table
22 - DRHD - Intel DMA Remapping Hardware Unit Definition
23 - RMRR - Intel Reserved Memory Region Reporting Structure
24 - IVRS - AMD I/O Virtualization Reporting Structure
25 - IVDB - AMD I/O Virtualization Definition Block
26 - IVHD - AMD I/O Virtualization Hardware Definition
31 There are some devices the BIOS controls, for e.g USB devices to perform
[all …]
|
| /Documentation/devicetree/bindings/soc/tegra/ |
| D | nvidia,tegra20-pmc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/soc/tegra/nvidia,tegra20-pmc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Thierry Reding <thierry.reding@gmail.com>
11 - Jonathan Hunter <jonathanh@nvidia.com>
16 - nvidia,tegra20-pmc
17 - nvidia,tegra30-pmc
18 - nvidia,tegra114-pmc
19 - nvidia,tegra124-pmc
[all …]
|
| /Documentation/networking/device_drivers/can/ctu/ |
| D | ctucanfd-driver.rst | 1 .. SPDX-License-Identifier: GPL-2.0-or-later
10 ------------------------
16 of `FEE <http://www.fel.cvut.cz/en/>`_ at `CTU <https://www.cvut.cz/en>`_.
19 `Vivado integration <https://gitlab.fel.cvut.cz/canbus/zynq/zynq-can-sja1000-top>`_
20 and Intel Cyclone V 5CSEMA4U23C6 based DE0-Nano-SoC Terasic board
21 `QSys integration <https://gitlab.fel.cvut.cz/canbus/intel-soc-ctucanfd>`_
23 `PCIe integration <https://gitlab.fel.cvut.cz/canbus/pcie-ctucanfd>`_ of the core.
33 version of emulation support can be cloned from ctu-canfd branch of QEMU local
34 development `repository <https://gitlab.fel.cvut.cz/canbus/qemu-canbus>`_.
38 ---------------
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | metafmt-d4xx.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _v4l2-meta-fmt-d4xx:
15 Intel D4xx (D435, D455 and others) cameras include per-frame metadata in their UVC
37 .. flat-table:: D4xx metadata
39 :header-rows: 1
40 :stub-columns: 0
42 * - **Field**
43 - **Description**
44 * - :cspan:`1` *Depth Control*
45 * - __u32 ID
[all …]
|
| /Documentation/tee/ |
| D | op-tee.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 OP-TEE (Open Portable Trusted Execution Environment)
7 The OP-TEE driver handles OP-TEE [1] based TEEs. Currently it is only the ARM
8 TrustZone based OP-TEE solution that is supported.
10 Lowest level of communication with OP-TEE builds on ARM SMC Calling
11 Convention (SMCCC) [2], which is the foundation for OP-TEE's SMC interface
12 [3] used internally by the driver. Stacked on top of that is OP-TEE Message
15 OP-TEE SMC interface provides the basic functions required by SMCCC and some
16 additional functions specific for OP-TEE. The most interesting functions are:
18 - OPTEE_SMC_FUNCID_CALLS_UID (part of SMCCC) returns the version information
[all …]
|
| /Documentation/hid/ |
| D | intel-ish-hid.rst | 6 processing to a dedicated low power co-processor. This allows the core
11 Sensor usage tables. These may be found in tablets, 2-in-1 convertible laptops
19 mainly use HID over I2C or USB. But ISH doesn't use either I2C or USB.
27 ----------------- ----------------------
28 | USB HID | --> | ISH HID |
29 ----------------- ----------------------
30 ----------------- ----------------------
31 | USB protocol | --> | ISH Transport |
32 ----------------- ----------------------
33 ----------------- ----------------------
[all …]
|
| /Documentation/driver-api/ |
| D | scsi.rst | 12 ---------------
23 The `SCSI protocol <https://www.t10.org/scsi-3.htm>`__ is a big-endian
24 peer-to-peer packet based protocol. SCSI commands are 6, 10, 12, or 16
28 are the default protocol for storage devices attached to USB, SATA, SAS,
31 TCP/IP (`iSCSI <https://en.wikipedia.org/wiki/ISCSI>`__), even `Parallel
35 ----------------------------------
46 In between is the SCSI mid-layer, analogous to a network routing layer
47 such as the IPv4 stack. The SCSI mid-layer routes a packet based data
56 The upper layer supports the user-kernel interface by providing device
60 --------------
[all …]
|
| /Documentation/arch/arm/ |
| D | marvell.rst | 13 ------------
16 - 88F5082
17 - 88F5181 a.k.a Orion-1
18 - 88F5181L a.k.a Orion-VoIP
19 - 88F5182 a.k.a Orion-NAS
21 …- Datasheet: https://web.archive.org/web/20210124231420/http://csclub.uwaterloo.ca/~board/ts7800/M…
22 …- Programmer's User Guide: https://web.archive.org/web/20210124231536/http://csclub.uwaterloo.ca/~…
23 …- User Manual: https://web.archive.org/web/20210124231631/http://csclub.uwaterloo.ca/~board/ts7800…
24 …- Functional Errata: https://web.archive.org/web/20210704165540/https://www.digriz.org.uk/ts78xx/8…
25 - 88F5281 a.k.a Orion-2
[all …]
|
12