162306a36Sopenharmony_ci# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 262306a36Sopenharmony_ci%YAML 1.2 362306a36Sopenharmony_ci--- 462306a36Sopenharmony_ci$id: http://devicetree.org/schemas/nvmem/layouts/nvmem-layout.yaml# 562306a36Sopenharmony_ci$schema: http://devicetree.org/meta-schemas/core.yaml# 662306a36Sopenharmony_ci 762306a36Sopenharmony_cititle: NVMEM (Non Volatile Memory) layouts 862306a36Sopenharmony_ci 962306a36Sopenharmony_cimaintainers: 1062306a36Sopenharmony_ci - Srinivas Kandagatla <srinivas.kandagatla@linaro.org> 1162306a36Sopenharmony_ci - Michael Walle <michael@walle.cc> 1262306a36Sopenharmony_ci - Miquel Raynal <miquel.raynal@bootlin.com> 1362306a36Sopenharmony_ci 1462306a36Sopenharmony_cidescription: | 1562306a36Sopenharmony_ci Most NVMEM layouts are static and thus do not require additional description 1662306a36Sopenharmony_ci besides the bytes/bits offset and length. Other layouts can be less statically 1762306a36Sopenharmony_ci define and might require dynamic reading of the NVMEM device in order to 1862306a36Sopenharmony_ci perform their parsing. The nvmem-layout container is here to describe these. 1962306a36Sopenharmony_ci 2062306a36Sopenharmony_cioneOf: 2162306a36Sopenharmony_ci - $ref: fixed-layout.yaml 2262306a36Sopenharmony_ci - $ref: kontron,sl28-vpd.yaml 2362306a36Sopenharmony_ci - $ref: onie,tlv-layout.yaml 2462306a36Sopenharmony_ci 2562306a36Sopenharmony_ciproperties: 2662306a36Sopenharmony_ci compatible: true 2762306a36Sopenharmony_ci 2862306a36Sopenharmony_cirequired: 2962306a36Sopenharmony_ci - compatible 3062306a36Sopenharmony_ci 3162306a36Sopenharmony_ciunevaluatedProperties: false 32