Documentation/devicetree/bindings/nvmem/layouts/nvmem-layout.yaml

Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/nvmem/layouts/nvmem-layout.yaml

File Facts

System: Linux kernel
Corpus path: Documentation/devicetree/bindings/nvmem/layouts/nvmem-layout.yaml
Extension: .yaml
Size: 931 bytes
Lines: 33
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/nvmem/layouts/nvmem-layout.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#

title: NVMEM (Non Volatile Memory) layouts

maintainers:
  - Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
  - Michael Walle <michael@walle.cc>
  - Miquel Raynal <miquel.raynal@bootlin.com>

description: |
  Most NVMEM layouts are static and thus do not require additional description
  besides the bytes/bits offset and length. Other layouts can be less statically
  define and might require dynamic reading of the NVMEM device in order to
  perform their parsing. The nvmem-layout container is here to describe these.

oneOf:
  - $ref: fixed-layout.yaml
  - $ref: kontron,sl28-vpd.yaml
  - $ref: onie,tlv-layout.yaml
  - $ref: u-boot,env.yaml

properties:
  compatible: true

required:
  - compatible

unevaluatedProperties: false

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.