Switch to Use phosphor-dbus-interface defined constants

We are redefining a lot of the constants which are already
defined in the phosphor-dbus-interface auto-generated
headers. This change switches

Switch to Use phosphor-dbus-interface defined constants

We are redefining a lot of the constants which are already
defined in the phosphor-dbus-interface auto-generated
headers. This change switches the code to use those instead
of allowing compile time definition of those.

Allowing for compile time definition would probably break
clients who are not aware of the new paths anyway.

Tested by build a harma image and loading in qemu to test
the added interfaces are unchanged.
```
busctl introspect xyz.openbmc_project.State.BMC \
/xyz/openbmc_project/state/bmc0
busctl introspect xyz.openbmc_project.State.Host \
/xyz/openbmc_project/state/host0
busctl introspect xyz.openbmc_project.State.Chassis \
/xyz/openbmc_project/state/chassis0
```

Change-Id: Ib4c77d2789c13f509b75a2b1837ea454e53e8ae9
Signed-off-by: Amithash Prasasd <amithash@meta.com>

show more ...

host-gpios: enable by default

We should tend to have a default meson.option policy that enables as
much code as possible so that it is covered by CI. The `host-gpios`
option was disabled and we did

host-gpios: enable by default

We should tend to have a default meson.option policy that enables as
much code as possible so that it is covered by CI. The `host-gpios`
option was disabled and we did not have a PACKAGECONFIG for it in
openbmc/openbmc. With Ia737a5645dcf472efdc75a9af7260eff60ef90ed, I
have added a PACKAGECONFIG for this setting and it will be disabled by
default in our Yocto builds. Enable it here to regain the CI coverage.

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I952095a294059a27ae1066d6abdc9abcc5ba709a

show more ...

Add option to enable/disable forced warm reboots

Some OpenBMC systems don't support a forced warm reboot. Provide a
compile option to enable/disable.

Tested:
- Confirmed that if feature is disabled

Add option to enable/disable forced warm reboots

Some OpenBMC systems don't support a forced warm reboot. Provide a
compile option to enable/disable.

Tested:
- Confirmed that if feature is disabled, then AllowedHostTransitions did
not have ForceWarmReboot option.

Change-Id: I207b8fa7e3f60efbf406397ff4df980a5d2677ed
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>

show more ...

meson.options: Fix some warnings

Warning messages:
```
meson.options:129: WARNING: Project targets '>=1.1.1' but uses
feature deprecated since '1.1.0': "boolean option" keyword argument
"value" of t

meson.options: Fix some warnings

Warning messages:
```
meson.options:129: WARNING: Project targets '>=1.1.1' but uses
feature deprecated since '1.1.0': "boolean option" keyword argument
"value" of type str. use a boolean, not a string

meson.options:144: WARNING: Project targets '>=1.1.1' but uses
feature deprecated since '1.1.0': "boolean option" keyword argument
"value" of type str. use a boolean, not a string
```

Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: I69f41cca5cc792e89306531d380d52b19ec41775

show more ...

meson_options.txt: Support for reading options from meson.options

Support has been added for reading options from meson.options instead
of meson_options.txt[1]. These are equivalent, but not using t

meson_options.txt: Support for reading options from meson.options

Support has been added for reading options from meson.options instead
of meson_options.txt[1]. These are equivalent, but not using the .txt
extension for a build file has a few advantages, chief among them
many tools and text editors expect a file with the .txt extension to
be plain text files, not build scripts.

[1] https://mesonbuild.com/Release-notes-for-1-1-0.html#support-for-reading-options-from-mesonoptions

Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: I705afd61af8cfcad6e66008ff45f285fa99ec78b

show more ...