Searched full:are (Results 1 – 25 of 10726) sorted by relevance
12345678910>>...430
| /Linux-v5.10/Documentation/input/ |
| D | gamepad.rst | 12 document defines how gamepads are supposed to report their data.
44 4 buttons in diamonds-shape (on the right side). The buttons are
56 all devices have both or any, but they are present at most times.
59 Triggers are located on the upper-side of the pad in vertical direction.
60 Not all devices provide them, but the upper buttons are normally named
63 Many devices provide force-feedback features. But are mostly just
79 All new gamepads are supposed to comply with this mapping. Please report any
82 There are a lot of less-featured/less-powerful devices out there, which re-use
103 of the labels on the buttons, the codes are sent according to the
106 Please note that 2- and 3-button pads are fairly rare and old. You might
[all …]
|
| /Linux-v5.10/Documentation/fb/ |
| D | api.rst | 13 buffer core are not described.
24 Device and driver capabilities are reported in the fixed screen information
39 When supported, formats are configured using a FOURCC instead of manually
46 Pixels are stored in memory in hardware-dependent formats. Applications need
50 Formats are described by frame buffer types and visuals. Some visuals require
51 additional information, which are stored in the variable screen information
55 macropixels. Types describe how macropixels are stored in memory. The following
56 types and visuals are supported.
60 Macropixels are stored contiguously in a single plane. If the number of bits
61 per macropixel is not a multiple of 8, whether macropixels are padded to the
[all …]
|
| /Linux-v5.10/sound/pci/cs46xx/ |
| D | cs46xx.h | 173 * The following defines are for the flags in the host interrupt status
208 * The following defines are for the flags in the host signal register 0.
245 * The following defines are for the flags in the host interrupt control
252 * The following defines are for the flags in the DMA status register.
260 * The following defines are for the flags in the host DMA source address
275 * The following defines are for the flags in the host DMA destination address
290 * The following defines are for the flags in the host DMA control register.
299 * The following defines are for the flags in the host DMA control register.
329 * The following defines are for the flags in the performance monitor control
356 * The following defines are for the flags in the performance counter value 1
[all …]
|
| /Linux-v5.10/Documentation/userspace-api/media/v4l/ |
| D | colorspaces.rst | 20 the human eye has color receptors that are sensitive to three different
22 color. Be glad you are not a mantis shrimp as those are sensitive to 12
27 color receptors are stimulated. This is based on the Spectral Power
35 those receptors and are perceived as the same color, even though the SPD
43 After some further mathematical transforms these stimuli are known as
45 color as perceived by a human unambiguously. These X, Y and Z values are
56 The x and y values are the chromaticity coordinates and can be used to
59 colors are specified with lower case 'x' and 'y', then the CIE xyY
64 will find reading resources that go into much more detail if you are
71 phosphors used in the displays. These *color primaries* are part of what
[all …]
|
| /Linux-v5.10/Documentation/livepatch/ |
| D | livepatch.rst | 28 There are many situations where users are reluctant to reboot a system. It may
39 There are multiple mechanisms in the Linux kernel that are directly related
43 - The kernel probes are the most generic. The code can be redirected by
52 are in any way modified.
56 Most of these problems are solved by using the dynamic ftrace framework as
59 a live patch is called with the help of a custom ftrace handler. But there are
66 Functions are there for a reason. They take some input parameters, get or
73 Most of these changes are self contained and the function presents itself
77 But there are more complex fixes. For example, a patch might change
83 when it is safe to do so, e.g. when the affected locks are released
[all …]
|
| /Linux-v5.10/Documentation/ |
| D | atomic_t.txt | 5 RMW operations between CPUs (atomic operations on MMIO are not supported and
82 The non-RMW ops are (typically) regular LOADs and STOREs and are canonically
86 and are doing it wrong.
91 C Atomic-RMW-ops-are-atomic-WRT-atomic_set
142 these are limited to the arithmetic operations because those are
143 reversible. Bitops are irreversible and therefore the modified value
150 - misc; the special purpose operations that are commonly used and would,
152 are time critical and can, (typically) on LL/SC architectures, be more
155 All these operations are SMP atomic; that is, the operations (for a single
165 - non-RMW operations are unordered;
[all …]
|
| /Linux-v5.10/Documentation/admin-guide/pm/ |
| D | suspend-flows.rst | 26 different sleep states of the system are quite similar, but there are some
36 states are mostly identical, so they both together will be referred to as
45 The following steps are taken in order to transition the system from the working
58 Tasks are frozen primarily in order to avoid unchecked hardware accesses
64 All user space tasks are intercepted as though they were sent a signal and
69 specific reasons are frozen subsequently, but they are not intercepted.
70 Instead, they are expected to periodically check whether or not they need
79 Devices are suspended in four phases called *prepare*, *suspend*,
87 phase and high-level ("action") interrupt handlers are prevented from being
90 Interrupts are still handled after that, but they are only acknowledged to
[all …]
|
| /Linux-v5.10/Documentation/process/ |
| D | howto.rst | 31 are not a good substitute for a solid C education and/or years of
32 experience, the following books are good for, if anything, reference:
39 adheres to the ISO C89 standard, it uses a number of extensions that are
42 portions of the C standard are not supported. Arbitrary long long
43 divisions and floating point are not allowed. It can sometimes be
49 Please remember that you are trying to learn how to work with the
54 possible about these standards ahead of time, as they are well
64 rules and how to use `SPDX <https://spdx.org/>`_ identifiers in source code are
67 not ask on the Linux kernel mailing list. The people on the mailing lists are
78 The Linux kernel source tree has a large range of documents that are
[all …]
|
| /Linux-v5.10/Documentation/vm/ |
| D | hugetlbfs_reserv.rst | 10 Huge pages as described at :ref:`hugetlbpage` are typically
11 preallocated for application use. These huge pages are instantiated in a
12 task's address space at page fault time if the VMA indicates huge pages are
28 This description is primarily targeted at kernel developers who are modifying
37 huge pages are only available to the task which reserved them.
62 The 'from' and 'to' fields of the file region structure are huge page
67 These are stored in the bottom bits of the reservation map pointer.
89 of mappings. Location differences are:
95 inode->i_mapping->private_data. Since shared mappings are always backed
103 Reservations are created when a huge page backed shared memory segment is
[all …]
|
| /Linux-v5.10/Documentation/admin-guide/device-mapper/ |
| D | statistics.rst | 6 regions of a DM device. If no regions are defined no statistics are
8 devices are currently supported.
14 The I/O statistics counters for each step-sized area of a region are
16 Documentation/admin-guide/iostats.rst). But two extra counters (12 and 13) are
22 The reported times are in milliseconds and the granularity depends on
24 reported times are in nanoseconds.
65 The following optional arguments are supported:
70 used, the resulting times are in nanoseconds instead of
71 milliseconds. Precise timestamps are a little bit slower
75 numbers n1, n2, etc are times that represent the boundaries
[all …]
|
| /Linux-v5.10/Documentation/admin-guide/LSM/ |
| D | Smack.rst | 15 are encouraged to compare Smack with the other mechanisms
22 - Basic utilities, which are helpful but not required
32 configurations are intolerant of IP options and can impede
44 There are five commands included in smackutil:
56 These two commands are obsolete with the introduction of
78 objects. The attributes are stored in the extended attribute security
82 The extended attributes that Smack uses are:
118 There are multiple ways to set a Smack label on a file::
177 The following numbers are the categories::
189 The following numbers are the categories::
[all …]
|
| /Linux-v5.10/Documentation/filesystems/ |
| D | ext2.rst | 10 filesystem in use by Linux. There are also implementations available
16 Most defaults are determined by the filesystem superblock, and can be
17 set using tune2fs(8). Kernel-determined defaults are indicated by (*).
79 compression though these are not yet implemented (some are available as
87 The space in the device or file is split up into blocks. These are
96 Blocks are clustered into block groups in order to reduce fragmentation
100 Two blocks near the start of each group are reserved for the block usage
102 are in use. Since each bitmap is limited to a single block, this means
105 The block(s) following the bitmaps in each block group are designated
106 as the inode table for that block group and the remainder are the data
[all …]
|
| D | squashfs.rst | 10 directories. Inodes in the system are very small and all blocks are packed to
11 minimise data overhead. Block sizes greater than 4K are supported up to a
51 directory data are highly compacted, and packed on byte boundaries. Each
100 Compressed data blocks are written to the filesystem as files are read from
103 xattr tables are written.
110 these are stored here.
115 Metadata (inodes and directories) are compressed in 8Kbyte blocks. Each
120 Inodes are packed into the metadata blocks, and are not aligned to block
121 boundaries, therefore inodes overlap compressed blocks. Inodes are identified
126 To maximise compression there are different inodes for each file type
[all …]
|
| /Linux-v5.10/net/netlabel/ |
| D | netlabel_mgmt.h | 23 * The following NetLabel payloads are supported by the management interface.
33 * If IPv4 is specified the following attributes are required:
38 * If IPv6 is specified the following attributes are required:
43 * If using NETLBL_NLTYPE_CIPSOV4 the following attributes are required:
47 * If using NETLBL_NLTYPE_UNLABELED no other attributes are required,
71 * If the IP address selectors are not used the following attribute is
76 * If the IP address selectors are used then the following attritbute is
82 * attributes are required:
87 * attributes are required.
97 * If using NETLBL_NLTYPE_CIPSOV4 the following attributes are required:
[all …]
|
| /Linux-v5.10/Documentation/hid/ |
| D | hid-transport.rst | 15 drivers on top of it. The transport drivers are responsible of raw data
18 and quirks are handled by all layers depending on the quirk.
62 drivers are not required to register themselves with HID core. HID core is never
63 aware of which transport drivers are available and is not interested in it. It
68 this struct are used by HID core to communicate with the device.
70 Transport drivers are responsible of detecting device failures and unplugging.
100 reports. No management commands or data acknowledgements are sent on this
103 send their input events on this channel. Outgoing events are normally
107 channel and are normally ignored. Instead, devices only send management
111 Outgoing reports are usually sent on the ctrl channel via synchronous
[all …]
|
| /Linux-v5.10/Documentation/driver-api/media/ |
| D | camera-sensor.rst | 16 input parameters that are specific to the hardware:: the external clock frequency
17 and the link frequency. The two parameters generally are obtained from system
20 The reason why the clock frequencies are so important is that the clock signals
23 elsewhere. Therefore only the pre-determined frequencies are configurable by the
29 There are two distinct ways to configure the frame size produced by camera
46 they control based on user requests, are limited to a number of preset
48 level are independent. How a driver picks such configuration is based on the
51 Most sensor drivers are implemented this way, see e.g.
57 There are two different methods for obtaining possibilities for different frame
78 Horizontal and vertical blanking are specified by ``V4L2_CID_HBLANK`` and
[all …]
|
| /Linux-v5.10/Documentation/devicetree/ |
| D | writing-schema.rst | 6 Devicetree bindings are written using json-schema vocabulary. Schema files are
16 top-level json-schema properties used are:
46 schema. By default without 'select', nodes are matched against their possible
56 binding. The exact schema syntax depends on whether properties are known,
57 common properties (e.g. 'interrupts') or are binding/vendor specific properties.
65 Optional. Similar to 'properties', but names are regex.
75 Unless noted otherwise, all properties are required.
82 vocabulary for that property. The properties schemas are what is used for
86 binding schema need to be defined such as how many values are valid or what
87 possible values are valid.
[all …]
|
| /Linux-v5.10/arch/arm/mach-s3c/ |
| D | Kconfig.s3c24xx | 97 Common power management code for systems that are
179 Say Y here if you are using the American Microsystems M5900 Series
195 Say Y here if you are using the Simtec Electronics EB2410ITX
213 Say Y here if you are using the HP IPAQ H1940
236 Say Y here if you are using the Nex Vision OTOM board
243 Say Y here if you are using the Armzone QT2410
250 Say Y here if you are using the SMDK2410 or the derived module A9M2410
257 Say Y here if you are using the TinCanTools Hammer Board
269 Say Y here if you are using the Thorcom VR1000 board.
307 Say Y here if you are using the Logitech Jive.
[all …]
|
| /Linux-v5.10/Documentation/core-api/ |
| D | this_cpu_ops.rst | 8 this_cpu operations are a way of optimizing access to per cpu
18 This means that there are no atomicity issues between the calculation of
24 Read-modify-write operations are of particular interest. Frequently
32 synchronization is not necessary since we are dealing with per cpu
34 processor should be accessing that variable and therefore there are no
37 Please note that accesses by remote processors to a per cpu area are
45 are defined. These operations can be used without worrying about
116 the value of the individual counters for each processor are
120 Per cpu variables are used for performance reasons. Bouncing cache
190 Operations on these fields are straightforward::
[all …]
|
| D | workqueue.rst | 13 There are many cases where an asynchronous process execution context
22 While there are work items on the workqueue the worker executes the
82 worker threads become idle. These worker threads are managed in so
89 There are two worker-pools, one for normal work items and the other
96 aspects of the way the work items are executed by setting flags on the
97 workqueue they are putting the work item on. These flags include
110 (how many execution contexts are active) is an important issue. cmwq
118 number of the currently runnable workers. Generally, work items are
121 stalling should be optimal. As long as there are one or more runnable
125 are pending work items. This allows using a minimal number of workers
[all …]
|
| /Linux-v5.10/Documentation/virt/kvm/ |
| D | vcpu-requests.rst | 12 /* Check if any requests are pending for VCPU @vcpu. */
39 (kvm_make_request() calls) are followed by a call to kvm_vcpu_kick(),
50 thread, there are two other actions a kick may take. All three actions
51 are listed below:
54 2) Waking a sleeping VCPU. Sleeping VCPUs are VCPU threads outside guest
67 ensure VCPU requests are seen by VCPUs (see "Ensuring Requests Are Seen"),
69 even to ensure IPI acknowledgements are waited upon (see "Waiting for
70 Acknowledgements"). The following modes are defined:
94 VCPU requests are simply bit indices of the ``vcpu->requests`` bitmap.
101 break the abstraction. The first 8 bits are reserved for architecture
[all …]
|
| /Linux-v5.10/Documentation/driver-api/ |
| D | device_link.rst | 8 that are borne out of a parent/child relationship within the device
10 are ordered based on this relationship, i.e. children are always suspended
30 presence on the supplier. The consumer devices are not probed before the
77 to deletion. Device links managed by the driver core are deleted automatically
86 Two other flags are specifically targeted at use cases where the device
104 ``DL_FLAG_STATELESS`` are invalid and cannot be used.
116 Moreover, managed device links cannot be deleted directly. They are deleted
117 by the driver core when they are not necessary any more in accordance with the
120 set) are expected to be removed by whoever called :c:func:`device_link_add()`
138 Sometimes drivers depend on optional resources. They are able to operate
[all …]
|
| /Linux-v5.10/Documentation/scsi/ |
| D | st.rst | 49 above. Additional modes are dormant until they are defined by the
58 parameters are reset when a new tape is loaded).
73 non-rewind devices (minor is 128 + device number) are implemented.
98 are caught at that point, but this takes time. In some applications, several
109 The compile options are defined in the file linux/drivers/scsi/st_options.h.
124 each drive are used.
132 byte). The bits defining the mode are below the non-rewind bit. The
142 directories corresponding to the existing tape devices. There are autorewind
143 and non-rewind entries for each mode. The names are stxy and nstxy, where x
145 a). For example, the directories for the first tape device are (assuming four
[all …]
|
| /Linux-v5.10/sound/firewire/dice/ |
| D | dice-interface.h | 12 * Writes are not allowed except where noted; quadlet-sized registers must be
15 * All values are in big endian. The DICE firmware runs on a little-endian CPU
21 * Streaming is handled by the "DICE driver" interface. Its registers are
27 * The registers are organized in several sections, which are organized
31 * The section offset values are relative to DICE_PRIVATE_SPACE; the offset/
32 * size values are measured in quadlets. Read-only.
61 * the bits of previous events are cleared, and the value of this register is
78 * bytes. Quadlets are byte-swapped. The encoding is whatever the host driver
88 * register can be changed even while streams are running.
216 * Names of all clock sources; read-only. Quadlets are byte-swapped. Names
[all …]
|
| /Linux-v5.10/Documentation/security/keys/ |
| D | trusted-encrypted.rst | 5 Trusted and Encrypted Keys are two new key types added to the existing kernel
6 key ring service. Both of these new types are variable length symmetric keys,
7 and in both cases all keys are created in the kernel, and user space sees,
10 Keys can be used on any system. All user level blobs, are displayed and loaded
11 in hex ascii for convenience, and are integrity verified.
13 Trusted Keys use a TPM both to generate and to seal the keys. Keys are sealed
17 (future) PCR values, so keys are easily migrated to new pcr values, such as
18 when the kernel and initramfs are updated. The same key can have many saved
19 blobs under different PCR values, so multiple boots are easily supported.
24 By default, trusted keys are sealed under the SRK, which has the default
[all …]
|
12345678910>>...430
