drivers/i2c/busses/i2c-omap.c
Source file repositories/reference/linux-study-clean/drivers/i2c/busses/i2c-omap.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/i2c/busses/i2c-omap.c- Extension
.c- Size
- 43473 bytes
- Lines
- 1633
- 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.
- Touches IRQ or DMA behavior; this matters for the representative real-device path.
- 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/module.hlinux/delay.hlinux/i2c.hlinux/err.hlinux/interrupt.hlinux/completion.hlinux/platform_device.hlinux/clk.hlinux/io.hlinux/mux/consumer.hlinux/of.hlinux/slab.hlinux/platform_data/i2c-omap.hlinux/pm_runtime.hlinux/pinctrl/consumer.hlinux/property.h
Detected Declarations
struct omap_i2c_devfunction omap_i2c_write_regfunction omap_i2c_read_regfunction __omap_i2c_initfunction omap_i2c_resetfunction omap_i2c_initfunction omap_i2c_recover_busfunction omap_i2c_wait_for_bbfunction omap_i2c_wait_for_bb_validfunction omap_i2c_resize_fifofunction omap_i2c_waitfunction omap_i2c_xfer_msgfunction omap_i2c_xfer_commonfunction omap_i2c_xfer_irqfunction omap_i2c_xfer_pollingfunction omap_i2c_funcfunction omap_i2c_complete_cmdfunction omap_i2c_ack_statfunction i2c_omap_errata_i207function omap_i2c_omap1_isrfunction errata_omap3_i462function omap_i2c_receive_datafunction omap_i2c_transmit_datafunction omap_i2c_xfer_datafunction omap_i2c_isr_threadfunction omap_i2c_get_sclfunction omap_i2c_get_sdafunction omap_i2c_set_sclfunction omap_i2c_prepare_recoveryfunction omap_i2c_unprepare_recoveryfunction omap_i2c_probefunction omap_i2c_removefunction omap_i2c_runtime_suspendfunction omap_i2c_runtime_resumefunction omap_i2c_suspendfunction omap_i2c_resumefunction omap_i2c_init_driverfunction omap_i2c_exit_drivermodule init omap_i2c_init_driver
Annotated Snippet
subsys_initcall(omap_i2c_init_driver);
static void __exit omap_i2c_exit_driver(void)
{
platform_driver_unregister(&omap_i2c_driver);
}
module_exit(omap_i2c_exit_driver);
MODULE_AUTHOR("MontaVista Software, Inc. (and others)");
MODULE_DESCRIPTION("TI OMAP I2C bus adapter");
MODULE_LICENSE("GPL");
MODULE_ALIAS("platform:omap_i2c");
Annotation
- Immediate include surface: `linux/module.h`, `linux/delay.h`, `linux/i2c.h`, `linux/err.h`, `linux/interrupt.h`, `linux/completion.h`, `linux/platform_device.h`, `linux/clk.h`.
- Detected declarations: `struct omap_i2c_dev`, `function omap_i2c_write_reg`, `function omap_i2c_read_reg`, `function __omap_i2c_init`, `function omap_i2c_reset`, `function omap_i2c_init`, `function omap_i2c_recover_bus`, `function omap_i2c_wait_for_bb`, `function omap_i2c_wait_for_bb_valid`, `function omap_i2c_resize_fifo`.
- Atlas domain: Driver Families / drivers/i2c.
- Implementation status: integration implementation candidate.
- IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.
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.