drivers/i2c/i2c-stub.c
Source file repositories/reference/linux-study-clean/drivers/i2c/i2c-stub.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/i2c/i2c-stub.c- Extension
.c- Size
- 10112 bytes
- Lines
- 418
- 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.
- 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/errno.hlinux/i2c.hlinux/init.hlinux/kernel.hlinux/list.hlinux/module.hlinux/slab.h
Detected Declarations
struct smbus_block_datastruct stub_chipfunction list_for_each_entryfunction stub_xferfunction stub_funcfunction i2c_stub_allocate_banksfunction i2c_stub_freefunction i2c_stub_initfunction i2c_stub_exitmodule init i2c_stub_init
Annotated Snippet
module_init(i2c_stub_init);
module_exit(i2c_stub_exit);Annotation
- Immediate include surface: `linux/errno.h`, `linux/i2c.h`, `linux/init.h`, `linux/kernel.h`, `linux/list.h`, `linux/module.h`, `linux/slab.h`.
- Detected declarations: `struct smbus_block_data`, `struct stub_chip`, `function list_for_each_entry`, `function stub_xfer`, `function stub_func`, `function i2c_stub_allocate_banks`, `function i2c_stub_free`, `function i2c_stub_init`, `function i2c_stub_exit`, `module init i2c_stub_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.