Documentation/ABI/testing/sysfs-bus-dfl-devices-emif

Source file repositories/reference/linux-study-clean/Documentation/ABI/testing/sysfs-bus-dfl-devices-emif

File Facts

System: Linux kernel
Corpus path: Documentation/ABI/testing/sysfs-bus-dfl-devices-emif
Extension: [no extension]
Size: 847 bytes
Lines: 26
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/dfl/devices/dfl_dev.X/infX_cal_fail
Date:		Oct 2020
KernelVersion:	5.12
Contact:	Xu Yilun <yilun.xu@intel.com>
Description:	Read-only. It indicates if the calibration failed on this
		memory interface. "1" for calibration failure, "0" for OK.
		Format: %u

What:		/sys/bus/dfl/devices/dfl_dev.X/infX_init_done
Date:		Oct 2020
KernelVersion:	5.12
Contact:	Xu Yilun <yilun.xu@intel.com>
Description:	Read-only. It indicates if the initialization completed on
		this memory interface. "1" for initialization complete, "0"
		for not yet.
		Format: %u

What:		/sys/bus/dfl/devices/dfl_dev.X/infX_clear
Date:		Oct 2020
KernelVersion:	5.12
Contact:	Xu Yilun <yilun.xu@intel.com>
Description:	Write-only. Writing "1" to this file will zero out all memory
		data in this memory interface. Writing of other values is
		invalid.
		Format: %u

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.