Documentation/ABI/testing/sysfs-platform-intel-wmi-sbl-fw-update

Source file repositories/reference/linux-study-clean/Documentation/ABI/testing/sysfs-platform-intel-wmi-sbl-fw-update

File Facts

System: Linux kernel
Corpus path: Documentation/ABI/testing/sysfs-platform-intel-wmi-sbl-fw-update
Extension: [no extension]
Size: 538 bytes
Lines: 14
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.

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/44FADEB1-B204-40F2-8581-394BBDC1B651[-X]/firmware_update_request
Date:		April 2020
KernelVersion:	5.7
Contact:	"Jithu Joseph" <jithu.joseph@intel.com>
Description:
		Allow user space entities to trigger update of Slim
		Bootloader (SBL). This attribute normally has a value
		of 0 and userspace can signal SBL to update firmware,
		on next reboot, by writing a value of 1.
		There are two available states:

		    * 0 -> Skip firmware update while rebooting
		    * 1 -> Attempt firmware update on next reboot

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.