drivers/char/hw_random/geode-rng.c

File Facts

System

Linux kernel

Corpus path

drivers/char/hw_random/geode-rng.c

Extension

.c

Size

3533 bytes

Lines

162

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.
• 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/delay.h
• linux/hw_random.h
• linux/io.h
• linux/kernel.h
• linux/module.h
• linux/pci.h

Detected Declarations

• struct amd_geode_priv
• function geode_rng_data_read
• function geode_rng_data_present
• function geode_rng_init
• function for_each_pci_dev
• function geode_rng_exit
• module init geode_rng_init

Annotated Snippet

module_init(geode_rng_init);
module_exit(geode_rng_exit);

MODULE_DESCRIPTION("H/W RNG driver for AMD Geode LX CPUs");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/delay.h`, `linux/hw_random.h`, `linux/io.h`, `linux/kernel.h`, `linux/module.h`, `linux/pci.h`.
• Detected declarations: `struct amd_geode_priv`, `function geode_rng_data_read`, `function geode_rng_data_present`, `function geode_rng_init`, `function for_each_pci_dev`, `function geode_rng_exit`, `module init geode_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.