xref: /freebsd/sys/contrib/device-tree/Bindings/nvmem/layouts/nvmem-layout.yaml (revision f126890ac5386406dadf7c4cfa9566cbb56537c5)
18bab661aSEmmanuel Vadot# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
28bab661aSEmmanuel Vadot%YAML 1.2
38bab661aSEmmanuel Vadot---
48bab661aSEmmanuel Vadot$id: http://devicetree.org/schemas/nvmem/layouts/nvmem-layout.yaml#
58bab661aSEmmanuel Vadot$schema: http://devicetree.org/meta-schemas/core.yaml#
68bab661aSEmmanuel Vadot
78bab661aSEmmanuel Vadottitle: NVMEM (Non Volatile Memory) layouts
88bab661aSEmmanuel Vadot
98bab661aSEmmanuel Vadotmaintainers:
108bab661aSEmmanuel Vadot  - Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
118bab661aSEmmanuel Vadot  - Michael Walle <michael@walle.cc>
128bab661aSEmmanuel Vadot  - Miquel Raynal <miquel.raynal@bootlin.com>
138bab661aSEmmanuel Vadot
148bab661aSEmmanuel Vadotdescription: |
158bab661aSEmmanuel Vadot  Most NVMEM layouts are static and thus do not require additional description
168bab661aSEmmanuel Vadot  besides the bytes/bits offset and length. Other layouts can be less statically
178bab661aSEmmanuel Vadot  define and might require dynamic reading of the NVMEM device in order to
188bab661aSEmmanuel Vadot  perform their parsing. The nvmem-layout container is here to describe these.
198bab661aSEmmanuel Vadot
208bab661aSEmmanuel VadotoneOf:
21*f126890aSEmmanuel Vadot  - $ref: fixed-layout.yaml
228bab661aSEmmanuel Vadot  - $ref: kontron,sl28-vpd.yaml
238bab661aSEmmanuel Vadot  - $ref: onie,tlv-layout.yaml
248bab661aSEmmanuel Vadot
258bab661aSEmmanuel Vadotproperties:
268bab661aSEmmanuel Vadot  compatible: true
278bab661aSEmmanuel Vadot
288bab661aSEmmanuel Vadotrequired:
298bab661aSEmmanuel Vadot  - compatible
308bab661aSEmmanuel Vadot
318bab661aSEmmanuel VadotunevaluatedProperties: false
32