Add Hoth interface

Create a new google namespace and add the Hoth interface to this
namespace.

Signed-off-by: John Edward Broadbent <jebr@google.com>
Change-Id: I001dc34ef081885b6094d3d1aab578b0d88

Add Hoth interface

Create a new google namespace and add the Hoth interface to this
namespace.

Signed-off-by: John Edward Broadbent <jebr@google.com>
Change-Id: I001dc34ef081885b6094d3d1aab578b0d882b53a

show more ...

Certs: add Interfaces for bulk installation and replacement

The corresponding design is in
https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/49317.

Signed-off-by: Nan Zhou <nanzhoumails@gmail.com

Certs: add Interfaces for bulk installation and replacement

The corresponding design is in
https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/49317.

Signed-off-by: Nan Zhou <nanzhoumails@gmail.com>
Change-Id: I969090951a2da59c67cea232f212e664a193425c

show more ...

AccountPolicy: InvalidArgument for min password

Values less than the pre-defined lower limit are not allowed so trying
to set them should result in a distinct error; add InvalidArgument for
that cas

AccountPolicy: InvalidArgument for min password

Values less than the pre-defined lower limit are not allowed so trying
to set them should result in a distinct error; add InvalidArgument for
that case.

Signed-off-by: Paul Fertser <fercerpav@gmail.com>
Change-Id: I1c589e2ce8a2823564034eb370f571a9663650f6

show more ...

power-recovery: add PowerRestoreDelay to RestorePolicy

This commit introduce new property to set delay before invoke Power
Restore operations after system startup. This delay supposed to be
calculat

power-recovery: add PowerRestoreDelay to RestorePolicy

This commit introduce new property to set delay before invoke Power
Restore operations after system startup. This delay supposed to be
calculated from BMC power up and limited by BMC software boot time.

x86-power-control used to use undocumented interface
`xyz.openbmc_project.Control.Power.RestoreDelay` to represent this
property, but this looks good fit to
`xyz.openbmc_project.Control.Power.RestorePolicy`.

Signed-off-by: Andrei Kartashev <a.kartashev@yadro.com>
Change-Id: I81f35bf1555ccba7de9db6c2455a4ff54cb72f81

show more ...

Add setMode method to OCC PassThrough interface

This will allow BMC root users to set any Power Modes including OEM modes
that are not available via Redfish.

Tested on Rainier and Everest systems

Add setMode method to OCC PassThrough interface

This will allow BMC root users to set any Power Modes including OEM modes
that are not available via Redfish.

Tested on Rainier and Everest systems

Change-Id: I5dd6be67120ab14caa1b3a972eb2571e3c821f7d
Signed-off-by: Chris Cain <cjcain@us.ibm.com>

show more ...

bmc-reboot: add pinhole reset reason

Some systems have a physical mechanism on them to force a reboot of the
BMC. One common mechanism for this is a pinhole. The user utilizes a
round, thin piece of

bmc-reboot: add pinhole reset reason

Some systems have a physical mechanism on them to force a reboot of the
BMC. One common mechanism for this is a pinhole. The user utilizes a
round, thin piece of metal (commonly a paper clip) to trigger this
reset.

The use of the pinhole reset is usually utilized to force a reboot of
an unresponsive BMC. BMC firmware, when it comes back from the reboot,
may want to do some special handling for this scenario.

Some systems, like the IBM p10bmc machines, have some logic in the
hardware to set a GPIO so that BMC firmware will have a mechanism to
know if the reboot cause was the result of a pinhole reset. IBM systems
would like to add some software logic around this. For example, if a
pinhole reset was done, the firmware will not run its auto power on
functions. If a user has force reset a system, they do not want firmware
trying to auto power on the machine.

The design on this can be found here:
https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/47816

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

show more ...

power-recovery: introduce CurrentPowerStatus to chassis

The power coming into a chassis can have its own status. For example, if
power has been lost (blackout) but the system has an uninterruptible

power-recovery: introduce CurrentPowerStatus to chassis

The power coming into a chassis can have its own status. For example, if
power has been lost (blackout) but the system has an uninterruptible
power supply(UPS) connected, then chassis power could still be on but
its important to provide the fact that the system is running off of a
UPS to other BMC software.

For example, IBM has a policy that it will allow a system to remain on
if it is already on when a blackout or brownout occurs (and running on
a UPS), but it will not allow a user to power a system on if in one of
these conditions. IBM will also not allow a system to power on until
a UPS is fully charged.

The design for this can be found over in the following series:
https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/48210

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

show more ...

sensor: add relative humidity

Change-Id: I84f37194adbcaf99b4c426a8d51afc738bd6a799

sensor: sort units and document all types

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

Update power cap interface

Add Min, Max properties which can be used by phosphor-host-ipmid

Signed-off-by: Gaurav Gandhi <gauravgandhi@google.com>
Change-Id: Ib1622b53c93fa33a050bfd2db954c3d5619f0b

Update power cap interface

Add Min, Max properties which can be used by phosphor-host-ipmid

Signed-off-by: Gaurav Gandhi <gauravgandhi@google.com>
Change-Id: Ib1622b53c93fa33a050bfd2db954c3d5619f0bb4

show more ...

Add D-Bus interface for a logical volume

Add an initial D-Bus interface for a logical volume, which will be used
for eStoraged. It includes the following methods: FormatLuks, Lock,
Unlock, and Chang

Add D-Bus interface for a logical volume

Add an initial D-Bus interface for a logical volume, which will be used
for eStoraged. It includes the following methods: FormatLuks, Lock,
Unlock, and ChangePassword.

The design doc for eStoraged can be found here:
https://github.com/openbmc/docs/blob/master/designs/estoraged.md

Signed-off-by: John Wedig <johnwedig@google.com>
Signed-off-by: John Edward Broadbent <jebr@google.com>
Change-Id: I7975056e52901a82b36933b51fb3eea112818385

show more ...

Add interface for sending raw PECI commands

This adds a D-Bus interface to send raw PECI commands to the
CPU.

Change-Id: I37c8c0b9fc713705b3afc81adca22ca313e91701
Signed-off-by: Jason M. Bills <jas

Add interface for sending raw PECI commands

This adds a D-Bus interface to send raw PECI commands to the
CPU.

Change-Id: I37c8c0b9fc713705b3afc81adca22ca313e91701
Signed-off-by: Jason M. Bills <jason.m.bills@linux.intel.com>

show more ...

Add UPower Device interface

Add a YAML description of the UPower Device interface defined at
https://upower.freedesktop.org/docs/Device.html

Signed-off-by: Shawn McCarney <shawnmm@us.ibm.com>
Chang

Add UPower Device interface

Add a YAML description of the UPower Device interface defined at
https://upower.freedesktop.org/docs/Device.html

Signed-off-by: Shawn McCarney <shawnmm@us.ibm.com>
Change-Id: Ib70d6525b913cf06da4e93a53e332487126f1db0

show more ...

software: leverage Compatible strings

Enhance the software design to leverage Inventory.Decorator.Compatible
strings for associating software images to system elements where the
image can be applied

software: leverage Compatible strings

Enhance the software design to leverage Inventory.Decorator.Compatible
strings for associating software images to system elements where the
image can be applied.

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

show more ...

software: define multi-slot/multi-device update

Enhance the Software update design to be capable of handling updates to
multiple devices of the same type or a single device with multiple
update loca

software: define multi-slot/multi-device update

Enhance the Software update design to be capable of handling updates to
multiple devices of the same type or a single device with multiple
update locations.

Signed-off-by: Carlos J. Mazieri <carlos.mazieri@hcl.com>
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I58008fddb532f4bba4c77b4a8228b8df2abec164

show more ...

software: remove old TODO

The software design had a reference to a "TODO" pertaining to the old
REST API, which has been present for years and unresolved. Since the
REsT API is deprecated anyhow an

software: remove old TODO

The software design had a reference to a "TODO" pertaining to the old
REST API, which has been present for years and unresolved. Since the
REsT API is deprecated anyhow and issues should be tracked elsewhere,
remove this TODO.

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

show more ...

host-state: introduce new host crash restart reason

In situations where the host firmware crashes, and BMC firmware detects
it, the BMC will attempt to recover by initiating a reboot of the host
fir

host-state: introduce new host crash restart reason

In situations where the host firmware crashes, and BMC firmware detects
it, the BMC will attempt to recover by initiating a reboot of the host
firmware a certain amount of times.

On IBM systems, the host needs to know when a crash is the reason for a
boot. This property will be utilized by the host communication firmware
to tell them.

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

show more ...

host-state: introduce new scheduled power on reason

The xyz.openbmc_project.State.ScheduledHostTransition interface is
utilized to schedule a host transition at some point in the future. Add
this as

host-state: introduce new scheduled power on reason

The xyz.openbmc_project.State.ScheduledHostTransition interface is
utilized to schedule a host transition at some point in the future. Add
this as a potential reason for the host RestartCause property.

On IBM systems, the host needs to know when a scheduled transition is
the reason for a boot. This property will be utilized by the host
communication firmware to tell them.

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

show more ...

CpuCore: Update Microcode type to uint

Match the type with Cpu.interface.yaml with the change that went in:
https://gerrit.openbmc-project.xyz/47987

Signed-off-by: Brandon Kim <brandonkim@google.co

CpuCore: Update Microcode type to uint

Match the type with Cpu.interface.yaml with the change that went in:
https://gerrit.openbmc-project.xyz/47987

Signed-off-by: Brandon Kim <brandonkim@google.com>
Change-Id: I97401a8325c939ec1f69a6e59716fa9bc4dfd45e

show more ...

Software: Settings: add setting to Software interface

Added the xyz.openbmc_project.Software.Settings interface to provide
the user with some control over the Software it manages.

Currently, it onl

Software: Settings: add setting to Software interface

Added the xyz.openbmc_project.Software.Settings interface to provide
the user with some control over the Software it manages.

Currently, it only has `WriteProtected` that indicate if the software is
writeable or not.

The settings are enforced by the service that manage the property.

Change-Id: I726c247428b4e1c8b1fe9cf66554ef272bbcd231
Signed-off-by: Willy Tu <wltu@google.com>

show more ...

Cpu: Update Step and Microcode type to uint

Looking at the Redfish Resource and Schema guide:
https://www.dmtf.org/sites/default/files/standards/documents/DSP2046_2021.2.pdf

Section 6.86.6 at page

Cpu: Update Step and Microcode type to uint

Looking at the Redfish Resource and Schema guide:
https://www.dmtf.org/sites/default/files/standards/documents/DSP2046_2021.2.pdf

Section 6.86.6 at page 668, we see:

```
"Manufacturer": "Intel(R) Corporation",
"Model": "Multi-Core Intel(R) Xeon(R) processor 7xxx Series",
"ProcessorId": {
"VendorId": "GenuineIntel",
"IdentificationRegisters": "0x34AC34DC8901274A",
"EffectiveFamily": "0x42",
"EffectiveModel": "0x61",
"Step": "0x1",
"MicrocodeInfo": "0x429943"
},
```

We see that Step and Microcode information should be represented in hex.
To ensure this, we should pass in uint and let the external interface do
the conversion to hex string.

Following Intel specs, Stepping seems to be 1 byte, and Microcode 4.
https://en.wikipedia.org/wiki/CPUID#EAX=1:_Processor_Info_and_Feature_Bits

Signed-off-by: Brandon Kim <brandonkim@google.com>
Change-Id: Ifb2baf2c04da7bad08e2b1b01bb6db7acebc4e36

show more ...

Cpu: Add EffectiveFamily and update Model to EffectiveModel

Looking at the Redfish Resource and Schema guide:
https://www.dmtf.org/sites/default/files/standards/documents/DSP2046_2021.2.pdf

Section

Cpu: Add EffectiveFamily and update Model to EffectiveModel

Looking at the Redfish Resource and Schema guide:
https://www.dmtf.org/sites/default/files/standards/documents/DSP2046_2021.2.pdf

Section 6.86.6 at page 668, we see:

```
"Manufacturer": "Intel(R) Corporation",
"Model": "Multi-Core Intel(R) Xeon(R) processor 7xxx Series",
"ProcessorId": {
"VendorId": "GenuineIntel",
"IdentificationRegisters": "0x34AC34DC8901274A",
"EffectiveFamily": "0x42",
"EffectiveModel": "0x61",
"Step": "0x1",
"MicrocodeInfo": "0x429943"
},
```

We see that EffectiveFamily and EffectiveModel should be the hex
CPU ID values, while "Model" should be the human-readable name.

Set type of EffectiveFamily and EffectiveModel to uint.

Signed-off-by: Brandon Kim <brandonkim@google.com>
Change-Id: I1a0893a9ec04d41c2ba8d8737a6d210d1633f73b

show more ...

pcieslot, cpu: add upstream_processor association

Define a mechanism for documenting associations in PDI YAML files.

A new associations member is added to the interface definitions. The
new associ

pcieslot, cpu: add upstream_processor association

Define a mechanism for documenting associations in PDI YAML files.

A new associations member is added to the interface definitions. The
new associations member is an array, with each array element having an
object or structure type that consists of a name, reverse_name (all
OpenBMC associations are bi-directional), description, and an array of
required_endpoint_interfaces. The name and reverse_name properties must
be snake_case and comply with D-Bus specification restrictions on object
paths so they could be used directly as an object path element in a real
D-Bus implementation. Similarly the required_endpoint_interfaces array
elements must also comply with D-Bus specification restrictions and best
practices on interfaces names.

Associations should only exist as subordinate objects to a superior
object with a specific D-Bus interface - for example the
upstream_processor association should only exist on objects which
implement the PCIeSlot interface. This is the motivating thought behind
documenting OpenBMC associations in the existing interface definition
files instead of somewhere else. Reuse of upstream_processor in other
interfaces is allowed (for example a memory DIMM), but it must be
explicitly listed in each interface definition that wishes to host the
association.

This first use of the associations documentation adds an
upstream_processor interface used to link PCIeSlots to upstream PCIe
host bridges or on-processor PCIe root complexes.

Change-Id: I1d8bdb90a2705c4f16c5b015b7135870782ad672
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>

show more ...

Add "GenerationInUse" and "GenerationSupported" to PCIeDevice interface

Add PCIeDevice properties "GenerationInUse" and "GenerationSupported"
then let managerment APIs like redfish can expose the in

Add "GenerationInUse" and "GenerationSupported" to PCIeDevice interface

Add PCIeDevice properties "GenerationInUse" and "GenerationSupported"
then let managerment APIs like redfish can expose the information.

New property:
GenerationInUse : The PCIe interface generation in use by the device
GenerationSupported: The maximum PCIe generation supported by the device

Dbus Sample output:
NAME TYPE SIGNATURE RESULT/VALUE FLAGS
[...]
xyz.openbmc_project.PCIe.Device interface - - -
.DeviceType property s "SingleFunction" emits-change
.Function0ClassCode property s "0x060400" emits-change
[...]
.GenerationInUse property s "xyz.openbmc_project.Inventory.Item.PCIeSlot.Generations.Gen2" emits-change

Signed-off-by: Spencer Ku <Spencer.Ku@quantatw.com>
Change-Id: Ie1bf12a703dc85c3670487b146fb62f0dbae9908

show more ...

net: Client.Create interface from SNMP project

This is a port of phosphor-snmp commits d84e327dc and 95201f15c. Moving
to PDI simplifies the phosphor-snmp project build process and improves
OpenBMC

net: Client.Create interface from SNMP project

This is a port of phosphor-snmp commits d84e327dc and 95201f15c. Moving
to PDI simplifies the phosphor-snmp project build process and improves
OpenBMC DBus interface documentation consolidation.

Change-Id: Ib6aee82e1c60e4ca1d6d9f50e9ad886daa4bc92b
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>

show more ...