Home
last modified time | relevance | path

Searched +full:usb +full:- +full:attach (Results 1 – 20 of 20) sorted by relevance

/Documentation/devicetree/bindings/usb/
Dqcom,pmic-typec.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/usb/qcom,pmic-typec.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Qualcomm PMIC based USB Type-C block
10 - Bryan O'Donoghue <bryan.odonoghue@linaro.org>
13 Qualcomm PMIC Type-C block
18 - enum:
19 - qcom,pmi632-typec
20 - qcom,pm8150b-typec
[all …]
Drichtek,rt1719.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/usb/richtek,rt1719.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Richtek RT1719 sink-only Type-C PD controller
10 - ChiYuan Huang <cy_huang@richtek.com>
13 The RT1719 is a sink-only USB Type-C controller that complies with the latest
14 USB Type-C and PD standards. It does the USB Type-C detection including attach
15 and orientation. It integrates the physical layer of the USB BMC power
17 support for alternative interfaces of the Type-C specification.
[all …]
Drichtek,rt1711h.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/usb/richtek,rt1711h.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Richtek RT1711H Type-C Port Switch and Power Delivery controller
10 - Gene Chen <gene_chen@richtek.com>
13 The RT1711H is a USB Type-C controller that complies with the latest
14 USB Type-C and PD standards. It does the USB Type-C detection including attach
15 and orientation. It integrates the physical layer of the USB BMC power
17 support for alternative interfaces of the Type-C specification.
[all …]
Dusb251xb.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/usb/usb251xb.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Microchip USB 2.0 Hi-Speed Hub Controller
10 - Richard Leitner <richard.leitner@skidata.com>
15 - microchip,usb2422
16 - microchip,usb2512b
17 - microchip,usb2512bi
18 - microchip,usb2513b
[all …]
/Documentation/usb/
Dfunctionfs.rst9 unique behaviour. It may be added to an USB configuration only after
28 For more information about FunctionFS descriptors see :doc:`functionfs-desc`
51 $ mkdir /dev/ffs-mtp && mount -t functionfs mtp /dev/ffs-mtp
52 $ ( cd /dev/ffs-mtp && mtp-daemon ) &
53 $ mkdir /dev/ffs-hid && mount -t functionfs hid /dev/ffs-hid
54 $ ( cd /dev/ffs-hid && hid-daemon ) &
56 On kernel level the gadget checks ffs_data->dev_name to identify
64 parameter's value is just a one-element list, then the behaviour
69 filesystems have been mounted and USB descriptors of all functions
72 Conversely, the gadget is unregistered after the first USB function
[all …]
Dusbip_protocol.rst2 USB/IP protocol
8 The USB/IP protocol follows a server/client architecture. The server exports the
9 USB devices and the clients import them. The device driver for the exported
10 USB device runs on the client machine.
12 The client may ask for the list of the exported USB devices. To get the list the
16 the OP_REP_DEVLIST packet which lists the exported USB devices. Finally the
21 virtual host controller usb host
23 (imports USB devices) (exports USB devices)
26 | ----------------------------------------------> |
29 | <---------------------------------------------- |
[all …]
/Documentation/iio/
Diio_dmabuf_api.rst1 .. SPDX-License-Identifier: GPL-2.0
4 High-speed DMABUF interface for IIO
11 file-based interface, with read() and write() access calls through the
15 can attach DMABUF objects (externally created) to an IIO buffer, and
20 zero-copy fashion, for instance between IIO and the USB stack.
22 The userspace application can also memory-map the DMABUF objects, and
25 kernel and userspace. This is particularly useful for high-speed devices
27 It does however increase the userspace-kernelspace synchronization
39 Attach the DMABUF object, identified by its file descriptor, to the
/Documentation/driver-api/
Dsm501.rst10 which may provide numerous interfaces including USB host controller USB gadget,
15 ----
29 The core re-uses the platform device system as the platform device
31 need to create a new bus-type and the associated code to go with it.
35 ---------
43 as this is by-far the most resource-sensitive of the on-chip functions.
59 -------------
69 There is an errata (AB-5) affecting the selection of the
74 attach if the PLL selection is different.
/Documentation/filesystems/
D9p.rst1 .. SPDX-License-Identifier: GPL-2.0
26 http://xcpu.org/papers/xcpu-talk.pdf
30 http://xcpu.org/papers/cellfs-talk.pdf
33 * VirtFS: A Virtualization Aware File System pass-through
34 https://kernel.org/doc/ols/2010/ols2010-pages-109-120.pdf
41 mount -t 9p 10.10.1.2 /mnt/9
45 mount -t 9p `namespace`/acme /mnt/9 -o trans=unix,uname=$USER
49 mount -t 9p -o trans=virtio <mount_tag> /mnt/9
59 To mount a 9p FS on a USB Host accessible via the gadget at runtime::
61 mount -t 9p -o trans=usbg,aname=/path/to/fs <device> /mnt/9
[all …]
/Documentation/hid/
Dhiddev.rst8 In addition to the normal input type HID devices, USB also uses the
14 To support these disparate requirements, the Linux USB system provides
18 normalised event interface - see Documentation/input/input.rst
24 usb.c ---> hid-core.c ----> hid-input.c ----> [keyboard/mouse/joystick/event]
27 --> hiddev.c ----> POWER / MONITOR CONTROL
29 In addition, other subsystems (apart from USB) can potentially feed
36 The hiddev interface is a char interface using the normal USB major,
40 mknod /dev/usb/hiddev0 c 180 96
41 mknod /dev/usb/hiddev1 c 180 97
42 mknod /dev/usb/hiddev2 c 180 98
[all …]
Dhid-transport.rst6 only USB was supported, but other specifications adopted the HID design and
7 provided new transport drivers. The kernel includes at least support for USB,
8 Bluetooth, I2C and user-space I/O drivers.
17 report-parsing, report interpretation and the user-space API. Device specifics
22 +-----------+ +-----------+ +-----------+ +-----------+
24 +-----------+ +-----------+ +-----------+ +-----------+
26 +------------+ +------------+
28 +------------+ +------------+
30 +------------------+ +------------------+
32 +------------------+ +------------------+
[all …]
/Documentation/fb/
Dudlfb.rst5 This is a driver for DisplayLink USB 2.0 era graphics chips.
9 USB wire. That hardware framebuffer is able to drive the VGA, DVI, or HDMI
15 pixels line-by-line via USB bulk transfers.
18 does not require any acks - the effect is very low latency that
20 non-gaming and non-video applications.
23 setting is very flexible - able to set nearly arbitrary modes from any timing.
25 Advantages of USB graphics in general:
27 * Ability to add a nearly arbitrary number of displays to any USB 2.0
29 (FB_MAX is currently 32). Of course, all USB devices on the same
30 host controller share the same 480Mbs USB 2.0 interface.
[all …]
/Documentation/input/joydev/
Djoystick.rst3 .. _joystick-doc:
14 linux-input@vger.kernel.org
16 send "subscribe linux-input" to majordomo@vger.kernel.org to subscribe to it.
25 ---------
29 usually packaged as ``joystick``, ``input-utils``, ``evtest``, and so on.
35 ------------
48 ln -s input/js0 js0
49 ln -s input/js1 js1
50 ln -s input/js2 js2
51 ln -s input/js3 js3
[all …]
/Documentation/ABI/testing/
Dsysfs-class-extcon14 the 30-pin port of Nuri board (/arch/arm/mach-exynos)
16 video, and USB cables attached simultaneously.
36 attach/detach information of the corresponding extcon object.
98 Note that mutually_exclusive is a sub-directory of the extcon
100 directory show the mutually-exclusive sets, not the contents
/Documentation/networking/device_drivers/can/
Dcan327.rst1 .. SPDX-License-Identifier: (GPL-2.0-only OR BSD-3-Clause)
7 --------
14 -----------
26 -------------
33 order to fake full-duplex operation.
36 enough to implement simple request-response protocols (such as OBD II),
39 Most ELM327s come as nondescript serial devices, attached via USB or
41 is up to the user to attach it in form of a TTY line discipline
50 -----------
58 How to attach the line discipline
[all …]
/Documentation/driver-api/media/drivers/
Dpvrusb2.rst1 .. SPDX-License-Identifier: GPL-2.0
9 ----------
11 This driver is intended for the "Hauppauge WinTV PVR USB 2.0", which
12 is a USB 2.0 hosted TV Tuner. This driver is a work in progress.
13 Its history started with the reverse-engineering effort by Björn
29 1. Low level wire-protocol implementation with the device.
38 tear-down, arbitration, and interaction with high level
61 --------
70 --------------------------------------
76 pvrusb2-audio.[ch] - This is glue logic that resides between this
[all …]
/Documentation/dev-tools/
Dkcov.rst5 for coverage-guided fuzzing. Coverage data of a running kernel is exported via
13 inherently non-deterministic parts of the kernel (e.g. scheduler, locking).
24 -------------
41 mount -t debugfs none /sys/kernel/debug
44 -------------------
49 .. code-block:: c
80 if (fd == -1)
85 /* Mmap buffer shared between kernel- and user-space. */
96 read(-1, NULL, 0);
134 The interface is fine-grained to allow efficient forking of test processes.
[all …]
/Documentation/scsi/
Dscsi_mid_low_api.rst1 .. SPDX-License-Identifier: GPL-2.0
4 SCSI mid_level - lower_level driver interface
14 (SCSI terminology, see SAM-3 at http://www.t10.org) sends SCSI commands
20 its own subsystem in Linux (e.g. USB and ieee1394). In such cases the
22 Examples are the usb-storage driver (found in the drivers/usb/storage
30 HBAs. These HBAs might be either on PCI daughter-boards or built into
33 has its own PCI device address. [The one-to-one correspondence between
49 documented in Documentation/scsi (e.g. aic7xxx.rst). The SCSI mid-level is
53 scsi-generic.rst (for the sg driver).
57 about the USB mass storage driver see the
[all …]
/Documentation/admin-guide/
Dreporting-issues.rst1 .. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0)
36 ensure it's vanilla (IOW: not patched and not using add-on modules). Also make
44 to pin-point the culprit with a bisection; if you succeed, include its
45 commit-id and CC everyone in the sign-off-by chain.
51 Step-by-step guide how to report issues to the kernel maintainers
58 step-by-step approach. It still tries to be brief for readability and leaves
59 out a lot of details; those are described below the step-by-step guide in a
89 kernel modules on-the-fly, which solutions like DKMS might be doing locally
169 --------------------------------------------------------------
204 -------------------------------------------------------------
[all …]
/Documentation/sound/kernel-api/
Dwriting-an-alsa-driver.rst11 Architecture) <http://www.alsa-project.org/>`__ driver. The document
19 low-level driver implementation details. It only describes the standard
26 -------
49 /usb
56 --------------
60 sub-directories contain different modules and are dependent upon the
74 This directory and its sub-directories are for the ALSA sequencer. This
76 as snd-seq-midi, snd-seq-virmidi, etc. They are compiled only when
85 -----------------
88 to be exported to user-space, or included by several files in different
[all …]