drivers/mfd/ucb1x00-assabet.c
Source file repositories/reference/linux-study-clean/drivers/mfd/ucb1x00-assabet.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/mfd/ucb1x00-assabet.c- Extension
.c- Size
- 2775 bytes
- Lines
- 104
- Domain
- Driver Families
- Bucket
- drivers/mfd
- 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/module.hlinux/init.hlinux/device.hlinux/err.hlinux/fs.hlinux/gpio_keys.hlinux/input.hlinux/platform_device.hlinux/proc_fs.hlinux/mfd/ucb1x00.h
Detected Declarations
function ucb1x00_assabet_addfunction ucb1x00_assabet_removefunction ucb1x00_assabet_initfunction ucb1x00_assabet_exitmodule init ucb1x00_assabet_init
Annotated Snippet
module_init(ucb1x00_assabet_init);
module_exit(ucb1x00_assabet_exit);
MODULE_AUTHOR("Russell King <rmk@arm.linux.org.uk>");
MODULE_DESCRIPTION("Assabet noddy testing only example ADC driver");
MODULE_LICENSE("GPL");
Annotation
- Immediate include surface: `linux/module.h`, `linux/init.h`, `linux/device.h`, `linux/err.h`, `linux/fs.h`, `linux/gpio_keys.h`, `linux/input.h`, `linux/platform_device.h`.
- Detected declarations: `function ucb1x00_assabet_add`, `function ucb1x00_assabet_remove`, `function ucb1x00_assabet_init`, `function ucb1x00_assabet_exit`, `module init ucb1x00_assabet_init`.
- Atlas domain: Driver Families / drivers/mfd.
- 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.