| commit | 6cfd0d08a7083263102cb8e7a216f818a4c210eb | [log] [tgz] |
|---|---|---|
| author | Chau Ly <chaul@amperecomputing.com> | Thu Nov 30 03:41:37 2023 +0000 |
| committer | Chau Ly <chaul@amperecomputing.com> | Thu Nov 30 15:08:01 2023 +0000 |
| tree | 645826fb1e8f4816aca579111d8d91094dba8d6d | |
| parent | 22d5f74417f214e392b7c0db89e87ebaf3bbb808 [diff] |
Association between intrusion sensor and item Chassis intrusion sensor does not have the Sensor.Value interface to be legit into the "sensors" association with the chassis but there's a need to associate the sensor with the chassis that it is monitoring physical security state. This commit introduces the monitoring/monitored_by association between a chassis intrusion sensor and the inventory items that it is currently monitoring the physical security state. The association in this case requires the two endpoint interfaces of "xyz.openbmc_project.Chassis.Intrusion" and "xyz.openbmc_project.Inventory.Item". Signed-off-by: Chau Ly <chaul@amperecomputing.com> Change-Id: I1d110c8a83c5d264785ce30c363a654cbf711731
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