drivers/iio/industrialio-configfs.c

File Facts

System

Linux kernel

Corpus path

drivers/iio/industrialio-configfs.c

Extension

.c

Size

1124 bytes

Lines

49

Domain

Driver Families

Bucket

drivers/iio

Inferred role

Driver Families: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

• Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/configfs.h
• linux/module.h
• linux/init.h
• linux/kmod.h
• linux/slab.h
• linux/iio/iio.h
• linux/iio/configfs.h

Detected Declarations

• function iio_configfs_init
• function iio_configfs_exit
• module init iio_configfs_init
• export iio_configfs_subsys

Annotated Snippet

module_init(iio_configfs_init);

static void __exit iio_configfs_exit(void)
{
	configfs_unregister_subsystem(&iio_configfs_subsys);
}
module_exit(iio_configfs_exit);

MODULE_AUTHOR("Daniel Baluta <daniel.baluta@intel.com>");
MODULE_DESCRIPTION("Industrial I/O configfs support");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/configfs.h`, `linux/module.h`, `linux/init.h`, `linux/kmod.h`, `linux/slab.h`, `linux/iio/iio.h`, `linux/iio/configfs.h`.
• Detected declarations: `function iio_configfs_init`, `function iio_configfs_exit`, `module init iio_configfs_init`, `export iio_configfs_subsys`.
• Atlas domain: Driver Families / drivers/iio.
• Implementation status: integration implementation candidate.

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.