| /Documentation/driver-api/acpi/ |
| D | scan_handlers.rst | 1 .. SPDX-License-Identifier: GPL-2.0
5 ACPI Scan Handlers
12 During system initialization and ACPI-based device hot-add, the ACPI namespace
15 registered with the driver core for every device object in the ACPI namespace
23 During ACPI-based device hot-remove device nodes representing pieces of hardware
26 The core ACPI namespace scanning code in drivers/acpi/scan.c carries out basic
39 called ACPI scan handlers represented by the following structure::
49 take care of, list_node is the hook to the global list of ACPI scan handlers
50 maintained by the ACPI core and the .attach() and .detach() callbacks are
76 ACPI scan handlers can be added to the list maintained by the ACPI core with the
|
| /Documentation/firmware-guide/acpi/ |
| D | debug.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 ACPI CA Debug Output
7 The ACPI CA can generate debug output. This document describes how to use this
10 Compile-time configuration
13 The ACPI CA debug output is globally enabled by CONFIG_ACPI_DEBUG. If this
16 Boot- and run-time configuration
20 you're interested in. At boot-time, use the acpi.debug_layer and
21 acpi.debug_level kernel command line options. After boot, you can use the
22 debug_layer and debug_level files in /sys/module/acpi/parameters/ to control
29 specific part of the ACPI interpreter. To build the debug_layer bitmask, look
[all …]
|
| D | enumeration.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 ACPI Based Device Enumeration
7 ACPI 5 introduced a set of new resources (UartTSerialBus, I2cSerialBus,
12 SoC/Chipset to appear only in ACPI namespace. These are typically devices
13 that are accessed through memory-mapped registers.
15 In order to support this and re-use the existing drivers as much as
18 - Devices that have no bus connector resource are represented as
21 - Devices behind real busses where there is a connector resource
26 As both ACPI and Device Tree represent a tree of devices (and their
30 The ACPI implementation enumerates devices behind busses (platform, SPI,
[all …]
|
| D | osi.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 ACPI _OSI and _REV methods
7 An ACPI BIOS can use the "Operating System Interfaces" method (_OSI)
13 The ACPI _REV method returns the "Revision of the ACPI specification
22 Linux runs on two groups of machines -- those that are tested by the OEM
51 _OSI("Linux-OEM-my_interface_name")
52 where 'OEM' is needed if this is an OEM-specific hook,
54 quirk, a bug, or a bug-fix.
60 any custom Linux-* strings by default.
67 ACPI 1.0 specified "_OS" as an
[all …]
|
| /Documentation/admin-guide/pm/ |
| D | sleep-states.rst | 1 .. SPDX-License-Identifier: GPL-2.0
13 Sleep states are global low-power states of the entire system in which user
28 Suspend-to-Idle
29 ---------------
31 This is a generic, pure software, light-weight variant of system suspend (also
34 I/O devices into low-power states (possibly lower-power than available in the
38 The system is woken up from this state by in-band interrupts, so theoretically
43 or :ref:`suspend-to-RAM <s2ram>`, or it can be used in addition to any of the
50 -------
58 I/O devices into low-power states, which is done for :ref:`suspend-to-idle
[all …]
|
| /Documentation/wmi/ |
| D | driver-development-guide.rst | 1 .. SPDX-License-Identifier: GPL-2.0-or-later
8 documented at Documentation/driver-api/wmi.rst. This document will serve
11 using the deprecated GUID-based WMI interface.
14 --------------------------------
22 lswmi -V
30 The ``wmi-bmof`` driver exposes this information to userspace, see
31 Documentation/wmi/devices/wmi-bmof.rst.
37 ./bmf2mof /sys/bus/wmi/devices/05901221-D566-11D1-B2F0-00A0C9062910[-X]/bmof
39 Sometimes, looking at the disassembled ACPI tables used to describe the WMI device
40 helps in understanding how the WMI device is supposed to work. The path of the ACPI
[all …]
|
| /Documentation/admin-guide/acpi/ |
| D | ssdt-overlays.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 In order to support ACPI open-ended hardware configurations (e.g. development
8 boards) we need a way to augment the ACPI configuration provided by the firmware
13 recompiling the firmware image with updated ACPI tables, neither is practical:
17 Because ACPI supports external references in AML code a more practical
18 way to augment firmware ACPI configuration is by dynamically loading
58 Intel ACPI Component Architecture
59 ASL Optimizing Compiler version 20140214-64 [Mar 29 2014]
60 Copyright (c) 2000 - 2014 Intel Corporation
62 ASL Input: minnomax.asl - 30 lines, 614 bytes, 7 keywords
[all …]
|
| /Documentation/driver-api/media/ |
| D | camera-sensor.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 This document covers the in-kernel APIs only. For the best practices on
12 CSI-2, parallel and BT.656 buses
13 --------------------------------
15 Please see :ref:`transmitter-receiver`.
18 ---------------
21 divisors. The clock tree is generally configured by the driver based on a few
29 elsewhere. Therefore only the pre-determined frequencies are configurable by the
32 ACPI section in Handling clocks
35 Read the ``clock-frequency`` _DSD property to denote the frequency. The driver
[all …]
|
| /Documentation/admin-guide/laptops/ |
| D | thinkpad-acpi.rst | 2 ThinkPad ACPI Extras Driver
9 - Borislav Deianov <borislav@users.sf.net>
10 - Henrique de Moraes Holschuh <hmh@hmh.eng.br>
12 http://ibm-acpi.sf.net/
16 through the ACPI and ACPI EC framework, but not otherwise fully
17 supported by the generic Linux ACPI drivers.
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
[all …]
|
| D | sony-laptop.rst | 5 - Copyright (C) 2004- 2005 Stelian Pop <stelian@popies.net>
6 - Copyright (C) 2007 Mattia Dongili <malattia@linux.it>
8 This mini-driver drives the SNC and SPIC device present in the ACPI BIOS of the
11 obsoleted by sony-laptop now.
14 ------------------
17 reported both through the ACPI subsystem as acpi events and through the INPUT
24 are indexes to the table "sony_laptop_input_keycode_map" in the sony-laptop.c
29 ------------------
45 ------------------
46 Loading the sony-laptop module will create a
[all …]
|
| /Documentation/wmi/devices/ |
| D | dell-wmi-ddv.rst | 1 .. SPDX-License-Identifier: GPL-2.0-or-later
4 Dell DDV WMI interface driver (dell-wmi-ddv)
10 Many Dell notebooks made after ~2020 support a WMI-based interface for
15 so it was called `DDV`. Currently the ``dell-wmi-ddv`` driver supports
21 trial-and-error, please keep that in mind.
27 including batteries. It has a form similar to `CC-PPPPPP-MMMMM-YMD-SSSS-FFF`
52 …), Locale("MS\\0x409"), Description("WMI Function"), guid("{8A42EA14-4F2A-FD45-6422-0087F7A7E608}"…
67 …[WmiMethodId(11), Implemented, read, write, Description("Return Battery Relative State-Of-Charge."…
79 Each WMI method takes an ACPI buffer containing a 32-bit index as input argument,
80 with the first 8 bit being used to specify the battery when using battery-related
[all …]
|
| /Documentation/arch/x86/x86_64/ |
| D | boot-options.rst | 1 .. SPDX-License-Identifier: GPL-2.0
39 Do not opt-in to Local MCE delivery. Use legacy method
55 Don't overwrite the bios-set CMCI threshold. This boot option
62 Force-enable recoverable machine check code paths
73 Use IO-APIC. Default
76 Don't use the IO-APIC.
85 See Documentation/arch/x86/i386/IO-APIC.rst
91 Don't check the IO-APIC timer. This can work around
133 acpi
134 Use the ACPI RESET_REG in the FADT. If ACPI is not configured or
[all …]
|
| /Documentation/nvdimm/ |
| D | maintainer-entry-profile.rst | 5 --------
8 https://patchwork.kernel.org/project/linux-nvdimm/list/
11 'libnvdimm-fixes' or 'libnvdimm-for-next' branch. Those branches are
15 In general patches can be submitted against the latest -rc; however, if
17 patch should be based on the libnvdimm-for-next branch. However, since
29 -------------------------
36 ACPI Device Specific Methods (_DSM)
39 be assigned a format-interface-code from the NVDIMM Sub-team of the ACPI
43 drivers/acpi/nfit/nfit.h for the set of supported command sets.
47 ---------------
[all …]
|
| /Documentation/firmware-guide/acpi/apei/ |
| D | einj.rst | 1 .. SPDX-License-Identifier: GPL-2.0
13 ACPI: EINJ 0x000000007370A000 000150 (v01 INTEL 00000001 INTL 00000001)
15 which shows that the BIOS is exposing an EINJ table - it is the
18 Alternatively, look in /sys/firmware/acpi/tables for an "EINJ" file,
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
[all …]
|
| /Documentation/i2c/busses/ |
| D | i2c-i801.rst | 2 Kernel driver i2c-i801
7 * Intel 82801AA and 82801AB (ICH and ICH0 - part of the
9 * Intel 82801BA (ICH2 - part of the '815E' chipset)
60 - Mark Studebaker <mdsxyz123@yahoo.com>
61 - Jean Delvare <jdelvare@suse.de>
65 -----------------
83 -----------
87 Intel's '810' chipset for Celeron-based PCs, '810E' chipset for
88 Pentium-based PCs, '815E' chipset, and others.
108 --------------------
[all …]
|
| /Documentation/arch/arm64/ |
| D | arm-acpi.rst | 2 ACPI on Arm systems
5 ACPI can be used for Armv8 and Armv9 systems designed to follow
12 The Arm kernel implements the reduced hardware model of ACPI version
16 by the specification can be found via http://www.uefi.org/acpi.
19 or cannot be described using the mechanisms defined in the required ACPI
20 specifications, then ACPI may not be a good fit for the hardware.
23 industry-standard Arm systems, they also apply to more than one operating
25 ACPI and Linux only, on an Arm system -- that is, what Linux expects of
26 ACPI and what ACPI can expect of Linux.
29 Why ACPI on Arm?
[all …]
|
| D | acpi_object_usage.rst | 2 ACPI Tables
5 The expectations of individual ACPI tables are discussed in the list that
8 If a section number is used, it refers to a section number in the ACPI
14 For ACPI on arm64, tables also fall into the following categories:
16 - Required: DSDT, FADT, GTDT, MADT, MCFG, RSDP, SPCR, XSDT
18 - Recommended: BERT, EINJ, ERST, HEST, PCCT, SSDT
20 - Optional: AGDI, BGRT, CEDT, CPEP, CSRT, DBG2, DRTM, ECDT, FACS, FPDT,
24 - Not supported: AEST, APMT, BOOT, DBGP, DMAR, ETDT, HPET, IVRS, LPIT,
41 This table describes a non-maskable event, that is used by the platform
68 Optional, not currently supported, with no real use-case for an
[all …]
|
| /Documentation/core-api/ |
| D | printk-index.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 There are monitoring tools that filter and take action based on messages
19 Finding these changes in the sources would require non-trivial parsers.
36 named according to the binaries where the printk formats are built-in. There
44 might appear in "vmlinux" when the module is built-in.
48 $> head -1 /sys/kernel/debug/printk/index/vmlinux; shuf -n 5 vmlinux
50 <5> block/blk-settings.c:661 disk_stack_limits "%s: Warning: Device %s is misaligned\n"
54 <6> drivers/acpi/osl.c:1410 acpi_no_auto_serialize_setup "ACPI: auto-serialization disabled\n"
58 - :level: log level value: 0-7 for particular severity, -1 as default,
60 - :flags: optional flags: currently only 'c' for KERN_CONT
[all …]
|
| /Documentation/power/ |
| D | pci.rst | 8 management. Based on previous work by Patrick Mochel <mochel@transmeta.com>
13 power management refer to Documentation/driver-api/pm/devices.rst and
27 1.1. Native and Platform-Based Power Management
28 -----------------------------------------------
31 devices into states in which they draw less power (low-power states) at the
34 Usually, a device is put into a low-power state when it is underutilized or
36 again, it has to be put back into the "fully functional" state (full-power
41 PCI devices may be put into low-power states in two ways, by using the device
43 or with the help of platform firmware, such as an ACPI BIOS. In the first
53 to put the device that sent it into the full-power state. However, the PCI Bus
[all …]
|
| /Documentation/devicetree/bindings/ |
| D | incomplete-devices.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/incomplete-devices.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Rob Herring <robh@kernel.org>
16 Examples are devices using ACPI PRP0001 with non-updatable firmware/ACPI
17 tables or old PowerPC platforms without in-tree DTS.
21 un-approved compatible.
29 - description:
30 Rejected compatibles in Devicetree, but used in ACPI-based devices
[all …]
|
| /Documentation/driver-api/thermal/ |
| D | intel_dptf.rst | 1 .. SPDX-License-Identifier: GPL-2.0
12 ------------
23 ACPI and PCI devices to expose various features for monitoring and
30 DPTF ACPI Drivers interface
31 ----------------------------
43 "42A441D6-AE6A-462b-A84B-4A8CE79027D3" : Passive 1
45 "3A95C389-E4B8-4629-A526-C52C88626BAE" : Active
47 "97C68AE7-15FA-499c-B8C9-5DA81D606E0A" : Critical
49 "63BE270F-1C11-48FD-A6F7-3AF253FF3E2D" : Adaptive performance
51 "5349962F-71E6-431D-9AE8-0A635B710AEE" : Emergency call
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-thermal | 5 E.g: "acpitz" indicates it's an ACPI thermal device.
25 kernel based algorithm or user space application.
61 E.g. it can be one of critical, hot, passive, `active[0-*]`
62 for ACPI thermal zone.
84 The trip point in this thermal zone which `cdev[0-*]` is
85 associated with; -1 means the cooling device is not
92 The influence of `cdev[0-*]` in this thermal zone. This value
124 Documentation/driver-api/thermal/power_allocator.rst
133 Documentation/driver-api/thermal/power_allocator.rst
143 Documentation/driver-api/thermal/power_allocator.rst
[all …]
|
| /Documentation/scsi/ |
| D | ufs.rst | 1 .. SPDX-License-Identifier: GPL-2.0
29 embedded and removable flash memory-based storage in mobile
31 is defined by JEDEC Solid State Technology Association. UFS is based
32 on the MIPI M-PHY physical layer standard. UFS uses MIPI M-PHY as the
41 - Support for Gear1 is mandatory (rate A: 1248Mbps, rate B: 1457.6Mbps)
42 - Support for Gear2 is optional (rate A: 2496Mbps, rate B: 2915.2Mbps)
46 - Gear3 (rate A: 4992Mbps, rate B: 5830.4Mbps)
55 UFS has a layered communication architecture which is based on SCSI
56 SAM-5 architectural model.
61 ---------------------
[all …]
|
| /Documentation/driver-api/soundwire/ |
| D | summary.rst | 10 SoundWire is a 2-pin multi-drop interface with data and clock line. It
15 commands over a single two-pin interface.
23 (4) Device status monitoring, including interrupt-style alerts to the Master.
38 +---------------+ +---------------+
40 | Master |-------+-------------------------------| Slave |
42 | |-------|-------+-----------------------| |
43 +---------------+ | | +---------------+
47 +--+-------+--+
52 +-------------+
64 3rd-party vendors to enable implementation-defined functionality while
[all …]
|
| /Documentation/admin-guide/ |
| D | kernel-parameters.txt | 12 acpi= [HW,ACPI,X86,ARM64,RISCV64,EARLY]
16 force -- enable ACPI if default was off
17 on -- enable ACPI but allow fallback to DT [arm64,riscv64]
18 off -- disable ACPI if default was on
19 noirq -- do not use ACPI for IRQ routing
20 strict -- Be less tolerant of platforms that are not
21 strictly ACPI specification compliant.
22 rsdt -- prefer RSDT over (default) XSDT
23 copy_dsdt -- copy DSDT to memory
24 nospcr -- disable console in ACPI SPCR table as
[all …]
|