drivers/iio/trigger/iio-trig-sysfs.c

File Facts

System

Linux kernel

Corpus path

drivers/iio/trigger/iio-trig-sysfs.c

Extension

.c

Size

4929 bytes

Lines

226

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/kernel.h
• linux/module.h
• linux/platform_device.h
• linux/slab.h
• linux/list.h
• linux/irq_work.h
• linux/iio/iio.h
• linux/iio/trigger.h

Detected Declarations

• struct iio_sysfs_trig
• function iio_sysfs_trig_add
• function iio_sysfs_trig_remove
• function iio_trigger_sysfs_release
• function iio_sysfs_trigger_work
• function iio_sysfs_trigger_poll
• function iio_sysfs_trigger_probe
• function iio_sysfs_trigger_remove
• function iio_sysfs_trig_init
• function iio_sysfs_trig_exit
• module init iio_sysfs_trig_init

Annotated Snippet

ret = device_add(&iio_sysfs_trig_dev);
	if (ret)
		put_device(&iio_sysfs_trig_dev);
	return ret;
}
module_init(iio_sysfs_trig_init);

static void __exit iio_sysfs_trig_exit(void)
{
	device_unregister(&iio_sysfs_trig_dev);
}
module_exit(iio_sysfs_trig_exit);

MODULE_AUTHOR("Michael Hennerich <michael.hennerich@analog.com>");
MODULE_DESCRIPTION("Sysfs based trigger for the iio subsystem");
MODULE_LICENSE("GPL v2");
MODULE_ALIAS("platform:iio-trig-sysfs");

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/platform_device.h`, `linux/slab.h`, `linux/list.h`, `linux/irq_work.h`, `linux/iio/iio.h`, `linux/iio/trigger.h`.
• Detected declarations: `struct iio_sysfs_trig`, `function iio_sysfs_trig_add`, `function iio_sysfs_trig_remove`, `function iio_trigger_sysfs_release`, `function iio_sysfs_trigger_work`, `function iio_sysfs_trigger_poll`, `function iio_sysfs_trigger_probe`, `function iio_sysfs_trigger_remove`, `function iio_sysfs_trig_init`, `function iio_sysfs_trig_exit`.
• Atlas domain: Driver Families / drivers/iio.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.