Documentation/ABI/stable/sysfs-driver-misc-cp500

Source file repositories/reference/linux-study-clean/Documentation/ABI/stable/sysfs-driver-misc-cp500

File Facts

System: Linux kernel
Corpus path: Documentation/ABI/stable/sysfs-driver-misc-cp500
Extension: [no extension]
Size: 985 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/devices/pciXXXX:XX/0000:XX:XX.X/0000:XX:XX.X/version
Date:		June 2024
KernelVersion:	6.11
Contact:	Gerhard Engleder <eg@keba.com>
Description:	Version of the FPGA configuration bitstream as printable string.
		This file is read only.
Users:		KEBA

What:		/sys/devices/pciXXXX:XX/0000:XX:XX.X/0000:XX:XX.X/keep_cfg
Date:		June 2024
KernelVersion:	6.11
Contact:	Gerhard Engleder <eg@keba.com>
Description:	Flag which signals if FPGA shall keep or reload configuration
		bitstream on reset. Normal FPGA behavior and default is to keep
		configuration bitstream and to only reset the configured logic.

		Reloading configuration on reset enables an update of the
		configuration bitstream with a simple reboot. Otherwise it is
		necessary to power cycle the device to reload the new
		configuration bitstream.

		This file is read/write. The values are as follows:
		1 = keep configuration bitstream on reset, default
		0 = reload configuration bitstream on reset
Users:		KEBA

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.