xref: /linux/Documentation/devicetree/bindings/nvmem/layouts/nvmem-layout.yaml (revision 2fcea44e1ba16c55f4602948d2d43f3a365d6070)
127dfc44eSMiquel Raynal# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
227dfc44eSMiquel Raynal%YAML 1.2
327dfc44eSMiquel Raynal---
427dfc44eSMiquel Raynal$id: http://devicetree.org/schemas/nvmem/layouts/nvmem-layout.yaml#
527dfc44eSMiquel Raynal$schema: http://devicetree.org/meta-schemas/core.yaml#
627dfc44eSMiquel Raynal
727dfc44eSMiquel Raynaltitle: NVMEM (Non Volatile Memory) layouts
827dfc44eSMiquel Raynal
927dfc44eSMiquel Raynalmaintainers:
1027dfc44eSMiquel Raynal  - Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
1127dfc44eSMiquel Raynal  - Michael Walle <michael@walle.cc>
1227dfc44eSMiquel Raynal  - Miquel Raynal <miquel.raynal@bootlin.com>
1327dfc44eSMiquel Raynal
1427dfc44eSMiquel Raynaldescription: |
1527dfc44eSMiquel Raynal  Most NVMEM layouts are static and thus do not require additional description
1627dfc44eSMiquel Raynal  besides the bytes/bits offset and length. Other layouts can be less statically
1727dfc44eSMiquel Raynal  define and might require dynamic reading of the NVMEM device in order to
1827dfc44eSMiquel Raynal  perform their parsing. The nvmem-layout container is here to describe these.
1927dfc44eSMiquel Raynal
20e33cfae0SMichael WalleoneOf:
21bd912c99SRafał Miłecki  - $ref: fixed-layout.yaml
22e33cfae0SMichael Walle  - $ref: kontron,sl28-vpd.yaml
23ce9c0b06SMiquel Raynal  - $ref: onie,tlv-layout.yaml
24*2fcea44eSRafał Miłecki  - $ref: u-boot,env.yaml
25e33cfae0SMichael Walle
2627dfc44eSMiquel Raynalproperties:
2727dfc44eSMiquel Raynal  compatible: true
2827dfc44eSMiquel Raynal
2927dfc44eSMiquel Raynalrequired:
3027dfc44eSMiquel Raynal  - compatible
3127dfc44eSMiquel Raynal
3227dfc44eSMiquel RaynalunevaluatedProperties: false
33