Home
last modified time | relevance | path

Searched +full:spin +full:- +full:table (Results 1 – 20 of 20) sorted by relevance

/Documentation/devicetree/bindings/arm/
Dcpus.yaml1 # 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/
Dcpu-topology.txt6 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/
Dlm93.rst10 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/
Dlocking.rst35 .. table:: Expected Results
37 +------------------------------------+------------------------------------+
41 +------------------------------------+------------------------------------+
43 +------------------------------------+------------------------------------+
45 +------------------------------------+------------------------------------+
47 +------------------------------------+------------------------------------+
49 +------------------------------------+------------------------------------+
51 +------------------------------------+------------------------------------+
55 .. table:: Possible Results
57 +------------------------------------+------------------------------------+
[all …]
/Documentation/translations/zh_CN/arm64/
Dbooting.txt12 ---------------------------------------------------------------------
26 ---------------------------------------------------------------------
36 AArch64 异常模型由多个异常级（EL0 - EL3）组成，对于 EL0 和 EL1 异常级
54 -----------------
65 ---------------
77 -------------
87 -------------
107 - 自 v3.17 起，除非另有说明，所有域都是小端模式。
109 - code0/code1 负责跳转到 stext.
111 - 当通过 EFI 启动时， 最初 code0/code1 被跳过。
[all …]
/Documentation/arm64/
Dbooting.rst13 (EL0 - EL3), with EL0 and EL1 having a secure and a non-secure
14 counterpart. EL2 is the hypervisor level and exists only in 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.
[all …]
/Documentation/networking/
Dz8530book.rst113 netdevice field of each channel. The hdlc-> priv field of the network
114 device points to your private data - you will need to be able to find
143 table is for the UK 'Kilostream' service and also happens to cover most
144 other end host configurations. The z8530_hdlc_kilostream_85230 table
151 sure to set registers 1-7, 9-11, 14 and 15 in all configurations. Where
153 bits itself when you open or close. Loading a new table with the
239 per device spin lock would probably materially improve performance.
249 .. kernel-doc:: drivers/net/wan/z85230.c
255 .. kernel-doc:: drivers/net/wan/z85230.c
/Documentation/devicetree/bindings/iio/
Dmount-matrix.txt2 * 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/ioctl/
Dcdrom.rst5 - 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/
Dbtt.rst2 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/RCU/Design/Requirements/
DRequirements.html1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
5 <meta HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
20 Read-copy update (RCU) is a synchronization mechanism that is often
21 used as a replacement for reader-writer locking.
23 which means that RCU's read-side primitives can be exceedingly fast
33 of as an informal, high-level specification for RCU.
49 <li> <a href="#Fundamental Non-Requirements">Fundamental Non-Requirements</a>
52 <li> <a href="#Quality-of-Implementation Requirements">
53 Quality-of-Implementation Requirements</a>
56 <li> <a href="#Software-Engineering Requirements">
[all …]
/Documentation/filesystems/
Dxfs-delayed-logging-design.txt2 --------------------------
4 Introduction to Re-logging in XFS
5 ---------------------------------
9 logged are made up of the changes to in-core structures rather than on-disk
10 structures. Other objects - typically buffers - have their physical changes
21 "re-logging". Conceptually, this is quite simple - all it requires is that any
44 moving forward. This can be seen in the table above by the changing
45 (increasing) LSN of each subsequent transaction - the LSN is effectively a
48 This relogging is also used to implement long-running, multiple-commit
62 the log - repeated operations to the same objects write the same changes to
[all …]
Dvfs.rst1 .. 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/RCU/
DRTFP.txt4 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/process/
Dkernel-docs.rst6 Juan-Mariano de Goyeneche <jmseyas@dit.upm.es>
9 linux-kernel mailing list as the same questions, asking for pointers
18 start. And, even if they exist, there was no "well-known" place which
24 send me an e-mail, and I'll include a reference to it here. Any
41 -----------------------------
55 On-line docs
56 ------------
63 :Keywords: glossary, terms, linux-kernel.
79 Having obtained a trace-log a kernel hacker can read and understand
83 Finally this trace-log is used as base for more a exact conceptual
[all …]
/Documentation/admin-guide/laptops/
Dthinkpad-acpi.rst9 - 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/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
29 -------
61 --------------
65 sub-directories contain different modules and are dependent upon the
74 ``core/seq/oss`` directory (see `below <#core-seq-oss>`__).
79 This directory and its sub-directories are for the ALSA sequencer. This
81 like snd-seq-midi, snd-seq-virmidi, etc. They are compiled only when
90 -----------------
93 to be exported to user-space, or included by several files at different
[all …]
/Documentation/cdrom/
Dcdrom-standard.rst2 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/
Dncr53c8xx.txt5 95170 DEUIL LA BARRE - FRANCE
57 10.4 PCI configuration fix-up boot option
74 16.1 Synchronous timings for 53C875 and 53C860 Ultra-SCSI controllers
75 16.2 Synchronous timings for fast SCSI-2 53C8XX controllers
94 Stefan Esser <se@mi.Uni-Koeln.de>
98 - ncr53c8xx generic driver that supports all the SYM53C8XX family including
101 - sym53c8xx enhanced driver (a.k.a. 896 drivers) that drops support of oldest
107 PCI-HOWTO written by Michael Will and in the SCSI-HOWTO written by
118 Useful SCSI tools written by Eric Youngdale are available at tsx-11:
120 ftp://tsx-11.mit.edu/pub/linux/ALPHA/scsi/scsiinfo-X.Y.tar.gz
[all …]
/Documentation/devicetree/
Dbooting-without-of.txt2 --------------------------------------------------
7 Freescale Semiconductor, FSL SOC and 32-bit additions
11 Table of Contents
14 I - Introduction
21 II - The DT block format
27 III - Required content of the device tree
40 IV - "dtc", the device tree compiler
42 V - Recommendations for a bootloader
44 VI - System-on-a-chip devices and nodes
48 VII - Specifying interrupt information for devices
[all …]