Documentation/ABI/testing/sysfs-bus-wmi
Source file repositories/reference/linux-study-clean/Documentation/ABI/testing/sysfs-bus-wmi
File Facts
- System
- Linux kernel
- Corpus path
Documentation/ABI/testing/sysfs-bus-wmi- Extension
[no extension]- Size
- 3151 bytes
- Lines
- 82
- Domain
- Support Tooling And Documentation
- Bucket
- Documentation
- Inferred role
- Support Tooling And Documentation: Documentation
- Status
- atlas-only
Why This File Exists
Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
What: /sys/bus/wmi/devices/.../driver_override
Date: February 2024
Contact: Armin Wolf <W_Armin@gmx.de>
Description:
This file allows the driver for a device to be specified which
will override standard ID table matching.
When specified, only a driver with a name matching the value
written to driver_override will have an opportunity to bind
to the device.
The override is specified by writing a string to the
driver_override file (echo wmi-event-dummy > driver_override).
The override may be cleared with an empty string (echo > \
driver_override) which returns the device to standard matching
rules binding.
Writing to driver_override does not automatically unbind the
device from its current driver or make any attempt to automatically
load the specified driver. If no driver with a matching name is
currently loaded in the kernel, the device will not bind to any
driver.
This also allows devices to opt-out of driver binding using a
driver_override name such as "none". Only a single driver may be
specified in the override, there is no support for parsing delimiters.
What: /sys/bus/wmi/devices/.../modalias
Date: November 20:15
Contact: Andy Lutomirski <luto@kernel.org>
Description:
This file contains the MODALIAS value emitted by uevent for a
given WMI device.
Format: wmi:XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX.
What: /sys/bus/wmi/devices/.../guid
Date: November 2015
Contact: Andy Lutomirski <luto@kernel.org>
Description:
This file contains the GUID used to match WMI devices to
compatible WMI drivers. This GUID is not necessarily unique
inside a given machine, it is solely used to identify the
interface exposed by a given WMI device.
What: /sys/bus/wmi/devices/.../object_id
Date: November 2015
Contact: Andy Lutomirski <luto@kernel.org>
Description:
This file contains the WMI object ID used internally to construct
the ACPI method names used by non-event WMI devices. It contains
two ASCII letters.
What: /sys/bus/wmi/devices/.../notify_id
Date: November 2015
Contact: Andy Lutomirski <luto@kernel.org>
Description:
This file contains the WMI notify ID used internally to map ACPI
events to WMI event devices. It contains two ASCII letters.
What: /sys/bus/wmi/devices/.../instance_count
Date: November 2015
Contact: Andy Lutomirski <luto@kernel.org>
Description:
This file contains the number of WMI object instances being
present on a given WMI device. It contains a non-negative
number.
What: /sys/bus/wmi/devices/.../expensive
Date: November 2015
Contact: Andy Lutomirski <luto@kernel.org>
Description:
This file contains a boolean flag signaling if interacting with
the given WMI device will consume significant CPU resources.
Annotation
- Atlas domain: Support Tooling And Documentation / Documentation.
- Implementation status: atlas-only.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.