drivers/pinctrl/pinctrl-mcp23s08_i2c.c

File Facts

System

Linux kernel

Corpus path

drivers/pinctrl/pinctrl-mcp23s08_i2c.c

Extension

.c

Size

2888 bytes

Lines

116

Domain

Driver Families

Bucket

drivers/pinctrl

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.
• 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/i2c.h
• linux/mod_devicetable.h
• linux/module.h
• linux/regmap.h
• pinctrl-mcp23s08.h

Detected Declarations

• function mcp230xx_probe
• function mcp23s08_i2c_init
• function mcp23s08_i2c_exit
• module init mcp23s08_i2c_init

Annotated Snippet

subsys_initcall(mcp23s08_i2c_init);

static void mcp23s08_i2c_exit(void)
{
	i2c_del_driver(&mcp230xx_driver);
}
module_exit(mcp23s08_i2c_exit);

MODULE_DESCRIPTION("MCP23S08 I2C GPIO driver");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/i2c.h`, `linux/mod_devicetable.h`, `linux/module.h`, `linux/regmap.h`, `pinctrl-mcp23s08.h`.
• Detected declarations: `function mcp230xx_probe`, `function mcp23s08_i2c_init`, `function mcp23s08_i2c_exit`, `module init mcp23s08_i2c_init`.
• Atlas domain: Driver Families / drivers/pinctrl.
• 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.