Home
last modified time | relevance | path

Searched +full:permanently +full:- +full:attached (Results 1 – 9 of 9) sorted by relevance

/Documentation/devicetree/bindings/usb/
Dfsl,imx8mp-dwc3.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/usb/fsl,imx8mp-dwc3.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Li Jun <jun.li@nxp.com>
15 const: fsl,imx8mp-dwc3
19 - description: Address and length of the register set for HSIO Block Control
20 - description: Address and length of the register set for the wrapper of dwc3 core on the SOC.
22 "#address-cells":
25 "#size-cells":
[all …]
Dusb251xb.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
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
19 - microchip,usb2513bi
[all …]
/Documentation/driver-api/usb/
Dpersist.rst1 .. _usb-persist:
14 bus must continue to supply suspend current (around 1-5 mA). This
16 detect connect-change events (devices being plugged in or unplugged).
23 device is still attached or perhaps it was removed and a different
28 wakes up all the devices attached to that controller are treated as
38 Unfortunately problems _can_ arise, particularly with mass-storage
41 filesystem on the device, you're out of luck -- everything in that
57 suspend-to-RAM. On almost all systems, no suspend current is
58 available during hibernation (also known as swsusp or suspend-to-disk).
65 suspended -- but it will crash as soon as it wakes up, which isn't
[all …]
/Documentation/fb/
Dudlfb.rst15 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.
35 one-to-one with the fbdev interface, making the driver quite small and
66 At that point, a /dev/fb? interface will be present for user-mode applications
71 defio support enabled, to support a page-fault based detection mechanism
74 The most common client of udlfb is xf86-video-displaylink or a modified
75 xf86-video-fbdev X server. These servers have no real DisplayLink specific
103 Or to apply options permanently, create a modprobe configuration file
[all …]
/Documentation/networking/
Dnapi.rst1 .. SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
30 of the NAPI instance while the method is the driver-specific event
37 -----------
40 from the system. The instances are attached to the netdevice passed
55 ------------
64 argument - drivers can process completions for any number of Tx
96 or return ``budget - 1``.
101 -------------
109 As mentioned in the :ref:`drv_ctrl` section - napi_disable() and subsequent
118 --------------------------
[all …]
Dfilter.rst1 .. SPDX-License-Identifier: GPL-2.0
3 .. _networking-filter:
10 ------
17 ------------
24 BPF allows a user-space program to attach a filter onto any socket and
44 SO_LOCK_FILTER option allows to lock the filter attached to a socket. Once
49 The biggest user of this construct might be libpcap. Issuing a high-level
50 filter command like `tcpdump -i em1 port 22` passes through the libpcap
52 via SO_ATTACH_FILTER to the kernel. `tcpdump -i em1 port 22 -ddd`
57 qdisc layer, SECCOMP-BPF (SECure COMPuting [1]_), and lots of other places
[all …]
/Documentation/filesystems/xfs/
Dxfs-delayed-logging-design.rst1 .. SPDX-License-Identifier: GPL-2.0
33 details logged are made up of the changes to in-core structures rather than
34 on-disk structures. Other objects - typically buffers - have their physical
64 place. This means that permanent transactions can be used for one-shot
65 modifications, but one-shot reservations cannot be used for permanent
68 In the code, a one-shot transaction pattern looks somewhat like this::
97 While this might look similar to a one-shot transaction, there is an important
123 the on-disk journal.
165 transaction, we have to reserve enough space to record a full leaf-to-root split
183 For one-shot transactions, a single unit space reservation is all that is
[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
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).
68 and OS-specific code (e.g. FreeBSD and Linux). Such drivers tend to have
84 permanently connected as well as modern "SCSI" devices (e.g. USB or
[all …]
/Documentation/power/
Druntime_pm.rst5 (C) 2009-2011 Rafael J. Wysocki <rjw@sisk.pl>, Novell Inc.
18 put their PM-related work items. It is strongly recommended that pm_wq be
20 them to be synchronized with system-wide power transitions (suspend to RAM,
53 The ->runtime_suspend(), ->runtime_resume() and ->runtime_idle() callbacks
57 1. PM domain of the device, if the device's PM domain object, dev->pm_domain,
60 2. Device type of the device, if both dev->type and dev->type->pm are present.
62 3. Device class of the device, if both dev->class and dev->class->pm are
65 4. Bus type of the device, if both dev->bus and dev->bus->pm are present.
69 dev->driver->pm directly (if present).
73 and bus type. Moreover, the high-priority one will always take precedence over
[all …]