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      If secondary-load-address is also provided (see below), then this is the
25      primary load address.
26
27- max-size [mandatory]
28    - value type: <u32>
29    - Maximum size of the configuration.
30
31- id [mandatory]
32    - value type: <u32>
33    - Image ID of the configuration.
34
35- secondary-load-address [optional]
36    - value type: <u64>
37    - A platform uses this physical address to copy the configuration to
38      another location during the boot-flow.
39
40--------------
41
42*Copyright (c) 2023, Arm Limited and Contributors. All rights reserved.*
43