drivers/char/hw_random/amd-rng.c
Source file repositories/reference/linux-study-clean/drivers/char/hw_random/amd-rng.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/char/hw_random/amd-rng.c- Extension
.c- Size
- 4920 bytes
- Lines
- 223
- 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.hlinux/hw_random.hlinux/io.hlinux/kernel.hlinux/module.hlinux/pci.h
Detected Declarations
struct amd768_privfunction amd_rng_readfunction amd_rng_initfunction amd_rng_cleanupfunction amd_rng_mod_initfunction for_each_pci_devfunction amd_rng_mod_exitmodule init amd_rng_mod_init
Annotated Snippet
module_init(amd_rng_mod_init);
module_exit(amd_rng_mod_exit);
MODULE_AUTHOR("The Linux Kernel team");
MODULE_DESCRIPTION("H/W RNG driver for AMD chipsets");
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 amd768_priv`, `function amd_rng_read`, `function amd_rng_init`, `function amd_rng_cleanup`, `function amd_rng_mod_init`, `function for_each_pci_dev`, `function amd_rng_mod_exit`, `module init amd_rng_mod_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.