Searched +full:spin +full:- +full:table (Results 1 – 21 of 21) sorted by relevance
| /Documentation/devicetree/bindings/arm/ |
| D | cpus.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> 21 with updates for 32-bit and 64-bit ARM systems provided in this document. 30 - square brackets define bitfields, eg reg[7:0] value of the bitfield in 59 On 32-bit ARM v7 or later systems this property is 68 On ARM v8 64-bit systems this property is required 71 * If cpus node's #address-cells property is set to 2 79 * If cpus node's #address-cells property is set to 1 [all …]
|
| /Documentation/devicetree/bindings/cpu/ |
| D | cpu-topology.txt | 6 1 - Introduction 12 - socket 13 - cluster 14 - core 15 - thread 18 symmetric multi-threading (SMT) is supported or not. 29 Currently, only ARM/RISC-V intend to use this cpu topology binding but it may be 39 2 - cpu-map node 42 The ARM/RISC-V CPU topology is defined within the cpu-map node, which is a direct 46 - cpu-map node [all …]
|
| /Documentation/hwmon/ |
| D | lm93.rst | 10 Addresses scanned: I2C 0x2c-0x2e 18 Addresses scanned: I2C 0x2c-0x2e 24 - Mark M. Hoffman <mhoffman@lightlink.com> 25 - Ported to 2.6 by Eric J. Bowersox <ericb@aspsys.com> 26 - Adapted to 2.6.20 by Carsten Emde <ce@osadl.org> 27 - Modified for mainline integration by Hans J. Koch <hjk@hansjkoch.de> 30 ----------------- 33 Set to non-zero to force some initializations (default is 0). 38 Configures in7 and in8 limit type, where 0 means absolute and non-zero 54 -------------------- [all …]
|
| /Documentation/kernel-hacking/ |
| D | locking.rst | 35 .. table:: Expected Results 37 +------------------------------------+------------------------------------+ 41 +------------------------------------+------------------------------------+ 43 +------------------------------------+------------------------------------+ 45 +------------------------------------+------------------------------------+ 47 +------------------------------------+------------------------------------+ 49 +------------------------------------+------------------------------------+ 51 +------------------------------------+------------------------------------+ 55 .. table:: Possible Results 57 +------------------------------------+------------------------------------+ [all …]
|
| /Documentation/translations/zh_TW/arch/arm64/ |
| D | booting.txt | 1 SPDX-License-Identifier: GPL-2.0 15 --------------------------------------------------------------------- 30 --------------------------------------------------------------------- 40 AArch64 異常模型由多個異常級(EL0 - EL3)組成,對於 EL0 和 EL1 異常級 58 ----------------- 69 --------------- 81 ------------- 91 ------------- 111 - 自 v3.17 起,除非另有說明,所有域都是小端模式。 113 - code0/code1 負責跳轉到 stext. [all …]
|
| /Documentation/translations/zh_CN/arch/arm64/ |
| D | booting.txt | 12 --------------------------------------------------------------------- 26 --------------------------------------------------------------------- 36 AArch64 异常模型由多个异常级(EL0 - EL3)组成,对于 EL0 和 EL1 异常级 54 ----------------- 65 --------------- 77 ------------- 87 ------------- 107 - 自 v3.17 起,除非另有说明,所有域都是小端模式。 109 - code0/code1 负责跳转到 stext. 111 - 当通过 EFI 启动时, 最初 code0/code1 被跳过。 [all …]
|
| /Documentation/devicetree/bindings/iio/ |
| D | mount-matrix.txt | 2 * is the definition of +/- values practical or counterintuitive? 13 that produce three-dimensional data in relation to the world where it is 37 reference. This means that the sensor may be flipped upside-down, left-right, 47 Device-to-world examples for some three-dimensional sensor types: 49 - Accelerometers have their world frame of reference toward the center of 57 as the gravity vector is projected 1:1 onto the sensors (z)-axis. 67 +--------+ +--------+ 69 +--------+ +--------+ 80 (---------) 81 ! ! y: -g [all …]
|
| /Documentation/userspace-api/ioctl/ |
| D | cdrom.rst | 5 - Edward A. Falk <efalk@google.com> 10 the CDROM layer. These are by-and-large implemented (as of Linux 2.6) 33 CDROMEJECT_SW enable(1)/disable(0) auto-ejecting 34 CDROMMULTISESSION Obtain the start-of-last-session 40 CDROMRESET hard-reset the drive 47 CDROMPLAYBLK scsi-cd only, (struct cdrom_blk) 49 CDROMGETSPINDOWN return 4-bit spindown value 50 CDROMSETSPINDOWN set 4-bit spindown value 54 CDROM_SELECT_SPEED Set the CD-ROM speed 55 CDROM_SELECT_DISC Select disc (for juke-boxes) [all …]
|
| /Documentation/driver-api/nvdimm/ |
| D | btt.rst | 2 BTT - Block Translation Table 14 using stored energy in capacitors to complete in-flight block writes, or perhaps 15 in firmware. We don't have this luxury with persistent memory - if a write is in 19 The Block Translation Table (BTT) provides atomic sector update semantics for 23 the heart of it, is an indirection table that re-maps all the blocks on the 37 next arena). The following depicts the "On-disk" metadata layout:: 40 Backing Store +-------> Arena 41 +---------------+ | +------------------+ 43 | Arena 0 +---+ | 4K | 44 | 512G | +------------------+ [all …]
|
| /Documentation/arch/arm64/ |
| D | booting.rst | 13 (EL0 - EL3), with EL0, EL1 and EL2 having a secure and a non-secure 33 --------------------------- 46 ------------------------- 50 The device tree blob (dtb) must be placed on an 8-byte boundary and must 59 ------------------------------ 71 ------------------------ 75 The decompressed kernel image contains a 64-byte header as follows:: 91 - As of v3.17, all fields are little endian unless stated otherwise. 93 - code0/code1 are responsible for branching to stext. 95 - when booting through EFI, code0/code1 are initially skipped. [all …]
|
| /Documentation/firmware-guide/acpi/apei/ |
| D | einj.rst | 1 .. SPDX-License-Identifier: GPL-2.0 15 which shows that the BIOS is exposing an EINJ table - it is the 43 - available_error_type 51 0x00000002 Processor Uncorrectable non-fatal 54 0x00000010 Memory Uncorrectable non-fatal 57 0x00000080 PCI Express Uncorrectable non-fatal 60 0x00000400 Platform Uncorrectable non-fatal 67 - error_type 72 - error_inject 78 - flags [all …]
|
| /Documentation/RCU/ |
| D | RTFP.txt | 4 This document describes RCU-related publications, and is followed by 19 with short-lived threads, such as the K42 research operating system. 20 However, Linux has long-lived tasks, so more is needed. 23 serialization, which is an RCU-like mechanism that relies on the presence 27 that these overheads were not so expensive in the mid-80s. Nonetheless, 28 passive serialization appears to be the first deferred-destruction 30 has lapsed, so this approach may be used in non-GPL software, if desired. 34 In 1987, Rashid et al. described lazy TLB-flush [RichardRashid87a]. 36 this paper helped inspire the update-side batching used in the later 38 a description of Argus that noted that use of out-of-date values can [all …]
|
| /Documentation/filesystems/ |
| D | locking.rst | 5 The text below describes the locking rules for VFS-related methods. 6 It is (believed to be) up-to-date. *Please*, if you change anything in 7 prototypes or locking protocols - update this file. And update the relevant 10 Don't turn it into log - maintainers of out-of-the-tree code are supposed to 37 ops rename_lock ->d_lock may block rcu-walk 39 d_revalidate: no no yes (ref-walk) maybe 50 d_manage: no no yes (ref-walk) maybe 108 permission: no (may not block if called in rcu-walk mode) 123 Additionally, ->rmdir(), ->unlink() and ->rename() have ->i_rwsem 125 cross-directory ->rename() has (per-superblock) ->s_vfs_rename_sem. [all …]
|
| D | vfs.rst | 1 .. SPDX-License-Identifier: GPL-2.0 9 - Copyright (C) 1999 Richard Gooch 10 - Copyright (C) 2005 Pekka Enberg 27 ------------------------------ 32 cache or dcache). This provides a very fast look-up mechanism to 44 ---------------- 64 --------------- 67 structure (this is the kernel-side implementation of file descriptors). 73 placed into the file descriptor table for the process. 88 .. code-block:: c [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/device-mapper/ |
| D | vdo-design.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only 4 Design of dm-vdo 7 The dm-vdo (virtual data optimizer) target provides inline deduplication, 8 compression, zero-block elimination, and thin provisioning. A dm-vdo target 12 production environments ever since. It was made open-source in 2017 after 14 dm-vdo. For usage, see vdo.rst in the same directory as this file. 25 The design of dm-vdo is based on the idea that deduplication is a two-part 27 storing multiple copies of those duplicates. Therefore, dm-vdo has two main 34 ------------------- 41 design attempts to be lock-free. [all …]
|
| /Documentation/sound/kernel-api/ |
| D | writing-an-alsa-driver.rst | 11 Architecture) <http://www.alsa-project.org/>`__ driver. The document 19 low-level driver implementation details. It only describes the standard 26 ------- 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 94 ----------------- [all …]
|
| /Documentation/admin-guide/laptops/ |
| D | thinkpad-acpi.rst | 9 - Borislav Deianov <borislav@users.sf.net> 10 - Henrique de Moraes Holschuh <hmh@hmh.eng.br> 12 http://ibm-acpi.sf.net/ 19 This driver used to be named ibm-acpi until kernel 2.6.21 and release 20 0.13-20070314. It used to be in the drivers/acpi tree, but it was 21 moved to the drivers/misc tree and renamed to thinkpad-acpi for kernel 25 The driver is named "thinkpad-acpi". In some places, like module 29 "tpacpi" is used as a shorthand where "thinkpad-acpi" would be too 33 ------ 38 - Fn key combinations [all …]
|
| /Documentation/cdrom/ |
| D | cdrom-standard.rst | 2 A Linux CD-ROM standard 14 Linux is probably the Unix-like operating system that supports 18 - The large list of hardware devices available for the many platforms 19 that Linux now supports (i.e., i386-PCs, Sparc Suns, etc.) 20 - The open design of the operating system, such that anybody can write a 22 - There is plenty of source code around as examples of how to write a driver. 29 This divergence of behavior has been very significant for CD-ROM 32 their drivers totally inconsistent, the writers of Linux CD-ROM 35 maintain uniform behavior across all the Linux CD-ROM drivers. 38 all the different CD-ROM device drivers for Linux. This document also [all …]
|
| /Documentation/scsi/ |
| D | ncr53c8xx.rst | 1 .. SPDX-License-Identifier: GPL-2.0 11 95170 DEUIL LA BARRE - FRANCE 64 10.4 PCI configuration fix-up boot option 81 16.1 Synchronous timings for 53C875 and 53C860 Ultra-SCSI controllers 82 16.2 Synchronous timings for fast SCSI-2 53C8XX controllers 97 - Gerard Roudier <groudier@free.fr> 101 - Wolfgang Stanglmeier <wolf@cologne.de> 102 - Stefan Esser <se@mi.Uni-Koeln.de> 106 - ncr53c8xx generic driver that supports all the SYM53C8XX family including 109 - sym53c8xx enhanced driver (a.k.a. 896 drivers) that drops support of oldest [all …]
|
| /Documentation/RCU/Design/Requirements/ |
| D | Requirements.rst | 16 ------------ 18 Read-copy update (RCU) is a synchronization mechanism that is often used 19 as a replacement for reader-writer locking. RCU is unusual in that 20 updaters do not block readers, which means that RCU's read-side 28 thought of as an informal, high-level specification for RCU. It is 40 #. `Fundamental Non-Requirements`_ 42 #. `Quality-of-Implementation Requirements`_ 44 #. `Software-Engineering Requirements`_ 53 ------------------------ 58 #. `Grace-Period Guarantee`_ [all …]
|