diff options
author | Madhukar Pappireddy <madhukar.pappireddy@arm.com> | 2019-12-06 15:46:42 -0600 |
---|---|---|
committer | Madhukar Pappireddy <madhukar.pappireddy@arm.com> | 2020-03-11 10:19:21 -0500 |
commit | 25d740c45e14d42c9284ab1788a8d7b516608ece (patch) | |
tree | e0eb3eae765d72813ee49c15797cbae89d171e32 /bl31 | |
parent | f09852c97bc5de46d7322f2d1532fdddbd787043 (diff) | |
download | arm-trusted-firmware-25d740c45e14d42c9284ab1788a8d7b516608ece.tar.gz |
fconf: enhancements to firmware configuration framework
A populate() function essentially captures the value of a property,
defined by a platform, into a fconf related c structure. Such a
callback is usually platform specific and is associated to a specific
configuration source.
For example, a populate() function which captures the hardware topology
of the platform can only parse HW_CONFIG DTB. Hence each populator
function must be registered with a specific 'config_type' identifier.
It broadly represents a logical grouping of configuration properties
which is usually a device tree source file.
Example:
> TB_FW: properties related to trusted firmware such as IO policies,
base address of other DTBs, mbedtls heap info etc.
> HW_CONFIG: properties related to hardware configuration of the SoC
such as topology, GIC controller, PSCI hooks, CPU ID etc.
This patch modifies FCONF_REGISTER_POPULATOR macro and fconf_populate()
to register and invoke the appropriate callbacks selectively based on
configuration type.
Change-Id: I6f63b1fd7a8729c6c9137d5b63270af1857bb44a
Signed-off-by: Madhukar Pappireddy <madhukar.pappireddy@arm.com>
Diffstat (limited to 'bl31')
0 files changed, 0 insertions, 0 deletions