Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-dbus-interfaces / b235159e0acc9943bc5f4e428ba6536f2e3cb621
commitb235159e0acc9943bc5f4e428ba6536f2e3cb621[log] [tgz]
authorPrithvi Pai <ppai@nvidia.com>Tue Feb 04 16:25:37 2025 +0530
committerPrithvi Pai <ppai@nvidia.com>Wed Feb 05 14:24:05 2025 +0530
tree6b276e3d2c63d397340523d390b951889f4a2aef
parent0e78828ce927548b4dd679e06fdaf2f294983289 [diff]
Add UEFI SecureBoot Setting related interfaces

Redfish added schema for SecureBoot, which contains UEFI Secure Boot
related information and represents properties for managing the UEFI
Secure Boot functionality of a system. It would be useful to add
remote UEFI secure boot configuration support which provides unified
interface for remote uefi secure boot configuration in data centers,
and provide a generic implementation for the remote management of
uefi secure boot.

Redfish Schema -
https://redfish.dmtf.org/schemas/v1/SecureBoot.v1_1_2.json

BIOSConfig.SecureBoot exposes three properties:
1) Enable: An indication of whether UEFI Secure Boot is enabled.
2) Current Boot: An indication of UEFI Secure Boot state during the
   current boot cycle
3) Mode: Indicates the current UEFI Secure Boot mode, as defined in
   the UEFI Specification.

Change-Id: I1a345c2efcdd42be9920b509649621157b88775a
Signed-off-by: Prithvi Pai <ppai@nvidia.com>
3 files changed
tree: 6b276e3d2c63d397340523d390b951889f4a2aef
  1. gen/
  2. registry/
  3. subprojects/
  4. yaml/
  5. .gitignore
  6. .markdownlint.yaml
  7. .prettierrc.yaml
  8. .shellcheck
  9. LICENSE
  10. meson.build
  11. meson.options
  12. OWNERS
  13. README.md
  14. requirements.md
README.md

phosphor-dbus-interfaces

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.

Building

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.

Configuration

Only the xyz/openbmc_project and org/freedesktop interfaces are built by default. Other interfaces can be enabled by meson options:

  • com/ibm - -Ddata_com_ibm=true
  • org/open_power - -Ddata_org_open_power=true

Example: meson builddir -Ddata_com_ibm=true && ninja -C builddir

References