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

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

File Facts

System: Linux kernel
Corpus path: Documentation/ABI/testing/sysfs-bus-fsl-mc
Extension: [no extension]
Size: 849 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/fsl-mc/drivers/.../bind
Date:		December 2016
Contact:	stuart.yoder@nxp.com
Description:
		Writing a device location to this file will cause
		the driver to attempt to bind to the device found at
		this location. The format for the location is Object.Id
		and is the same as found in /sys/bus/fsl-mc/devices/.

                For example::

		  # echo dpni.2 > /sys/bus/fsl-mc/drivers/fsl_dpaa2_eth/bind

What:		/sys/bus/fsl-mc/drivers/.../unbind
Date:		December 2016
Contact:	stuart.yoder@nxp.com
Description:
		Writing a device location to this file will cause the
		driver to attempt to unbind from the device found at
		this location. The format for the location is Object.Id
		and is the same as found in /sys/bus/fsl-mc/devices/.

                For example::

		  # echo dpni.2 > /sys/bus/fsl-mc/drivers/fsl_dpaa2_eth/unbind

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.