Documentation/devicetree/bindings/display/brcm,bcm2835-vc4.yaml

File Facts

System

Linux kernel

Corpus path

Documentation/devicetree/bindings/display/brcm,bcm2835-vc4.yaml

Extension

.yaml

Size

708 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

• 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
%YAML 1.2
---
$id: http://devicetree.org/schemas/display/brcm,bcm2835-vc4.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#

title: Broadcom VC4 (VideoCore4) GPU

maintainers:
  - Eric Anholt <eric@anholt.net>

description: >
  The VC4 device present on the Raspberry Pi includes a display system
  with HDMI output and the HVS (Hardware Video Scaler) for compositing
  display planes.

properties:
  compatible:
    enum:
      - brcm,bcm2711-vc5
      - brcm,bcm2712-vc6
      - brcm,bcm2835-vc4
      - brcm,cygnus-vc4

required:
  - compatible

additionalProperties: false

examples:
  - |
    vc4: gpu {
        compatible = "brcm,bcm2835-vc4";
    };

...

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.