drivers/mfd/da9052-spi.c

File Facts

System

Linux kernel

Corpus path

drivers/mfd/da9052-spi.c

Extension

.c

Size

2257 bytes

Lines

105

Domain

Driver Families

Bucket

drivers/mfd

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/device.h
• linux/module.h
• linux/input.h
• linux/mfd/core.h
• linux/spi/spi.h
• linux/err.h
• linux/mfd/da9052/da9052.h

Detected Declarations

• function Copyright
• function da9052_spi_remove
• function da9052_spi_init
• function da9052_spi_exit
• module init da9052_spi_init

Annotated Snippet

subsys_initcall(da9052_spi_init);

static void __exit da9052_spi_exit(void)
{
	spi_unregister_driver(&da9052_spi_driver);
}
module_exit(da9052_spi_exit);

MODULE_AUTHOR("David Dajun Chen <dchen@diasemi.com>");
MODULE_DESCRIPTION("SPI driver for Dialog DA9052 PMIC");

Annotation

• Immediate include surface: `linux/device.h`, `linux/module.h`, `linux/input.h`, `linux/mfd/core.h`, `linux/spi/spi.h`, `linux/err.h`, `linux/mfd/da9052/da9052.h`.
• Detected declarations: `function Copyright`, `function da9052_spi_remove`, `function da9052_spi_init`, `function da9052_spi_exit`, `module init da9052_spi_init`.
• Atlas domain: Driver Families / drivers/mfd.
• 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.