Documentation/devicetree/bindings/reserved-memory/nvidia,tegra210-emc-table.yaml

Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/reserved-memory/nvidia,tegra210-emc-table.yaml

File Facts

System: Linux kernel
Corpus path: Documentation/devicetree/bindings/reserved-memory/nvidia,tegra210-emc-table.yaml
Extension: .yaml
Size: 741 bytes
Lines: 32
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

No C-style include directives detected by the generator.

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/reserved-memory/nvidia,tegra210-emc-table.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#

title: NVIDIA Tegra210 EMC Frequency Table

maintainers:
  - Thierry Reding <thierry.reding@gmail.com>
  - Jon Hunter <jonathanh@nvidia.com>

description: On Tegra210, firmware passes a binary representation of the
  EMC frequency table via a reserved memory region.

allOf:
  - $ref: reserved-memory.yaml

properties:
  compatible:
    const: nvidia,tegra210-emc-table

  reg:
    description: region of memory reserved by firmware to pass the EMC
      frequency table

unevaluatedProperties: false

required:
  - compatible
  - reg

Annotation

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.