| commit | 7193e55f600537eaeeb5c4deaf53f9a3f88415c6 | [log] [tgz] |
|---|---|---|
| author | Kantesh Nagaradder <kantesh.nagaradder@ibm.com> | Tue Apr 25 12:09:50 2023 -0500 |
| committer | kantesh.nagaradder <kantesh.nagaradder@ibm.com> | Fri May 05 13:47:20 2023 +0000 |
| tree | 10458230abd2a6476c32c18fb58f4797f4e36816 | |
| parent | 47709f235791e9872c47b53ada844e5e58042e2a [diff] |
Add a new dbus interface for VSBK record This commit will add interface to support the new record(VSBK) and its keywords to store the system backplane's critical data as backup. The Bonnell BMC is embedded in the system backplane, so if either fails, the backplane should be replaced as a whole. Thus, we must backup the system backplane critical keywords on the VSBK record on the operator panel base EEPROM. Hence VSBK interface being added. Below is the introspect for VSBK: busctl introspect xyz.openbmc_project.Inventory.Manager /xyz/openbmc_project/inventory/system/chassis/motherboard/ base_op_panel_blyth com.ibm.ipzvpd.VSBK NAME TYPE SIGNATURE RESULT/VALUE FLAGS .BR property ay 2 83 48 emits-change writable .D0 property ay 1 1 emits-change writable .ES property ay 7 66 90 83 48 48 48 51 emits-change writable .F5 property ay 16 32 32 32 32 32 32 32 32 32 32 32 3... emits-change writable .F6 property ay 0 emits-change writable .FC property ay 8 50 69 52 65 45 48 48 49 emits-change writable .FV property ay 32 32 32 32 32 32 32 32 32 32 32 32 3... emits-change writable .LX property ay 8 49 0 4 1 0 48 0 123 emits-change writable .RB property ay 4 49 32 32 32 emits-change writable .RG property ay 4 0 0 0 0 emits-change writable .RT property ay 4 86 83 66 75 emits-change writable .SE property ay 7 66 48 48 48 48 48 51 emits-change writable .SU property ay 6 0 4 172 31 28 19 emits-change writable .TM property ay 8 57 48 50 56 45 50 49 66 emits-change writable .VZ property ay 2 48 50 emits-change writable .WN property ay 12 67 48 53 48 55 54 48 67 52 56 57 66 emits-change writable Change-Id: I333001f4317aa954dfd700dfa153133e179c4785 Signed-off-by: Kantesh Nagaradder <kantesh.nagaradder@ibm.com>
YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.
Before defining a new D-Bus interface or modifying an existing one, please read through the documented set of the common requirements and expectations.
This project can be built with meson. The typical meson workflow is: meson builddir && ninja -C builddir.
The meson files used to handle the YAML files are automatically generated and found under the gen subdirectory. When adding or removing YAML files, this must be regenerated. This can be done with the helper script found in the gen subdirectory: cd gen && ./regenerate-meson.
Only the xyz/openbmc_project and org/freedesktop interfaces are built by default. Other interfaces can be enabled by meson options:
-Ddata_com_ibm=true-Ddata_org_open_power=trueExample: meson builddir -Ddata_com_ibm=true && ninja -C builddir