drivers/char/hw_random/pseries-rng.c

File Facts

System

Linux kernel

Corpus path

drivers/char/hw_random/pseries-rng.c

Extension

.c

Size

2205 bytes

Lines

93

Domain

Driver Families

Bucket

drivers/char

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/hw_random.h
• asm/vio.h

Detected Declarations

• function Copyright
• function pseries_rng_get_desired_dma
• function pseries_rng_probe
• function pseries_rng_remove
• function rng_init
• function rng_exit
• module init rng_init

Annotated Snippet

module_init(rng_init);

static void __exit rng_exit(void)
{
	vio_unregister_driver(&pseries_rng_driver);
}
module_exit(rng_exit);

MODULE_LICENSE("GPL");
MODULE_AUTHOR("Michael Neuling <mikey@neuling.org>");
MODULE_DESCRIPTION("H/W RNG driver for IBM pSeries processors");

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/hw_random.h`, `asm/vio.h`.
• Detected declarations: `function Copyright`, `function pseries_rng_get_desired_dma`, `function pseries_rng_probe`, `function pseries_rng_remove`, `function rng_init`, `function rng_exit`, `module init rng_init`.
• Atlas domain: Driver Families / drivers/char.
• 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.