com: meta: Add OEM "UnifiedSEL" event

Existing Meta BIOS create a "UnifiedSEL" structure for reporting
problems detected by the Host. These are sent via either IPMI
or PLDM messages. Create a new-

com: meta: Add OEM "UnifiedSEL" event

Existing Meta BIOS create a "UnifiedSEL" structure for reporting
problems detected by the Host. These are sent via either IPMI
or PLDM messages. Create a new-style event for these so that
they can be exposed via Redfish.

Change-Id: I155e90c75f72f1b061646453f13cdc76fee56532
Signed-off-by: Amithash Prasad <amithash@meta.com>
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>

show more ...

Thermal: Add events for temperature based faults

Define two events DeviceOverOperatingTemperature and
DeviceOverOperatingTemperatureFault to indicate device
thermal overrun events to provide informa

Thermal: Add events for temperature based faults

Define two events DeviceOverOperatingTemperature and
DeviceOverOperatingTemperatureFault to indicate device
thermal overrun events to provide information of their
x86 equivalent PROCHOT and THERMTRIP.

Change-Id: Iee45c6cdf6063c886043fe5e5b5a4ef8f434f6dd
Signed-off-by: Amithash Prasad <amithash@meta.com>

show more ...

registry: add registry_target to the external dependency

When PDI is used as a subproject, we need some dependency that indicates
the registry is populated. Add the internal build rule to the prima

registry: add registry_target to the external dependency

When PDI is used as a subproject, we need some dependency that indicates
the registry is populated. Add the internal build rule to the primary
external dependency so any dependency on PDI satisfies the registry
population.

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

show more ...

LockOut: add events for Lock-Out / Tag-Out style devices

It is common practice for dangerous machinery to have a Lock-Out-Tag-Out
process (LOTO) to prevent the system from operating while the machin

LockOut: add events for Lock-Out / Tag-Out style devices

It is common practice for dangerous machinery to have a Lock-Out-Tag-Out
process (LOTO) to prevent the system from operating while the machine
is being worked on. Servers may have Lock-Out style devices to prevent
either power or liquid cooling operations while the system is in
service. For example, a switch may disable all liquid cooling pumps so
that the coolant does not pump onto the floor while coolant lines are
being repaired.

Add events to indicate the state of a Lock-Out style device.

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

show more ...

Power: add events for power rail and voltage regulator faults

Define two events: PowerRailFault and VoltageRegulatorFault.
These can be used for power rail / pgood failure and voltage regulator
repo

Power: add events for power rail and voltage regulator faults

Define two events: PowerRailFault and VoltageRegulatorFault.
These can be used for power rail / pgood failure and voltage regulator
reported failures respectively.

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

show more ...

SMC: add events for Satellite Management Controllers

Add events to report issues with attached SMCs, such as
heartbeat failures or inability to communicate. This is
reported as a generic event (SMC

SMC: add events for Satellite Management Controllers

Add events to report issues with attached SMCs, such as
heartbeat failures or inability to communicate. This is
reported as a generic event (SMCFailed), which is most
likely useful enough for external reporting and fault isolation,
but includes a field for additional debug data of the failure
type.

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

show more ...

meson: reformat with meson formatter

Apply the `meson format` results.

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

State: Add BMC redundancy interface

Define an interface in support of redundant BMC functionality as
mentioned in the design doc
https://gerrit.openbmc.org/c/openbmc/docs/+/70233. To start with, it

State: Add BMC redundancy interface

Define an interface in support of redundant BMC functionality as
mentioned in the design doc
https://gerrit.openbmc.org/c/openbmc/docs/+/70233. To start with, it
defines the Role and RedundancyEnabled properties.

With this usage one BMC is considered the active BMC, and the other is
the passive. There will be a new application running on each BMC that
hosts this interface.

This implementation is not related to the one that uses the
xyz.openbmc_project.State.BMCRedundancy interface, of which there
doesn't appear to be any upstream uses of.

Change-Id: I6415175bbee03f6c07b14e1db1ee0082bd1724ed
Signed-off-by: Matt Spinler <spinler@us.ibm.com>

show more ...

Update GetUserInfo to return TOTPSecretkeyRequired

This commit updates GetUserInfo to return TOTPSecretkeyRequired

Change-Id: I6a37e65a9746b16947ad16f69d1bf459b8b8eeac
Signed-off-by: Ravi Teja <rav

Update GetUserInfo to return TOTPSecretkeyRequired

This commit updates GetUserInfo to return TOTPSecretkeyRequired

Change-Id: I6a37e65a9746b16947ad16f69d1bf459b8b8eeac
Signed-off-by: Ravi Teja <raviteja28031990@gmail.com>

show more ...

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 fu

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>

show more ...

regenerate-meson: enable meson formatting

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

add the redfish mapping for leak detector events

DTMF has released the Redfish Message Registry [1] with Leak events, so
update the related redfish mapping for Leak Detector events. Also drop
the en

add the redfish mapping for leak detector events

DTMF has released the Redfish Message Registry [1] with Leak events, so
update the related redfish mapping for Leak Detector events. Also drop
the en section as this will come from standard redfish definitions.

References:
[1] https://www.dmtf.org/sites/default/files/standards/documents/DSP2065_2024.4.pdf

Change-Id: I8be7314ba7c21da6a576668e1e29dbb3d7b7913c
Signed-off-by: Jagpal Singh Gill <paligill@gmail.com>

show more ...

add events for leak detector group

Add the leak events to be reported for leak detector groups. Currently,
there is no standard redfish messages registry for these events, hence
adding them to openB

add events for leak detector group

Add the leak events to be reported for leak detector groups. Currently,
there is no standard redfish messages registry for these events, hence
adding them to openBMC namespace.
```
https://redfishforum.com/thread/1074/redfish-message-registry-leakdetection
```

Change-Id: I83aa5589426726f537c768d9ac05aa42a065abba
Signed-off-by: Jagpal Singh Gill <paligill@gmail.com>

show more ...

leak detection: add support for detector groups

Add support for leak detector groups alongwith appropriate association
to the leak detectors. For more details on leak detector groups refer to
- http

leak detection: add support for detector groups

Add support for leak detector groups alongwith appropriate association
to the leak detectors. For more details on leak detector groups refer to
- https://redfish.dmtf.org/schemas/v1/LeakDetection.v1_1_0.json.

Change-Id: I6f31adf2d806ef4f0c7dade94432581f2b10c8a3
Signed-off-by: Jagpal Singh Gill <paligill@gmail.com>

show more ...

add EM configuration for GPIOLeakDetector

Add entity manager configuration for GPIOLeakDetector based on
https://gerrit.openbmc.org/c/openbmc/entity-manager/+/75734.

Change-Id: I366700a523620b8f891

add EM configuration for GPIOLeakDetector

Add entity manager configuration for GPIOLeakDetector based on
https://gerrit.openbmc.org/c/openbmc/entity-manager/+/75734.

Change-Id: I366700a523620b8f891298f544ad46ba175a1d14
Signed-off-by: Jagpal Singh Gill <paligill@gmail.com>

show more ...

Configuration: Add GPIODeviceDetect interface

configuration interface for gpio-presence daemon.

As defined in the design document for gpio hw inventory [1]

References:
[1] https://github.com/openb

Configuration: Add GPIODeviceDetect interface

configuration interface for gpio-presence daemon.

As defined in the design document for gpio hw inventory [1]

References:
[1] https://github.com/openbmc/docs/blob/abbf7355231fbd9d5231e136780c167f2a89494e/designs/inventory/gpio-based-hardware-inventory.md

Change-Id: I01b002623125de258366779a656592c0840a6d89
Signed-off-by: Alexander Hansen <alexander.hansen@9elements.com>

show more ...

Inventory.Source: Add DevicePresence interface

Dbus interface needed for the gpio hw inventory design [1].

This interface allows to use the presence of any device to be used as an
inventory source.

Inventory.Source: Add DevicePresence interface

Dbus interface needed for the gpio hw inventory design [1].

This interface allows to use the presence of any device to be used as an
inventory source. The motivating use-case is for hardware detected via
gpios.

[1] https://github.com/openbmc/docs/blob/abbf7355231fbd9d5231e136780c167f2a89494e/designs/inventory/gpio-based-hardware-inventory.md

Change-Id: I2d4a80498acbca46c834d2c3f093098098415a35
Signed-off-by: Alexander Hansen <alexander.hansen@9elements.com>

show more ...

Add new interface to define sensor purpose

A chassis can have a sensor which tracks the total power consumption.
Clients such as bmcweb need a programmatic approach to finding the
unique sensor from

Add new interface to define sensor purpose

A chassis can have a sensor which tracks the total power consumption.
Clients such as bmcweb need a programmatic approach to finding the
unique sensor from the chassis.

A design discussion [1] in development channel of Discord settled on the
following approach:
- Define a D-Bus interface for defining a special purpose for a
sensor.
- Use the existing all_sensors/chassis association to connect the
sensor to its Chassis.
- Clients such as bmcweb use object mapper to find all_sensors
associated with the Chassis. They then filter to
find the sensor implementing the specific purpose required.

This initial implementation only defines a single special purpose. The
expectation is others will be added as needed in the future.

The openpower-occ-control repo implemented a total_power association.[2]
This will be modified to implement this new interface on the total_power
sensor.

There is a commit for bmcweb which will be modified to use this new
approach for finding the total_power sensor.[3]

Note: There is technical debt to convert all_sensors/chassis
associations to use the monitoring/monitored_by association instead.[4]
That change would also need to convert the association used to find
objects implementing this interface.

[1] https://discord.com/channels/775381525260664832/867820390406422538/1326612654852280433
[2] https://gerrit.openbmc.org/c/openbmc/openpower-occ-control/+/75572
[3] https://gerrit.openbmc.org/c/openbmc/bmcweb/+/57717
[4] https://discord.com/channels/775381525260664832/867820390406422538/1326609419022372916

Change-Id: Ic8b509c9b2b17e823243f7b784ef941ec461cddb
Signed-off-by: Janet Adkins <janeta@us.ibm.com>

show more ...

Add SecretKeyRequired D-bus method

This commit adds SecretKeyRequired D-bus method to Manager
interface.
bmcweb codes needs to query generate secret key required for a given
user, local users on BMC

Add SecretKeyRequired D-bus method

This commit adds SecretKeyRequired D-bus method to Manager
interface.
bmcweb codes needs to query generate secret key required for a given
user, local users on BMC have d-bus objects for each user but LDAP
users does not have D-bus objects, so this d-bus method helps identify
whether generate secret key required for user local and remote LDAP
users

Change-Id: Ib522802c395d61f0c3e9fbf84fc6a399a66a3afa
Signed-off-by: Ravi Teja <raviteja28031990@gmail.com>

show more ...

Break apart trigger interface

Having this large type creates confusion for translation. Splitting
this parameter into two fields allows us to remove the variant property
altogether, and allows spli

Break apart trigger interface

Having this large type creates confusion for translation. Splitting
this parameter into two fields allows us to remove the variant property
altogether, and allows splitting the rules for each type into their own
description.

The only users of this are bmcweb and telemetry, both of which have
patches up to effect this change under the same topic. Testing in those
patches.

Change-Id: I51a1dd3fe0619aa7a75f92764875552feda01a92
Signed-off-by: Ed Tanous <ed@tanous.net>

show more ...

meson: remove pc_sysroot from registry_dir

The pkg-config variable 'registry_dir' is intended to represent where
the Redfish Message Registries will be installed. When cross-compiling,
bitbake prov

meson: remove pc_sysroot from registry_dir

The pkg-config variable 'registry_dir' is intended to represent where
the Redfish Message Registries will be installed. When cross-compiling,
bitbake provides meson with the `sys_root` as somewhere in the bitbake
build tree, which meson then uses as an argument to pkg-config, which
uses it as the `${pc_sysrootdir}` value. If we use `${pc_sysrootdir}`
in the pkg-config file, it ends up being expanded as the cross-compile
sysroot and not the final location. Remove the `${pc_sysroot}` portion
so that the value points at the final location.

There is an argument that it is useful to have it contain the sysroot
location during the compilation state. Some repositories _could_
choose to process the registry during build time, like phosphor-logging
does with the `yamldir` variable. However, cross-compile environments
provide an alternative way to get the sysroot, such as
`meson.get_external_property('sys_root')`. Having it already included
in the pkg-config makes it harder to get the install location (since
you have to subtract the path, rather than add it).

Arguably, `yamldir` should also be adjusted but that will require
changes in, at least, phosphor-logging that should be made separately.

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

show more ...

build: support registry generation

sdbus++-gen-meson version 10 adds support for redfish registry
generation and greatly simplifies the install directives.

Regenerate the YAML meson files and modif

build: support registry generation

sdbus++-gen-meson version 10 adds support for redfish registry
generation and greatly simplifies the install directives.

Regenerate the YAML meson files and modify the base meson.build
as necessary. Also, format meson.build with `meson format`.

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

show more ...

Remove vim mode line

It isn't necessary to store editor settings in source files.

Change-Id: I9c5c60150f34b2e5ac2071ca4a67e0610c5885ec
Signed-off-by: Matt Spinler <spinler@us.ibm.com>

NIC: Add new NIC dump entry interface

NIC is a new type of dump in openbmc/phosphor-debug-collector.

Change-Id: Ie9ae8fa754d3b5d57b1e008394491fa1ef80012e
Signed-off-by: eddylu <puzzy8338@gmail.com>

Logging.Entry: switch 'AdditionalData' to dict of metadata

All client users of AdditionalData have moved to AdditionalData2,
which is already a dict. Switch AdditionalData to be a dict as
the next

Logging.Entry: switch 'AdditionalData' to dict of metadata

All client users of AdditionalData have moved to AdditionalData2,
which is already a dict. Switch AdditionalData to be a dict as
the next part of the migration.

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

show more ...