Home
last modified time | relevance | path

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

/linux-6.15/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 …]
/linux-6.15/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 …]
/linux-6.15/Documentation/admin-guide/hw-vuln/
Drsb.rst1 .. SPDX-License-Identifier: GPL-2.0
4 RSB-related mitigations
8 Please keep this document up-to-date, otherwise you will be
17 amongst a myriad of microarchitecture-specific documents.
20 once place and clarify the reasoning behind the current RSB-related
22 the current kernel mitigations: what are the RSB-related attack vectors
39 ----
47 RSB poisoning is a technique used by SpectreRSB [#spectre-rsb]_ where
49 to speculate to an attacker-controlled address. This can happen when
54 [#intel-rsb-filling]_ [#amd-rsb-filling]_ when transitioning between
[all …]
/linux-6.15/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 …]
/linux-6.15/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 …]
/linux-6.15/drivers/ata/
Dpata_it8213.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * pata_it8213.c - iTE Tech. Inc. IT8213 PATA driver
25 * it8213_pre_reset - probe begin
38 struct ata_port *ap = link->ap; in it8213_pre_reset()
39 struct pci_dev *pdev = to_pci_dev(ap->host->dev); in it8213_pre_reset()
40 if (!pci_test_config_bits(pdev, &it8213_enable_bits[ap->port_no])) in it8213_pre_reset()
41 return -ENOENT; in it8213_pre_reset()
47 * it8213_cable_detect - check for 40/80 pin
56 struct pci_dev *pdev = to_pci_dev(ap->host->dev); in it8213_cable_detect()
59 if (tmp & 2) /* The initial docs are incorrect */ in it8213_cable_detect()
[all …]
/linux-6.15/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 …]
/linux-6.15/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 …]
/linux-6.15/drivers/hid/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
22 most commonly used to refer to the USB-HID specification, but other
27 removed from the HID bus by the transport-layer drivers, such as
30 For docs and specs, see https://www.usb.org/developers/hidpage/
58 to work on raw hid events when they want to, and avoid using transport-specific
64 tristate "User-space I/O driver support for HID subsystem"
67 Say Y here if you want to provide HID I/O Drivers from user-space.
68 This allows to write I/O drivers in user-space and feed the data from
71 user-space device.
73 This driver cannot be used to parse HID-reports in user-space and write
[all …]
/linux-6.15/drivers/usb/serial/
Dftdi_sio_ids.h1 /* SPDX-License-Identifier: GPL-2.0 */
6 * Philipp Gühring - pg@futureware.at - added the Device ID of the USB relais
25 #define FTDI_4232H_PID 0x6011 /* Quad channel hi-speed device */
26 #define FTDI_232H_PID 0x6014 /* Single channel hi-speed device */
27 #define FTDI_FTX_PID 0x6015 /* FT-X series (FT201X, FT230X, FT231X, etc) */
28 #define FTDI_FT2233HP_PID 0x6040 /* Dual channel hi-speed device with PD */
29 #define FTDI_FT4233HP_PID 0x6041 /* Quad channel hi-speed device with PD */
30 #define FTDI_FT2232HP_PID 0x6042 /* Dual channel hi-speed device with PD */
31 #define FTDI_FT4232HP_PID 0x6043 /* Quad channel hi-speed device with PD */
32 #define FTDI_FT233HP_PID 0x6044 /* Dual channel hi-speed device with PD */
[all …]
/linux-6.15/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 …]
/linux-6.15/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 …]
/linux-6.15/
DCREDITS1 This is at least a partial credits-file of people that have
4 scripts. The fields are: name (N), email (E), web-address
6 snail-mail address (S).
10 ----------
51 D: in-kernel DRM Maintainer
76 E: tim_alpaerts@toyota-motor-europe.com
80 S: B-2610 Wilrijk-Antwerpen
85 W: http://www-stu.christs.cam.ac.uk/~aia21/
106 D: Maintainer of ide-cd and Uniform CD-ROM driver,
107 D: ATAPI CD-Changer support, Major 2.1.x CD-ROM update.
[all …]
DMAINTAINERS5 ---------------------------------------------------
21 W: *Web-page* with status/info
23 B: URI for where to file *bugs*. A web-page with detailed bug
28 patches to the given subsystem. This is either an in-tree file,
29 or a URI. See Documentation/maintainer/maintainer-entry-profile.rst
46 N: [^a-z]tegra all files whose path contains tegra
64 ----------------
83 3WARE SAS/SATA-RAID SCSI DRIVERS (3W-XXXX, 3W-9XXX, 3W-SAS)
85 L: linux-scsi@vger.kernel.org
88 F: drivers/scsi/3w-*
[all …]
/linux-6.15/drivers/net/ethernet/sfc/
Dmcdi_pcol.h1 /* SPDX-License-Identifier: GPL-2.0-only */
4 * Copyright 2009-2018 Solarflare Communications Inc.
5 * Copyright 2019-2020 Xilinx Inc.
13 /* Power-on reset state */
35 /* The 'doorbell' addresses are hard-wired to alert the MC when written */
38 /* The rest of these are firmware-defined */
46 /* Values to be written to the per-port status dword in shared
71 * | | \--- Response
72 * | \------- Error
73 * \------------------------------ Resync (always set)
[all …]