drivers/i2c/busses/i2c-pasemi-core.h

File Facts

System

Linux kernel

Corpus path

drivers/i2c/busses/i2c-pasemi-core.h

Extension

.h

Size

609 bytes

Lines

27

Domain

Driver Families

Bucket

drivers/i2c

Inferred role

Driver Families: implementation source

Status

source 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.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/atomic.h
• linux/clk.h
• linux/delay.h
• linux/device.h
• linux/i2c.h
• linux/i2c-smbus.h
• linux/io.h
• linux/kernel.h
• linux/completion.h

Detected Declarations

• struct pasemi_smbus

Annotated Snippet

struct pasemi_smbus {
	struct device		*dev;
	struct i2c_adapter	 adapter;
	void __iomem		*ioaddr;
	unsigned int		 clk_div;
	int			 hw_rev;
	int			 use_irq;
	struct completion	 irq_completion;
};

int pasemi_i2c_common_probe(struct pasemi_smbus *smbus);

irqreturn_t pasemi_irq_handler(int irq, void *dev_id);

Annotation

• Immediate include surface: `linux/atomic.h`, `linux/clk.h`, `linux/delay.h`, `linux/device.h`, `linux/i2c.h`, `linux/i2c-smbus.h`, `linux/io.h`, `linux/kernel.h`.
• Detected declarations: `struct pasemi_smbus`.
• Atlas domain: Driver Families / drivers/i2c.
• Implementation status: source 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.