Documentation/devicetree/bindings/nvmem/maxim,max77759-nvmem.yaml

Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/nvmem/maxim,max77759-nvmem.yaml

File Facts

System: Linux kernel
Corpus path: Documentation/devicetree/bindings/nvmem/maxim,max77759-nvmem.yaml
Extension: .yaml
Size: 824 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-only OR BSD-2-Clause)
%YAML 1.2
---
$id: http://devicetree.org/schemas/nvmem/maxim,max77759-nvmem.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#

title: Maxim Integrated MAX77759 Non Volatile Memory

maintainers:
  - André Draszik <andre.draszik@linaro.org>

description: |
  This module is part of the MAX77759 PMIC. For additional information, see
  Documentation/devicetree/bindings/mfd/maxim,max77759.yaml.

  The MAX77759 is a PMIC integrating, amongst others, Non Volatile Memory
  (NVMEM) with 30 bytes of storage which can be used by software to store
  information or communicate with a boot loader.

properties:
  compatible:
    const: maxim,max77759-nvmem

  wp-gpios: false

required:
  - compatible

allOf:
  - $ref: nvmem.yaml#

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.