drivers/i2c/busses/i2c-imx.c
Source file repositories/reference/linux-study-clean/drivers/i2c/busses/i2c-imx.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/i2c/busses/i2c-imx.c- Extension
.c- Size
- 56979 bytes
- Lines
- 1992
- 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.
- Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
- 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/acpi.hlinux/clk.hlinux/cleanup.hlinux/completion.hlinux/delay.hlinux/dma-mapping.hlinux/dmaengine.hlinux/dmapool.hlinux/err.hlinux/errno.hlinux/gpio/consumer.hlinux/i2c.hlinux/init.hlinux/interrupt.hlinux/io.hlinux/iopoll.hlinux/kernel.hlinux/spinlock.hlinux/hrtimer.hlinux/module.hlinux/of.hlinux/of_dma.hlinux/pinctrl/consumer.hlinux/platform_data/i2c-imx.hlinux/platform_device.hlinux/pm_runtime.hlinux/sched.hlinux/slab.h
Detected Declarations
struct imx_i2c_clk_pairstruct imx_i2c_hwdatastruct imx_i2c_dmastruct imx_i2c_structenum imx_i2c_typeenum imx_i2c_statefunction is_imx1_i2cfunction is_vf610_i2cfunction imx_i2c_write_regfunction imx_i2c_read_regfunction i2c_imx_clear_irqfunction i2c_imx_reset_regsfunction i2c_imx_dma_requestfunction i2c_imx_dma_callbackfunction i2c_imx_dma_xferfunction i2c_imx_dma_freefunction i2c_imx_bus_busyfunction i2c_imx_trx_completefunction i2c_imx_ackedfunction i2c_imx_set_clkfunction i2c_imx_clk_notifier_callfunction i2c_imx_startfunction i2c_imx_stopfunction i2c_imx_enable_bus_idlefunction i2c_imx_slave_eventfunction i2c_imx_slave_finish_opfunction i2c_imx_slave_handlefunction i2c_imx_slave_timeoutfunction i2c_imx_slave_initfunction i2c_imx_reg_slavefunction i2c_imx_unreg_slavefunction i2c_imx_isr_ackedfunction i2c_imx_isr_writefunction i2c_imx_isr_readfunction i2c_imx_isr_read_continuefunction i2c_imx_isr_read_block_data_lenfunction i2c_imx_master_isrfunction i2c_imx_isrfunction scoped_guardfunction i2c_imx_dma_writefunction i2c_imx_prepare_readfunction i2c_imx_dma_readfunction i2c_imx_atomic_writefunction i2c_imx_writefunction i2c_imx_atomic_readfunction i2c_imx_readfunction i2c_imx_xfer_commonfunction gpiod_get_value_cansleep
Annotated Snippet
subsys_initcall(i2c_adap_imx_init);
static void __exit i2c_adap_imx_exit(void)
{
platform_driver_unregister(&i2c_imx_driver);
}
module_exit(i2c_adap_imx_exit);
MODULE_LICENSE("GPL");
MODULE_AUTHOR("Darius Augulis");
MODULE_DESCRIPTION("I2C adapter driver for IMX I2C bus");
MODULE_ALIAS("platform:" DRIVER_NAME);
Annotation
- Immediate include surface: `linux/acpi.h`, `linux/clk.h`, `linux/cleanup.h`, `linux/completion.h`, `linux/delay.h`, `linux/dma-mapping.h`, `linux/dmaengine.h`, `linux/dmapool.h`.
- Detected declarations: `struct imx_i2c_clk_pair`, `struct imx_i2c_hwdata`, `struct imx_i2c_dma`, `struct imx_i2c_struct`, `enum imx_i2c_type`, `enum imx_i2c_state`, `function is_imx1_i2c`, `function is_vf610_i2c`, `function imx_i2c_write_reg`, `function imx_i2c_read_reg`.
- Atlas domain: Driver Families / drivers/i2c.
- Implementation status: integration implementation candidate.
- Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
- 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.