HardwareIsolation: Added the "Entry" interface
In an OpenPOWER based system, a user or an application (in the
error path if the hardware is faulty) can isolate hardware and
the respective isolated hardware part will be ignored to init
during the next boot of the host.
This entry interface will be used to maintain the isolated
hardware information.
Please refer https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/27804
to get more details of hardware isolation.
Signed-off-by: Ramesh Iyyar <rameshi1@in.ibm.com>
Change-Id: I61cfdc757dd281e8b0b746304f7e5eafd6ef421d
diff --git a/gen/xyz/openbmc_project/HardwareIsolation/Entry/meson.build b/gen/xyz/openbmc_project/HardwareIsolation/Entry/meson.build
new file mode 100644
index 0000000..ff63673
--- /dev/null
+++ b/gen/xyz/openbmc_project/HardwareIsolation/Entry/meson.build
@@ -0,0 +1,14 @@
+# Generated file; do not modify.
+generated_sources += custom_target(
+ 'xyz/openbmc_project/HardwareIsolation/Entry__cpp'.underscorify(),
+ input: [ '../../../../../yaml/xyz/openbmc_project/HardwareIsolation/Entry.interface.yaml', ],
+ output: [ 'server.cpp', 'server.hpp', 'client.hpp', ],
+ command: [
+ sdbuspp_gen_meson_prog, '--command', 'cpp',
+ '--output', meson.current_build_dir(),
+ '--tool', sdbusplusplus_prog,
+ '--directory', meson.current_source_dir() / '../../../../../yaml',
+ 'xyz/openbmc_project/HardwareIsolation/Entry',
+ ],
+)
+