1DTB binding for FCONF properties
2================================
3
4This document describes the device tree format of |FCONF| properties. These
5properties are not related to a specific platform and can be queried from
6common code.
7
8Dynamic configuration
9~~~~~~~~~~~~~~~~~~~~~
10
11The |FCONF| framework expects a *dtb-registry* node with the following field:
12
13- compatible [mandatory]
14   - value type: <string>
15   - Must be the string "fconf,dyn_cfg-dtb_registry".
16
17Then a list of subnodes representing a configuration |DTB|, which can be used
18by |FCONF|. Each subnode should be named according to the information it
19contains, and must be formed with the following fields:
20
21- load-address [mandatory]
22    - value type: <u64>
23    - Physical loading base address of the configuration.
24
25- max-size [mandatory]
26    - value type: <u32>
27    - Maximum size of the configuration.
28
29- id [mandatory]
30    - value type: <u32>
31    - Image ID of the configuration.
32
33- ns-load-address [optional]
34    - value type: <u64>
35    - Physical loading base address of the configuration in the non-secure
36      memory.
37      Only needed by those configuration files which require being loaded
38      in secure memory (at load-address) as well as in non-secure memory
39      e.g. HW_CONFIG
40