drivers/i2c/busses/i2c-s3c2410.c

File Facts

System

Linux kernel

Corpus path

drivers/i2c/busses/i2c-s3c2410.c

Extension

.c

Size

30291 bytes

Lines

1207

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/kernel.h
• linux/module.h
• linux/i2c.h
• linux/init.h
• linux/time.h
• linux/interrupt.h
• linux/delay.h
• linux/errno.h
• linux/err.h
• linux/platform_device.h
• linux/pm_runtime.h
• linux/clk.h
• linux/cpufreq.h
• linux/slab.h
• linux/io.h
• linux/of.h
• linux/gpio/consumer.h
• linux/pinctrl/consumer.h
• linux/mfd/syscon.h
• linux/regmap.h
• asm/irq.h
• linux/platform_data/i2c-s3c2410.h

Detected Declarations

• struct s3c24xx_i2c
• enum s3c24xx_i2c_state
• function s3c24xx_get_device_quirks
• function s3c24xx_i2c_master_complete
• function s3c24xx_i2c_disable_ack
• function s3c24xx_i2c_enable_ack
• function s3c24xx_i2c_disable_irq
• function s3c24xx_i2c_enable_irq
• function is_ack
• function s3c24xx_i2c_message_start
• function s3c24xx_i2c_stop
• function bus
• function is_lastmsg
• function is_msglast
• function is_msgend
• function i2c_s3c_irq_nextbyte
• function s3c24xx_i2c_irq
• function s3c24xx_i2c_disable_bus
• function s3c24xx_i2c_set_master
• function s3c24xx_i2c_wait_idle
• function ktime_us_delta
• function s3c24xx_i2c_doxfer
• function s3c24xx_i2c_xfer
• function s3c24xx_i2c_xfer_atomic
• function s3c24xx_i2c_func
• function s3c24xx_i2c_calcdivisor
• function s3c24xx_i2c_clockrate
• function s3c24xx_i2c_parse_dt_gpio
• function s3c24xx_i2c_parse_dt_gpio
• function s3c24xx_i2c_init
• function s3c24xx_i2c_parse_dt
• function s3c24xx_i2c_parse_dt
• function unit
• function s3c24xx_i2c_remove
• function s3c24xx_i2c_suspend_noirq
• function s3c24xx_i2c_resume_noirq
• function i2c_adap_s3c_init
• function i2c_adap_s3c_exit
• module init i2c_adap_s3c_init

Annotated Snippet

subsys_initcall(i2c_adap_s3c_init);

static void __exit i2c_adap_s3c_exit(void)
{
	platform_driver_unregister(&s3c24xx_i2c_driver);
}
module_exit(i2c_adap_s3c_exit);

MODULE_DESCRIPTION("S3C24XX I2C Bus driver");
MODULE_AUTHOR("Ben Dooks <ben@simtec.co.uk>");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/i2c.h`, `linux/init.h`, `linux/time.h`, `linux/interrupt.h`, `linux/delay.h`, `linux/errno.h`.
• Detected declarations: `struct s3c24xx_i2c`, `enum s3c24xx_i2c_state`, `function s3c24xx_get_device_quirks`, `function s3c24xx_i2c_master_complete`, `function s3c24xx_i2c_disable_ack`, `function s3c24xx_i2c_enable_ack`, `function s3c24xx_i2c_disable_irq`, `function s3c24xx_i2c_enable_irq`, `function is_ack`, `function s3c24xx_i2c_message_start`.
• 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.