drivers/i2c/busses/i2c-sibyte.c

File Facts

System

Linux kernel

Corpus path

drivers/i2c/busses/i2c-sibyte.c

Extension

.c

Size

5000 bytes

Lines

187

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/kernel.h
• linux/module.h
• linux/init.h
• linux/i2c.h
• linux/io.h
• asm/sibyte/sb1250_regs.h
• asm/sibyte/sb1250_smbus.h

Detected Declarations

• struct i2c_algo_sibyte_data
• function smbus_xfer
• function bit_func
• function i2c_sibyte_add_bus
• function i2c_sibyte_init
• function i2c_sibyte_exit
• module init i2c_sibyte_init

Annotated Snippet

module_init(i2c_sibyte_init);
module_exit(i2c_sibyte_exit);

MODULE_AUTHOR("Kip Walker (Broadcom Corp.)");
MODULE_AUTHOR("Steven J. Hill <sjhill@realitydiluted.com>");
MODULE_DESCRIPTION("SMBus adapter routines for SiByte boards");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/init.h`, `linux/i2c.h`, `linux/io.h`, `asm/sibyte/sb1250_regs.h`, `asm/sibyte/sb1250_smbus.h`.
• Detected declarations: `struct i2c_algo_sibyte_data`, `function smbus_xfer`, `function bit_func`, `function i2c_sibyte_add_bus`, `function i2c_sibyte_init`, `function i2c_sibyte_exit`, `module init i2c_sibyte_init`.
• Atlas domain: Driver Families / drivers/i2c.
• 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.