Documentation/devicetree/bindings/rng/brcm,iproc-rng200.yaml
Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/rng/brcm,iproc-rng200.yaml
File Facts
- System
- Linux kernel
- Corpus path
Documentation/devicetree/bindings/rng/brcm,iproc-rng200.yaml- Extension
.yaml- Size
- 756 bytes
- Lines
- 37
- Domain
- Support Tooling And Documentation
- Bucket
- Documentation
- Inferred role
- Support Tooling And Documentation: configuration, schema, or hardware description
- Status
- atlas-only
Why This File Exists
Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
Dependency Surface
dt-bindings/interrupt-controller/arm-gic.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
%YAML 1.2
---
$id: http://devicetree.org/schemas/rng/brcm,iproc-rng200.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: HWRNG support for the iproc-rng200 driver
maintainers:
- Florian Fainelli <f.fainelli@gmail.com>
properties:
compatible:
enum:
- brcm,bcm2711-rng200
- brcm,bcm7211-rng200
- brcm,bcm7278-rng200
- brcm,iproc-rng200
reg:
maxItems: 1
interrupts:
maxItems: 1
additionalProperties: false
examples:
- |
#include <dt-bindings/interrupt-controller/arm-gic.h>
rng@18032000 {
compatible = "brcm,iproc-rng200";
reg = <0x18032000 0x28>;
interrupts = <GIC_SPI 83 IRQ_TYPE_LEVEL_HIGH>;
};
Annotation
- Immediate include surface: `dt-bindings/interrupt-controller/arm-gic.h`.
- Atlas domain: Support Tooling And Documentation / Documentation.
- Implementation status: atlas-only.
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.