Documentation/ABI/stable/sysfs-bus-fsl-mc

Source file repositories/reference/linux-study-clean/Documentation/ABI/stable/sysfs-bus-fsl-mc

File Facts

System: Linux kernel
Corpus path: Documentation/ABI/stable/sysfs-bus-fsl-mc
Extension: [no extension]
Size: 712 bytes
Lines: 20
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/fsl-mc/rescan
Date:		January 2021
KernelVersion:	5.12
Contact:	Ioana Ciornei <ioana.ciornei@nxp.com>
Description:	Writing a non-zero value to this attribute will
		force a rescan of fsl-mc bus in the system and
		synchronize the objects under fsl-mc bus and the
		Management Complex firmware.
Users:		Userspace drivers and management tools

What:		/sys/bus/fsl-mc/autorescan
Date:		January 2021
KernelVersion:	5.12
Contact:	Ioana Ciornei <ioana.ciornei@nxp.com>
Description:	Writing a zero value to this attribute will
		disable the DPRC IRQs on which automatic rescan
		of the fsl-mc bus is performed. A non-zero value
		will enable the DPRC IRQs.
Users:		Userspace drivers and management tools

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.