Documentation/devicetree/bindings/nvmem/nxp,s32g-ocotp-nvmem.yaml
Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/nvmem/nxp,s32g-ocotp-nvmem.yaml
File Facts
- System
- Linux kernel
- Corpus path
Documentation/devicetree/bindings/nvmem/nxp,s32g-ocotp-nvmem.yaml- Extension
.yaml- Size
- 911 bytes
- Lines
- 46
- 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/nxp,s32g-ocotp-nvmem.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: NXP S32G OCOTP NVMEM driver
maintainers:
- Ciprian Costea <ciprianmarian.costea@nxp.com>
description:
The drivers provides an interface to access One Time
Programmable memory pages, such as TMU fuse values.
properties:
compatible:
oneOf:
- enum:
- nxp,s32g2-ocotp
- items:
- enum:
- nxp,s32g3-ocotp
- nxp,s32r45-ocotp
- const: nxp,s32g2-ocotp
reg:
maxItems: 1
required:
- compatible
- reg
unevaluatedProperties: false
allOf:
- $ref: nvmem.yaml#
examples:
- |
nvmem@400a4000 {
compatible = "nxp,s32g2-ocotp";
reg = <0x400a4000 0x400>;
#address-cells = <1>;
#size-cells = <1>;
};
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.