drivers/i2c/busses/i2c-pxa-pci.c

File Facts

System

Linux kernel

Corpus path

drivers/i2c/busses/i2c-pxa-pci.c

Extension

.c

Size

3248 bytes

Lines

150

Domain

Driver Families

Bucket

drivers/i2c

Inferred role

Driver Families: operation-table or driver-model contract

Status

pattern 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.
• Defines an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• 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/init.h
• linux/pci.h
• linux/platform_device.h
• linux/platform_data/i2c-pxa.h
• linux/of.h
• linux/of_address.h

Detected Declarations

• struct ce4100_devices
• function for_each_child_of_node
• function ce4100_i2c_probe

Annotated Snippet

static struct pci_driver ce4100_i2c_driver = {
	.driver = {
		.suppress_bind_attrs = true,
	},
	.name           = "ce4100_i2c",
	.id_table       = ce4100_i2c_devices,
	.probe          = ce4100_i2c_probe,
};
builtin_pci_driver(ce4100_i2c_driver);

Annotation

• Immediate include surface: `linux/init.h`, `linux/pci.h`, `linux/platform_device.h`, `linux/platform_data/i2c-pxa.h`, `linux/of.h`, `linux/of_address.h`.
• Detected declarations: `struct ce4100_devices`, `function for_each_child_of_node`, `function ce4100_i2c_probe`.
• Atlas domain: Driver Families / drivers/i2c.
• Implementation status: pattern 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.