Searched +full:re +full:- +full:attached (Results 1 – 25 of 75) sorted by relevance
123
| /Documentation/driver-api/usb/ |
| D | persist.rst | 1 .. _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/admin-guide/ |
| D | bcache.rst | 11 This is the git repository of bcache-tools:
12 https://git.kernel.org/pub/scm/linux/kernel/git/colyli/bcache-tools.git/
17 It's designed around the performance characteristics of SSDs - it only allocates
25 great lengths to protect your data - it reliably handles unclean shutdown. (It
27 writes as completed until they're on stable storage).
29 Writeback caching can use most of the cache for buffering writes - writing
36 average is above the cutoff it will skip all IO from that task - instead of
47 You'll need bcache util from the bcache-tools repository. Both the cache device
50 bcache make -B /dev/sdb
51 bcache make -C /dev/sdc
[all …]
|
| /Documentation/arch/arm64/ |
| D | asymmetric-32bit.rst | 2 Asymmetric 32-bit SoCs
7 This document describes the impact of asymmetric 32-bit SoCs on the
8 execution of 32-bit (``AArch32``) applications.
10 Date: 2021-05-17
16 of the CPUs are capable of executing 32-bit user applications. On such
19 ``execve(2)`` of 32-bit ELF binaries, with the latter returning
20 ``-ENOEXEC``. If the mismatch is detected during late onlining of a
21 64-bit-only CPU, then the onlining operation fails and the new CPU is
25 running legacy 32-bit binaries. Unsurprisingly, that doesn't work very
28 It seems inevitable that future SoCs will drop 32-bit support
[all …]
|
| /Documentation/admin-guide/media/ |
| D | building.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 distribution-specific source file or via the Kernel's main git tree\ [1]_.
12 - you're a braveheart and want to experiment with new stuff;
13 - if you want to report a bug;
14 - if you're developing new patches
23 https://linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers
50 Device Drivers --->
51 <M> Remote Controller support --->
54 [*] HDMI CEC drivers --->
55 <*> Multimedia support --->
[all …]
|
| /Documentation/ABI/stable/ |
| D | firewire-cdev | 1 What: /dev/fw[0-9]+
4 Contact: linux1394-devel@lists.sourceforge.net
7 firewire-core and IEEE 1394 device drivers implemented in
8 userspace. The ioctl(2)- and read(2)-based ABI is defined and
9 documented in <linux/firewire-cdev.h>.
11 This ABI offers most of the features which firewire-core also
18 - The 1394 node which is associated with the file:
20 - Asynchronous request transmission
21 - Get the Configuration ROM
22 - Query node ID
[all …]
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | cgroups.rst | 6 Documentation/admin-guide/cgroup-v1/cpusets.rst
12 Portions Copyright (c) 2004-2006 Silicon Graphics, Inc.
42 ----------------------
56 schedules a resource or applies per-cgroup limits, but it may be
62 hierarchy, and a set of subsystems; each subsystem has system-specific
63 state attached to each cgroup in the hierarchy. Each hierarchy has
69 User-level code may create and destroy cgroups by name in an
79 access. For example, cpusets (see Documentation/admin-guide/cgroup-v1/cpusets.rst) allow
83 .. _cgroups-why-needed:
86 ----------------------------
[all …]
|
| D | cpusets.rst | 11 - Portions Copyright (c) 2004-2006 Silicon Graphics, Inc.
12 - Modified by Paul Jackson <pj@sgi.com>
13 - Modified by Christoph Lameter <cl@linux.com>
14 - Modified by Paul Menage <menage@google.com>
15 - Modified by Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
41 ----------------------
45 an on-line node that contains memory.
54 Documentation/admin-guide/cgroup-v1/cgroups.rst.
73 ----------------------------
77 non-uniform access times (NUMA) presents additional challenges for
[all …]
|
| /Documentation/hwmon/ |
| D | mlxreg-fan.rst | 1 Kernel driver mlxreg-fan
6 - QMB700, equipped with 40x200GbE InfiniBand ports;
7 - MSN3700, equipped with 32x200GbE or 16x400GbE Ethernet ports;
8 - MSN3410, equipped with 6x400GbE plus 48x50GbE Ethernet ports;
9 - MSN3800, equipped with 64x1000GbE Ethernet ports;
14 board with Mellanox Quantum or Spectrume-2 devices.
36 This setup can be re-programmed with other registers.
39 -----------
45 device. PWM and tachometers are sensed through the on-board programmable
46 device, which exports its register map. This device could be attached to
[all …]
|
| /Documentation/fb/ |
| D | sh7760fb.rst | 6 -----------
22 a) if you're using 15/16bit color modes at >= 640x480 px resolutions,
29 - drivers/video/sh7760fb.c
30 - include/asm-sh/sh7760fb.h
31 - Documentation/fb/sh7760fb.rst
34 -----------------
47 --------------------
49 attached. Data must be wrapped in a "struct sh7760fb_platdata" and
62 * NEC NL6440bc26-01 640x480 TFT
82 .left_margin = 114, /* HTOT - (HSYNSLEN + HSYNSTART) */
[all …]
|
| /Documentation/filesystems/xfs/ |
| D | xfs-delayed-logging-design.rst | 1 .. 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/admin-guide/pm/ |
| D | cpufreq.rst | 1 .. SPDX-License-Identifier: GPL-2.0
20 Operating Performance Points or P-states (in ACPI terminology). As a rule,
24 time (or the more power is drawn) by the CPU in the given P-state. Therefore
29 as possible and then there is no reason to use any P-states different from the
30 highest one (i.e. the highest-performance frequency/voltage configuration
38 put into different P-states.
41 capacity, so as to decide which P-states to put the CPUs into. Of course, since
64 information on the available P-states (or P-state ranges in some cases) and
65 access platform-specific hardware interfaces to change CPU P-states as requested
70 performance scaling algorithms for P-state selection can be represented in a
[all …]
|
| /Documentation/networking/device_drivers/can/ |
| D | can327.rst | 1 .. 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
50 -----------
59 ----------------------------------
65 be attached on a command prompt as follows::
[all …]
|
| /Documentation/networking/ |
| D | rxrpc.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 The RxRPC protocol driver provides a reliable two-phase transport on top of UDP
38 RxRPC is a two-layer protocol. There is a session layer which provides
44 +-------------+
46 +-------------+
48 +-------------+
50 +-------------+
52 +-------------+
60 (2) A two-phase protocol. The client transmits a blob (the request) and then
81 (2) provided with a protocol of the type of underlying transport they're going
[all …]
|
| D | rds.rst | 1 .. SPDX-License-Identifier: GPL-2.0
14 http://oss.oracle.com/pipermail/rds-devel/2007-November/000228.html
22 cluster - so in a cluster with N processes you need N sockets, in contrast
23 to N*N if you use a connection-oriented socket transport like TCP.
25 RDS is not Infiniband-specific; it was designed to support different
29 The high-level semantics of RDS from the application's point of view are
39 transport has to be IP-based. In fact, RDS over IB uses a
59 a active-active HA scenario), but only as long as the address
72 to create RDS sockets. SOL_RDS is the socket-level to be used
87 This is a soft limit rather than a hard limit - RDS will
[all …]
|
| /Documentation/netlink/specs/ |
| D | netdev.yaml | 1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
9 -
11 name: xdp-act
12 render-max: true
14 -
19 -
23 -
24 name: ndo-xmit
27 -
28 name: xsk-zerocopy
[all …]
|
| /Documentation/driver-api/ |
| D | device_link.rst | 31 supplier is bound to a driver, and they're unbound before the supplier
57 device ``->probe`` callback or a boot-time PCI quirk.
61 ``->probe`` callback while the supplier hasn't started to probe yet: Had the
65 non-presence. [Note that it is valid to create a link from the consumer's
66 ``->probe`` callback while the supplier is still probing, but the consumer must
72 is added in the ``->probe`` callback of the supplier or consumer driver, it is
73 typically deleted in its ``->remove`` callback for symmetry. That way, if the
87 link is added from the consumer's ``->probe`` callback: ``DL_FLAG_RPM_ACTIVE``
93 Similarly, when the device link is added from supplier's ``->probe`` callback,
125 :c:func:`device_link_add()` may cause the PM-runtime usage counter of the
[all …]
|
| /Documentation/PCI/ |
| D | pci-error-recovery.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 :Authors: - Linas Vepstas <linasvepstas@gmail.com>
9 - Richard Lary <rlary@us.ibm.com>
10 - Mike Mason <mmlnx@us.ibm.com>
16 chipsets are able to deal with these errors; these include PCI-E chipsets,
17 and the PCI-host bridges found on IBM Power4, Power5 and Power6-based
32 including multiple instances of a device driver on multi-function
34 waiting for some i/o-space register to change, when it never will.
39 is forced by the need to handle multi-function devices, that is,
42 of reset it desires, the choices being a simple re-enabling of I/O
[all …]
|
| D | sysfs-pci.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 |-- 0000:17:00.0
12 | |-- class
13 | |-- config
14 | |-- device
15 | |-- enable
16 | |-- irq
17 | |-- local_cpus
18 | |-- remove
19 | |-- resource
[all …]
|
| /Documentation/trace/rv/ |
| D | runtime-verification.rst | 10 Instead of relying on a fine-grained model of a system (e.g., a
11 re-implementation a instruction level), RV works by analyzing the trace of the
17 that require a re-implementation of the entire system in a modeling language.
20 events, avoiding, for example, the propagation of a failure on safety-critical
32 system, a set of instances of the monitor (per-cpu monitor, per-task monitor,
36 Linux +---- RV Monitor ----------------------------------+ Formal
38 +-------------------+ +----------------+ +-----------------+
40 | Tracing | -> | Instance(s) | <- | Model |
42 +-------------------+ +----------------+ +-----------------+
45 | +----------+ |
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-pci | 4 Contact: linux-pci@vger.kernel.org
15 (Note: kernels before 2.6.28 may require echo -n).
20 Contact: linux-pci@vger.kernel.org
31 (Note: kernels before 2.6.28 may require echo -n).
36 Contact: linux-pci@vger.kernel.org
55 Contact: Chris Wright <chrisw@sous-sol.org>
72 Contact: Linux PCI developers <linux-pci@vger.kernel.org>
74 Writing a non-zero value to this attribute will
76 re-discover previously removed devices.
80 Contact: Linux PCI developers <linux-pci@vger.kernel.org>
[all …]
|
| /Documentation/hid/ |
| D | uhid.rst | 2 UHID - User-space I/O driver support for HID subsystem
5 UHID allows user-space to implement HID transport drivers. Please see
6 hid-transport.rst for an introduction into HID transport drivers. This document
9 With UHID, a user-space transport driver can create kernel hid-devices for each
10 device connected to the user-space controlled bus. The UHID API defines the I/O
11 events provided from the kernel to user-space and vice versa.
13 There is an example user-space application in ./samples/uhid/uhid-example.c
16 ------------
18 UHID is accessed through a character misc-device. The minor number is allocated
25 write()'ing "struct uhid_event" objects. Non-blocking operations are supported
[all …]
|
| /Documentation/driver-api/surface_aggregator/clients/ |
| D | dtx.rst | 1 .. SPDX-License-Identifier: GPL-2.0+
10 User-Space DTX (Clipboard Detachment System) Interface
14 and re-attachment handling. To this end, it provides the ``/dev/surface/dtx``
15 device file, through which it can interface with a user-space daemon. This
17 actions, such as unmounting devices attached to the base,
18 unloading/reloading the graphics-driver, user-notifications, etc.
24 change. Commands are always driver-initiated, whereas events are always
40 The mechanism keeping the clipboard attached to the base in normal
56 ------------
65 being hot-unplugged while in use. More details can be found in the
[all …]
|
| /Documentation/scheduler/ |
| D | sched-util-clamp.rst | 1 .. SPDX-License-Identifier: GPL-2.0
57 foreground, top-app, etc. Util clamp can be used to constrain how much
60 the ones belonging to the currently active app (top-app group). Beside this
65 1. The big cores are free to run top-app tasks immediately. top-app
106 Note that by design RT tasks don't have per-task PELT signal and must always
114 See :ref:`section 3.4 <uclamp-default-values>` for default values and
115 :ref:`3.4.1 <sched-util-clamp-min-rt-default>` on how to change RT tasks
142 To be able to aggregate the util clamp value of all the tasks attached to the
150 task on the rq to only a subset of tasks on the top-most bucket.
157 uclamp value of the rq. See :ref:`section 2.1 <uclamp-buckets>` for details on
[all …]
|
| /Documentation/devicetree/ |
| D | usage-model.rst | 1 .. SPDX-License-Identifier: GPL-2.0
44 ----------
56 In 2005, when PowerPC Linux began a major cleanup and to merge 32-bit
57 and 64-bit support, the decision was made to require DT support on all
61 blob without requiring a real Open Firmware implementation. U-Boot,
66 existing non-DT aware firmware.
74 -------------
79 -------------------
88 per-machine hard coded selections.
101 ---------------------------
[all …]
|
| /Documentation/input/joydev/ |
| D | joystick.rst | 3 .. _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 …]
|
123