drivers/char/hw_random/cavium-rng.c

File Facts

System

Linux kernel

Corpus path

drivers/char/hw_random/cavium-rng.c

Extension

.c

Size

2226 bytes

Lines

93

Domain

Driver Families

Bucket

drivers/char

Inferred role

Driver Families: operation-table or driver-model contract

Status

pattern 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.
• Defines an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• 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/hw_random.h
• linux/io.h
• linux/module.h
• linux/pci.h
• linux/pci_ids.h

Detected Declarations

• struct cavium_rng_pf
• function cavium_rng_probe
• function cavium_rng_remove

Annotated Snippet

static struct pci_driver cavium_rng_pf_driver = {
	.name		= "cavium_rng_pf",
	.id_table	= cavium_rng_pf_id_table,
	.probe		= cavium_rng_probe,
	.remove		= cavium_rng_remove,
};

module_pci_driver(cavium_rng_pf_driver);
MODULE_AUTHOR("Omer Khaliq <okhaliq@caviumnetworks.com>");
MODULE_DESCRIPTION("Cavium ThunderX Random Number Generator support");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/hw_random.h`, `linux/io.h`, `linux/module.h`, `linux/pci.h`, `linux/pci_ids.h`.
• Detected declarations: `struct cavium_rng_pf`, `function cavium_rng_probe`, `function cavium_rng_remove`.
• Atlas domain: Driver Families / drivers/char.
• Implementation status: pattern 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.