drivers/i2c/busses/i2c-mxs.c

File Facts

System

Linux kernel

Corpus path

drivers/i2c/busses/i2c-mxs.c

Extension

.c

Size

24861 bytes

Lines

912

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/slab.h
• linux/device.h
• linux/module.h
• linux/i2c.h
• linux/err.h
• linux/interrupt.h
• linux/completion.h
• linux/platform_device.h
• linux/jiffies.h
• linux/io.h
• linux/stmp_device.h
• linux/of.h
• linux/dma-mapping.h
• linux/dmaengine.h
• linux/dma/mxs-dma.h

Detected Declarations

• struct mxs_i2c_dev
• enum mxs_i2c_devtype
• function mxs_i2c_reset
• function mxs_i2c_dma_finish
• function mxs_i2c_dma_irq_callback
• function mxs_i2c_dma_setup_xfer
• function mxs_i2c_pio_wait_xfer_end
• function mxs_i2c_pio_check_error_state
• function mxs_i2c_pio_trigger_cmd
• function mxs_i2c_pio_trigger_write_cmd
• function mxs_i2c_pio_setup_xfer
• function mxs_i2c_xfer_msg
• function mxs_i2c_xfer
• function mxs_i2c_func
• function mxs_i2c_isr
• function mxs_i2c_derive_timing
• function tBUF
• function mxs_i2c_get_ofdata
• function mxs_i2c_probe
• function mxs_i2c_remove
• function mxs_i2c_init
• function mxs_i2c_exit
• module init mxs_i2c_init

Annotated Snippet

subsys_initcall(mxs_i2c_init);

static void __exit mxs_i2c_exit(void)
{
	platform_driver_unregister(&mxs_i2c_driver);
}
module_exit(mxs_i2c_exit);

MODULE_AUTHOR("Marek Vasut <marex@denx.de>");
MODULE_AUTHOR("Wolfram Sang <kernel@pengutronix.de>");
MODULE_DESCRIPTION("MXS I2C Bus Driver");
MODULE_LICENSE("GPL");
MODULE_ALIAS("platform:" DRIVER_NAME);

Annotation

• Immediate include surface: `linux/slab.h`, `linux/device.h`, `linux/module.h`, `linux/i2c.h`, `linux/err.h`, `linux/interrupt.h`, `linux/completion.h`, `linux/platform_device.h`.
• Detected declarations: `struct mxs_i2c_dev`, `enum mxs_i2c_devtype`, `function mxs_i2c_reset`, `function mxs_i2c_dma_finish`, `function mxs_i2c_dma_irq_callback`, `function mxs_i2c_dma_setup_xfer`, `function mxs_i2c_pio_wait_xfer_end`, `function mxs_i2c_pio_check_error_state`, `function mxs_i2c_pio_trigger_cmd`, `function mxs_i2c_pio_trigger_write_cmd`.
• 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.