Lines Matching refs:be

10 platform specific data, allowing a "property" to be queried and a value
16 platform-defined tables. In the future, it may be provided as part of a device
26 Examples namespace can be:
33 Properties can be accessed with the ``FCONF_GET_PROPERTY(a,b,property)`` macro.
38 Properties composing the |FCONF| have to be stored in C structures. If
47 Hence each ``populate()`` function must be registered with a specific
59 Hence the ``populate()`` callback must be registered to the (|FCONF|) framework
61 would be called inside the generic ``fconf_populate()`` function during
73 Then, a wrapper has to be provided to match the ``FCONF_GET_PROPERTY()`` macro:
83 This second level wrapper can be used to remap the ``FCONF_GET_PROPERTY()`` to
93 The ``fconf_load_config(image_id)`` must be called to load fw_config and
94 tb_fw_config devices tree containing the properties' values. This must be done
104 can be used to fill the C data structure with the data from the config |DTB|.
114 sub-namespaces. The following concepts should be considered when adding new
122 across multiple platforms. They should be globally accessible and defined
123 inside the ``lib/fconf`` directory. The namespace must be chosen to reflect the
131 within the framework: Platform specific properties. They must be accessed only