drivers/i2c/busses/i2c-acorn.c
Source file repositories/reference/linux-study-clean/drivers/i2c/busses/i2c-acorn.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/i2c/busses/i2c-acorn.c- Extension
.c- Size
- 1932 bytes
- Lines
- 97
- Domain
- Driver Families
- Bucket
- drivers/i2c
- 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/i2c.hlinux/i2c-algo-bit.hlinux/io.hmach/hardware.hasm/hardware/ioc.h
Detected Declarations
function ioc_setsclfunction ioc_setsdafunction ioc_getsclfunction ioc_getsdafunction i2c_ioc_initmodule init i2c_ioc_init
Annotated Snippet
module_init(i2c_ioc_init);
MODULE_AUTHOR("Russell King <linux@armlinux.org.uk>");
MODULE_DESCRIPTION("ARM IOC/IOMD i2c driver");
MODULE_LICENSE("GPL v2");Annotation
- Immediate include surface: `linux/module.h`, `linux/i2c.h`, `linux/i2c-algo-bit.h`, `linux/io.h`, `mach/hardware.h`, `asm/hardware/ioc.h`.
- Detected declarations: `function ioc_setscl`, `function ioc_setsda`, `function ioc_getscl`, `function ioc_getsda`, `function i2c_ioc_init`, `module init i2c_ioc_init`.
- Atlas domain: Driver Families / drivers/i2c.
- 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.