Documentation/ABI/testing/sysfs-devices-firmware_node

Source file repositories/reference/linux-study-clean/Documentation/ABI/testing/sysfs-devices-firmware_node

File Facts

System: Linux kernel
Corpus path: Documentation/ABI/testing/sysfs-devices-firmware_node
Extension: [no extension]
Size: 686 bytes
Lines: 18
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/devices/.../firmware_node/
Date:		September 2012
Contact:	<>
Description:
		The /sys/devices/.../firmware_node directory contains attributes
		allowing the user space to check and modify some firmware
		related properties of given device.

What:		/sys/devices/.../firmware_node/description
Date:		September 2012
Contact:	Lance Ortiz <lance.ortiz@hp.com>
Description:
		The /sys/devices/.../firmware/description attribute contains a string
		that describes the device as provided by the _STR method in the ACPI
		namespace.  This attribute is read-only.  If the device does not have
		an _STR method associated with it in the ACPI namespace, this
		attribute is not present.

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.