arch/arm/mach-omap1/i2c.c

File Facts

System

Linux kernel

Corpus path

arch/arm/mach-omap1/i2c.c

Extension

.c

Size

3783 bytes

Lines

160

Domain

Architecture Layer

Bucket

arch/arm

Inferred role

Architecture Layer: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.

• CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/i2c.h
• linux/platform_data/i2c-omap.h
• mux.h
• soc.h
• i2c.h

Detected Declarations

• function omap1_i2c_mux_pins
• function omap_i2c_add_bus
• function omap_i2c_bus_setup
• function omap_register_i2c_bus_cmdline
• function omap_register_i2c_bus
• function omap_i2c_cmdline
• module init omap_i2c_cmdline

Annotated Snippet

subsys_initcall(omap_i2c_cmdline);

Annotation

• Immediate include surface: `linux/i2c.h`, `linux/platform_data/i2c-omap.h`, `mux.h`, `soc.h`, `i2c.h`.
• Detected declarations: `function omap1_i2c_mux_pins`, `function omap_i2c_add_bus`, `function omap_i2c_bus_setup`, `function omap_register_i2c_bus_cmdline`, `function omap_register_i2c_bus`, `function omap_i2c_cmdline`, `module init omap_i2c_cmdline`.
• Atlas domain: Architecture Layer / arch/arm.
• 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.