mirror of
https://github.com/ARM-software/arm-trusted-firmware.git
synced 2025-05-03 09:29:57 +00:00
4874793d2b
Complete the documentation with information on how to write a DTS for fconf. This patch adds the bindings information for dynamic configuration properties. Signed-off-by: Louis Mayencourt <louis.mayencourt@arm.com> Change-Id: Ic6d9f927df53bb87315c23ec5a8943d0c3258d45
32 lines
947 B
ReStructuredText
32 lines
947 B
ReStructuredText
DTB binding for FCONF properties
|
|
================================
|
|
|
|
This document describes the device tree format of |FCONF| properties. These
|
|
properties are not related to a specific platform and can be queried from
|
|
common code.
|
|
|
|
Dynamic configuration
|
|
~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
The |FCONF| framework expects a *dtb-registry* node with the following field:
|
|
|
|
- compatible [mandatory]
|
|
- value type: <string>
|
|
- Must be the string "fconf,dyn_cfg-dtb_registry".
|
|
|
|
Then a list of subnodes representing a configuration |DTB|, which can be used
|
|
by |FCONF|. Each subnode should be named according to the information it
|
|
contains, and must be formed with the following fields:
|
|
|
|
- load-address [mandatory]
|
|
- value type: <u64>
|
|
- Physical loading base address of the configuration.
|
|
|
|
- max-size [mandatory]
|
|
- value type: <u32>
|
|
- Maximum size of the configuration.
|
|
|
|
- id [mandatory]
|
|
- value type: <u32>
|
|
- Image ID of the configuration.
|
|
|