Home
last modified time | relevance | path

Searched +full:tech +full:- +full:docs (Results 1 – 8 of 8) sorted by relevance

/Documentation/devicetree/bindings/leds/
Dawinic,aw200xx.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Martin Kurbanov <mmkurbanov@sberdevices.ru>
16 - AW20036 (3x12) 36 LEDs
17 - AW20054 (6x9) 54 LEDs
18 - AW20072 (6x12) 72 LEDs
19 - AW20108 (9x12) 108 LEDs
22 aw20036 - https://www.awinic.com/en/productDetail/AW20036QNR#tech-docs
23 aw20054 - https://www.awinic.com/en/productDetail/AW20054QNR#tech-docs
[all …]
/Documentation/devicetree/bindings/hwmon/
Damd,sbrmi.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 Sideband Remote Management Interface (SB-RMI) compliant
12 - Akshay Gupta <Akshay.Gupta@amd.com>
15 SB Remote Management Interface (SB-RMI) is an SMBus compatible
17 Mailbox Service Request and resembles a typical 8-pin remote power
24 - amd,sbrmi
30 of the SoC register reference. The SB-RMI address is normally 78h for
34 https://www.amd.com/en/support/tech-docs?keyword=55898
[all …]
/Documentation/hwmon/
Dsbrmi.rst1 .. SPDX-License-Identifier: GPL-2.0-or-later
8 * Sideband Remote Management Interface (SB-RMI) compliant AMD SoC
15 To instantiate this driver on an AMD CPU with SB-RMI
22 As mentioned in AMD's APML specification, The SB-RMI address is
27 Datasheet: The SB-RMI interface and protocol along with the Advanced
31 https://www.amd.com/en/support/tech-docs?keyword=55898
36 -----------
39 (SB-RMI) module from the external SMBus master that can be used to report socket
40 power on AMD platforms using mailbox command and resembles a typical 8-pin remote
45 sysfs-Interface
[all …]
/Documentation/arch/x86/
Diommu.rst7 - Intel: http://www.intel.com/content/dam/www/public/us/en/documents/product-specifications/vt-dire…
8 - AMD: https://www.amd.com/content/dam/amd/en/documents/processor-tech-docs/specifications/48882_3_…
13 -----------
21 - DMAR - Intel DMA Remapping table
22 - DRHD - Intel DMA Remapping Hardware Unit Definition
23 - RMRR - Intel Reserved Memory Region Reporting Structure
24 - IVRS - AMD I/O Virtualization Reporting Structure
25 - IVDB - AMD I/O Virtualization Definition Block
26 - IVHD - AMD I/O Virtualization Hardware Definition
41 The architecture defines an ACPI-compatible data structure called an I/O
[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/ABI/testing/
Dsysfs-devices-system-cpu2 Date: pre-git history
3 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
18 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
37 See Documentation/admin-guide/cputopology.rst for more information.
43 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
58 Contact: Linux memory management mailing list <linux-mm@kvack.org>
67 /sys/devices/system/cpu/cpu42/node2 -> ../../node/node2
77 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
89 core_siblings_list: human-readable list of the logical CPU
99 thread_siblings_list: human-readable list of cpuX's hardware
[all …]
/Documentation/admin-guide/RAS/
Dmain.rst1 .. SPDX-License-Identifier: GPL-2.0
37 -------------
51 Self-Monitoring, Analysis and Reporting Technology (SMART).
59 ---------------
72 * **Correctable Error (CE)** - the error detection mechanism detected and
76 * **Uncorrected Error (UE)** - the amount of errors happened above the error
77 correction threshold, and the system was unable to auto-correct.
79 * **Fatal Error** - when an UE error happens on a critical component of the
83 * **Non-fatal Error** - when an UE error happens on an unused component,
91 The mechanism for handling non-fatal errors is usually complex and may
[all …]
/Documentation/networking/
Darcnet-hardware.rst1 .. SPDX-License-Identifier: GPL-2.0
11 2) This file is no longer Linux-specific. It should probably be moved out
17 e-mail apenwarr@worldvisions.ca with any settings for your particular card,
39 There are two "types" of ARCnet - STAR topology and BUS topology. This
46 well-designed standard. It uses something called "modified token passing"
47 which makes it completely incompatible with so-called "Token Ring" cards,
63 programming interface also means that when high-performance hardware
73 although they are generally kept down to the Ethernet-style 1500 bytes.
91 - Avery Pennraun <apenwarr@worldvisions.ca>
92 - Stephen A. Wood <saw@hallc1.cebaf.gov>
[all …]