| commit | 393c0fade4690d37e7dd7227730b2bcaef9214db | [log] [tgz] |
|---|---|---|
| author | Anupama B R <anupama.b.r1@ibm.com> | Mon Apr 07 05:14:31 2025 -0500 |
| committer | SunnySrivastava <sunnsr25@in.ibm.com> | Fri May 02 06:57:09 2025 +0000 |
| tree | d138aa177eb07f359ea88f711c3d9eb2f0c50092 | |
| parent | 96ebe968e520b95701dc0f2a49ffa0b97c9bcb32 [diff] |
Correlated JSON config file for DBus properties
This commit adds the new JSON file, the file contains set of DBus
properties which are correlated with properties from other interfaces.
This correlated property information is used for syncing DBus property
value, where the same property(data) can be reflected data under
different interface(s) property.
The correlated JSON has the following format,
```
{
"<dbus_service_name>": {
"<src_interface_name>": {
"<src_property_name>": {
"pathsPair": {
"<src_inventory_object_path>": {
"destinationInventoryPath": ["<dst_inv_path>", "<dst_inv_path>"],
"interfaces": {
"<dst_interface_name>": "<dst_interface_name>"
}
}
}//paths pair end
"defaultInterfaces": {
"<dst_interface_name>": "<dst_roperty_name>"
}
}//src property end
}//src interface end
}//dbus service end
}//end
```
More information about this correlation property JSON can be found
in README file under the doc folder path.
Change-Id: I269f1ed0d7a0f63f9ef8d89328b4139726096e51
Signed-off-by: Anupama B R <anupama.b.r1@ibm.com>
This repository hosts code for OpenPower and IBM IPZ format VPD parsers. Both OpenPower VPD and IPZ VPD formats are structured binaries that consist of records and keywords. A record is a collection of multiple keywords. More information about the format can be found here.
The repository consists of two distinct applications, which are:
This is a build-time YAML driven application that parses the OpenPower VPD format and uses the YAML configuration (see extra-properties-example.yaml and writefru.yaml) to determine:
The application instance must be passed in the file path to the VPD (this can, for example, be a sysfs path exposed by the EEPROM device driver) and also the D-Bus object path(s) that EEPROM data needs to be published under.
This parser is can be built by passing in the --enable-ibm-parser configure option. This parser differs from the OpenPower VPD parser in the following ways:
# and are > 255 bytes in length).Making the application runtime JSON driven allows us to support multiple systems (with different FRU configurations) to be supported in a single code image as well as making the application more flexible for future improvements.