Documentation/devicetree/bindings/bus/mti,mips-cdmm.yaml

File Facts

System

Linux kernel

Corpus path

Documentation/devicetree/bindings/bus/mti,mips-cdmm.yaml

Extension

.yaml

Size

757 bytes

Lines

38

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-only OR BSD-2-Clause)
%YAML 1.2
---
$id: http://devicetree.org/schemas/bus/mti,mips-cdmm.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#

title: MIPS Common Device Memory Map

description: |
  Defines a location of the MIPS Common Device Memory Map registers.

maintainers:
  - James Hogan <jhogan@kernel.org>

properties:
  compatible:
    const: mti,mips-cdmm

  reg:
    description: |
      Base address and size of an unoccupied memory region, which will be
      used to map the MIPS CDMM registers block.
    maxItems: 1

required:
  - compatible
  - reg

additionalProperties: false

examples:
  - |
    cdmm@1bde8000 {
      compatible = "mti,mips-cdmm";
      reg = <0x1bde8000 0x8000>;
    };
...

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.