drivers/interconnect/qcom/milos.c

File Facts

System

Linux kernel

Corpus path

drivers/interconnect/qcom/milos.c

Extension

.c

Size

44077 bytes

Lines

1920

Domain

Driver Families

Bucket

drivers/interconnect

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/device.h
• linux/interconnect-provider.h
• linux/interconnect.h
• linux/io.h
• linux/module.h
• linux/of_device.h
• linux/of_platform.h
• linux/platform_device.h
• dt-bindings/interconnect/qcom,milos-rpmh.h
• bcm-voter.h
• icc-common.h
• icc-rpmh.h

Detected Declarations

• function qnoc_driver_init
• function qnoc_driver_exit
• module init qnoc_driver_init

Annotated Snippet

core_initcall(qnoc_driver_init);

static void __exit qnoc_driver_exit(void)
{
	platform_driver_unregister(&qnoc_driver);
}
module_exit(qnoc_driver_exit);

MODULE_DESCRIPTION("Milos NoC driver");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/device.h`, `linux/interconnect-provider.h`, `linux/interconnect.h`, `linux/io.h`, `linux/module.h`, `linux/of_device.h`, `linux/of_platform.h`, `linux/platform_device.h`.
• Detected declarations: `function qnoc_driver_init`, `function qnoc_driver_exit`, `module init qnoc_driver_init`.
• Atlas domain: Driver Families / drivers/interconnect.
• 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.