Documentation/devicetree/bindings/mtd/partitions/ubi-volume.yaml

Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/mtd/partitions/ubi-volume.yaml

File Facts

System: Linux kernel
Corpus path: Documentation/devicetree/bindings/mtd/partitions/ubi-volume.yaml
Extension: .yaml
Size: 919 bytes
Lines: 41
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/mtd/partitions/ubi-volume.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#

title: UBI volume

description: |
  This binding describes a single UBI volume. Volumes can be matches either
  by their ID or their name, or both.

maintainers:
  - Daniel Golle <daniel@makrotopia.org>

properties:
  volid:
    $ref: /schemas/types.yaml#/definitions/uint32
    description:
      Match UBI volume ID

  volname:
    $ref: /schemas/types.yaml#/definitions/string
    description:
      Match UBI volume ID

  nvmem-layout:
    $ref: /schemas/nvmem/layouts/nvmem-layout.yaml#
    description:
      This container may reference an NVMEM layout parser.

anyOf:
  - required:
      - volid

  - required:
      - volname

# This is a generic file other binding inherit from and extend
additionalProperties: true

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.