History log of /openbmc/phosphor-dbus-interfaces/ (Results 1 – 25 of 886)
Revision Date Author Comments
(<<< Hide modified files)
(Show modified files >>>)
407f4a8c03-Nov-2025 Deepak Kodihalli <deepak.kodihalli.83@gmail.com>

metric: add path segments for network metrics

Add metrics, via path segments, for common NIC port metrics.
The nvidia-gpu dbus-sensors app will implement these metrics for Nvidia
devices such as the

metric: add path segments for network metrics

Add metrics, via path segments, for common NIC port metrics.
The nvidia-gpu dbus-sensors app will implement these metrics for Nvidia
devices such as the ConnectX NIC. These metrics exist in the Redfish
schemas already.

The existing measuring/measured_by associations documented in the value
interface will be used to associate an inventory item (network
device/port) to the network metrics.

Change-Id: If6fb4b7d3386aebe0afafccc1fea8dd5e081dc26
Signed-off-by: Deepak Kodihalli <deepak.kodihalli.83@gmail.com>

show more ...

a04d386721-Jan-2026 Ed Tanous <ed@tanous.net>

Remove old rest API documentation

These commands are already documented in the main docs repo [1]. This
was found when trying to clean up old login routines. Rather than fix
the docs, just remove

Remove old rest API documentation

These commands are already documented in the main docs repo [1]. This
was found when trying to clean up old login routines. Rather than fix
the docs, just remove them and rely on the main documentation in the
docs repo.

[1] https://github.com/openbmc/docs/blob/master/REST-cheatsheet.md

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

show more ...

f1b962be03-Nov-2025 Deepak Kodihalli <deepak.kodihalli.83@gmail.com>

metric: add path segments for PCIe port metrics

Add metrics, via path segments, for common PCIe port metrics. The
nvidia-gpu dbus-sensors app will implement these metrics for Nvidia PCIe
devices suc

metric: add path segments for PCIe port metrics

Add metrics, via path segments, for common PCIe port metrics. The
nvidia-gpu dbus-sensors app will implement these metrics for Nvidia PCIe
devices such as the ConnectX PCIe switch. These metrics exist in the
Redfish schemas already as metrics - see "PCIeErrors" under
https://redfish.dmtf.org/schemas/v1/PortMetrics.v1_8_0.json.

Some of these metrics are generic and some are PCIe specific - they've
been added accordingly.

Also add a path for Port metrics.

The existing measuring/measured_by associations documented in the value
interface will be used to associate an inventory item (PCIe port) to the
PCIe port metrics object.

Change-Id: I270ad1c3d5dacafb2c7cdf84d87d7654eafdd1f0
Signed-off-by: Deepak Kodihalli <deepak.kodihalli.83@gmail.com>

show more ...

b0f478ea27-Oct-2025 Deepak Kodihalli <deepak.kodihalli.83@gmail.com>

inventory: port: add Lanes and Speed

Add Width and Speed properties. On Nvidia ConnectX PCIe
switchboards, this patch allows the PCIe port lanes in use and current
speed properties to be exposed ove

inventory: port: add Lanes and Speed

Add Width and Speed properties. On Nvidia ConnectX PCIe
switchboards, this patch allows the PCIe port lanes in use and current
speed properties to be exposed over Redfish (backend is dbus-sensors).

Change-Id: I9e0b4fe3d138cdf7ca2edf3ac6692da9dea97bd7
Signed-off-by: Deepak Kodihalli <deepak.kodihalli.83@gmail.com>

show more ...

6d2ab68915-Jan-2026 Patrick Williams <patrick@stwcx.xyz>

State.BMC: Set default state to 'NotReady'

By default the initial value of a property will be either the 'default'
value specified or the default C++ initialization. For an enumeration
that would b

State.BMC: Set default state to 'NotReady'

By default the initial value of a property will be either the 'default'
value specified or the default C++ initialization. For an enumeration
that would be the first enum value, which in the case of the BMC is
"Ready". This makes it difficult to determine the initial case, in
order to send `BMC.StateChanged` events. There are two obvious options:

- Create an "Unknown" value which is only used for the
initialization case.
- Set "NotReady" as the default.

Since it isn't particularly useful to have a "NotReady" event emitted
during the boot sequence, and likely we are "NotReady" when the BMC
management application starts, setting this to the `default` makes
the code straight-forward for not emitting a spurious "NotReady" event.

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

show more ...

526d655005-Dec-2025 Eric Yang <eric.yang.wiwynn@gmail.com>

State.BMC: Add structured event for BMC state

Add a new event (xyz.openbmc_project.State.BMC.State) in the BMC events
YAML to represent the current BMC state as enum metadata.

Motivation:
Provide a

State.BMC: Add structured event for BMC state

Add a new event (xyz.openbmc_project.State.BMC.State) in the BMC events
YAML to represent the current BMC state as enum metadata.

Motivation:
Provide a standard, structured event schema so services can consistently
log BMC state transitions (Ready, NotReady, UpdateInProgress, Quiesced).

Change-Id: Ib69a45e3c4d39f35279a7908811e5a725e3f39ed
Signed-off-by: Eric Yang <eric.yang.wiwynn@gmail.com>

show more ...

09aa730413-Jan-2026 Alexander Hansen <alexander.hansen@9elements.com>

telemetry: document namespace paths

document namespace paths for Telemetry Report and Telemetry Trigger.

These are used by the telemetry application

```
busctl tree xyz.openbmc_project.Telemetry
`

telemetry: document namespace paths

document namespace paths for Telemetry Report and Telemetry Trigger.

These are used by the telemetry application

```
busctl tree xyz.openbmc_project.Telemetry
`- /xyz
`- /xyz/openbmc_project
`- /xyz/openbmc_project/Telemetry
|- /xyz/openbmc_project/Telemetry/Reports
| `- /xyz/openbmc_project/Telemetry/Reports/TelemetryService
| `- /xyz/openbmc_project/Telemetry/Reports/TelemetryService/AirTemps1s
`- /xyz/openbmc_project/Telemetry/Triggers
```

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

show more ...

3d500d7007-Jan-2026 Leo Yang <Leo-Yang@quantatw.com>

com.meta: yosemite5: add compatible strings for HSC/VR

Add compatible device strings specific to yosemite5
HSC:XDP71X_p52v_hsc
VR:RAA228006_discrete_vr

Change-Id: I5170d79bc5d451250cb3ba091989ef7e8

com.meta: yosemite5: add compatible strings for HSC/VR

Add compatible device strings specific to yosemite5
HSC:XDP71X_p52v_hsc
VR:RAA228006_discrete_vr

Change-Id: I5170d79bc5d451250cb3ba091989ef7e87e0bdd9
Signed-off-by: Leo Yang <Leo-Yang@quantatw.com>

show more ...

1e4506c707-Jan-2026 Patrick Williams <patrick@stwcx.xyz>

gitignore: add stdexec wrap

stdexec wrap comes from the sdbusplus subproject and is an indirection
there. Add it to the gitignore so it doesn't get committed.

Signed-off-by: Patrick Williams <patr

gitignore: add stdexec wrap

stdexec wrap comes from the sdbusplus subproject and is an indirection
there. Add it to the gitignore so it doesn't get committed.

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

show more ...

96c1421906-Jan-2026 Leo Wang <leo.jt.wang@fii-foxconn.com>

com.meta: add Clemente CPLD compatible hardware definitions

Add compatible hardware enum definitions for CPLD devices on the
Clemente platform.

These definitions are used by phosphor-software-manag

com.meta: add Clemente CPLD compatible hardware definitions

Add compatible hardware enum definitions for CPLD devices on the
Clemente platform.

These definitions are used by phosphor-software-manager CPLD update
daemon to match firmware images against supported hardware via the
CompatibleHardware string.

Change-Id: Ib70c9e4410c6e0dfda83646451b412192f9b4ae4
Signed-off-by: Leo Wang <leo.jt.wang@fii-foxconn.com>

show more ...

25c397dd07-Jan-2026 Potin Lai <potin.lai@quantatw.com>

com.meta: add SanMiguel BMC

Adding compatible string for SanMiguel BMC type.

Change-Id: Ib66c402652fdaf5a36d140dbad4895f32de3baf6
Signed-off-by: Potin Lai <potin.lai@quantatw.com>

90b011eb10-Oct-2024 Ivan Moiseev <moiseev.ivan4w@yandex.com>

User.Manager: add CreateUser2 method to create user

This adds CreateUser2 method to user manager interface on D-Bus. This
method is identical to existing CreateUser method but takes map of
variants

User.Manager: add CreateUser2 method to create user

This adds CreateUser2 method to user manager interface on D-Bus. This
method is identical to existing CreateUser method but takes map of
variants instead of CreateUser parameters with PasswordExpiration
property that it allows specify Epoch time when the password of
the user being created expires. The idea to introduce additional method
creating a user with a password expiration specified was suggested in
a comment [1] in the corresponding review in bmcweb [2].

When password expiration argument value is maximum then the password
will not expire. This value can also be used in a siutation when
password expiration must be reset.

When password expiration argument value is zero then the password
expiration will not be set. Basically, in this case function will work
exactly as existing CreateUser. I'm planning to extended this method by
adding account expiration argument, so this value will be useful in a
situation when, for example, only account expiration must be specified
without password expiration.

GetUserInfo method in user manager now reports password expiration Epoch
time as well.

User.Attributes: add password expiration errors

Error indicating invalid date time value was added when password
expiration date time point to the moment which happened before the last
password change.

[1] ```https://gerrit.openbmc.org/c/openbmc/bmcweb/+/75372```
[2] ```https://gerrit.openbmc.org/c/openbmc/bmcweb/+/75372/comment/d35c832d_e769bf9c/```
[3] ```https://gerrit.openbmc.org/c/openbmc/phosphor-user-manager/+/75237```

Change-Id: I0a33e343ec9369b42a66ff6ff0217fcba5d05b2c
Signed-off-by: Ivan Moiseev <moiseev.ivan4w@yandex.com>
Signed-off-by: Ivan Mikhaylov <fr0st61te@gmail.com>

show more ...

1ff0efa002-Jan-2026 Kyle Hsieh <Kyle.Hsieh@quantatw.com>

com.meta: add compatible device strings for Ventura2

Add Ventura2 compatible strings for SCM CPLD and TPM
to enable firmware update and version check.

Change-Id: I546986ac2d65ba29d9e922a06e9ede9939

com.meta: add compatible device strings for Ventura2

Add Ventura2 compatible strings for SCM CPLD and TPM
to enable firmware update and version check.

Change-Id: I546986ac2d65ba29d9e922a06e9ede9939437d87
Signed-off-by: Kyle Hsieh <Kyle.Hsieh@quantatw.com>

show more ...

16e45db506-Jan-2026 Ravi Teja <raviteja28031990@gmail.com>

OWNERS: Add myself as reviewer

I'm interested in changes to Network, Certs and User interfaces
so adding myself as reviewer for these directories.

Change-Id: I832df8356e0f4a11cebd780584804614911368

OWNERS: Add myself as reviewer

I'm interested in changes to Network, Certs and User interfaces
so adding myself as reviewer for these directories.

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

show more ...

a629b87628-Apr-2022 Jiaqing Zhao <jiaqing.zhao@intel.com>

EthernetInterface: Add FullDuplex property

Add FullDuplex property to support Redfish FullDuplex property. It will
be implemented in phosphor-networkd.

Change-Id: Iaf08ecc19e8302a6b38e338171476da12

EthernetInterface: Add FullDuplex property

Add FullDuplex property to support Redfish FullDuplex property. It will
be implemented in phosphor-networkd.

Change-Id: Iaf08ecc19e8302a6b38e338171476da1279c5f0e
Signed-off-by: Jiaqing Zhao <jiaqing.zhao@intel.com>
Signed-off-by: Ravi Teja <raviteja28031990@gmail.com>

show more ...

af6b2cce13-Nov-2025 Deepak Kodihalli <deepak.kodihalli.83@gmail.com>

Add association between PCIeSwitch and Port

This enables implementation of the Redfish Switch schema, and depicting
links between Switch and Port. This is part of the work to enable
Redfish for the

Add association between PCIeSwitch and Port

This enables implementation of the Redfish Switch schema, and depicting
links between Switch and Port. This is part of the work to enable
Redfish for the Nvidia ConnectX PCIe switchboard.

This is similar to df32eb57 in terms of using the
"connecting"/""connected_to" associations.

The relevant Redfish schema is:
https://redfish.dmtf.org/schemas/v1/Switch.v1_10_0.json

```
"Ports": {
"$ref": "http://redfish.dmtf.org/schemas/v1/PortCollection.json#/definitions/PortCollection",
"description": "The link to the collection ports for this switch.",
"longDescription": "This property shall contain a link to a resource collection of type `PortCollection`.",
"readonly": true
}
```

Change-Id: Ib1dfc61f599da9f235048832121fe65642f99a40
Signed-off-by: Deepak Kodihalli <deepak.kodihalli.83@gmail.com>

show more ...

b575e64e19-Nov-2025 Alexander Hansen <alexander.hansen@9elements.com>

document required_endpoint_interfaces

Documenting my current understanding of the
`required_endpoint_interfaces` property since i did not find it
documented anywhere [1].

References:
[1] https://gi

document required_endpoint_interfaces

Documenting my current understanding of the
`required_endpoint_interfaces` property since i did not find it
documented anywhere [1].

References:
[1] https://github.com/search?q=org%3Aopenbmc+required_endpoint_interfaces&type=code

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

show more ...

27bee56727-Oct-2025 Deepak Kodihalli <deepak.kodihalli.83@gmail.com>

inventory: port: add protocol and type

Add PortProtocol and PortType properties. On Nvidia ConnectX PCIe
switchboards, this patch allows the port protocol and type information
to be exposed over Red

inventory: port: add protocol and type

Add PortProtocol and PortType properties. On Nvidia ConnectX PCIe
switchboards, this patch allows the port protocol and type information
to be exposed over Redfish (backend is dbus-sensors).

Redfish defines a multitude of port protocols; this patch adds those
that can be tested on the Nvidia ConnectX switchboard platform.

Change-Id: Ie966be79e4796be5248f142703c1afaa62f083d1
Signed-off-by: Deepak Kodihalli <deepak.kodihalli.83@gmail.com>

show more ...

2ce9dee813-Jun-2025 Rohit PAI <ropai@nvidia.com>

Add max speed for accelerator device (GPU)

Max speed property for GPU device. The MR adds support for Max Speed
property of the GPU device. This is required to populate the MaxSpeedMHz
property unde

Add max speed for accelerator device (GPU)

Max speed property for GPU device. The MR adds support for Max Speed
property of the GPU device. This is required to populate the MaxSpeedMHz
property under Processor schema in Redfish.

Change-Id: I93d08b96b2b88013165cb64b260e966ffb63b1ba
Signed-off-by: Rohit PAI <ropai@nvidia.com>

show more ...

78a1849407-Jul-2025 Harshit Aghera <haghera@nvidia.com>

Sensor: add Type interface

Add an interface to indicate the type of the sensor.

Each property in the interface maps to a distinct group of sensor
subtypes.

Examples for use cases -

Nvidia datacen

Sensor: add Type interface

Add an interface to indicate the type of the sensor.

Each property in the interface maps to a distinct group of sensor
subtypes.

Examples for use cases -

Nvidia datacenter GPUs has a temperature sensor for the Thermal Limit
(TLIMIT) temperature. It is a countdown in degrees Celsius to the
threshold at which the closest software slowdown mechanism will engage.
The reported TLIMIT temperature can be greater than 0 degrees Celsius if
the current temperature is beyond a software slowdown threshold. The
TLIMIT value can be a negative value during the period when a slowdown
is engaged. The DMTF property ReadingBasis can be set to Headroom for
this sensor.

Property Implementation defines the type of the sensor based on whether
the sensor reading is obtained from a physical sensor or the reading is
synthesized from the reading of one or more different sensors.

Change-Id: I1d2d6a6c45f6bf292c56cb34900c0d280f8d93bd
Signed-off-by: Harshit Aghera <haghera@nvidia.com>

show more ...

1a062b4914-Nov-2025 Michal Orzel <michalx.orzel@intel.com>

Telemetry: Remove Trigger's LogToJournal action

It has been decided to drop support to LogToLogService action on
Redfish, because it doesn't comply with specification in its current
form. Its dbus c

Telemetry: Remove Trigger's LogToJournal action

It has been decided to drop support to LogToLogService action on
Redfish, because it doesn't comply with specification in its current
form. Its dbus counterpart is LogToJournal, therefore this change
removes it from the spec.

bmcweb patch: https://gerrit.openbmc.org/c/openbmc/bmcweb/+/84960
telemetry patch: https://gerrit.openbmc.org/c/openbmc/telemetry/+/85318

Change-Id: I38c6c1076783c229763eb6e3d7d7a64873bc0ad0
Signed-off-by: Michal Orzel <michalx.orzel@intel.com>

show more ...

360717f017-Nov-2025 Jae Hyun Yoo <jae.yoo@oss.qualcomm.com>

com.qualcomm: add AST2600 model

Add compatible string for AST2600 model.
Qualcomm uses a monolithic build target for all AST2600-based BMCs,
so the model name ends up being generic like this.

Chang

com.qualcomm: add AST2600 model

Add compatible string for AST2600 model.
Qualcomm uses a monolithic build target for all AST2600-based BMCs,
so the model name ends up being generic like this.

Change-Id: I52c25f3dc19ade755fecb43fea794e751c43caf4
Signed-off-by: Jae Hyun Yoo <jae.yoo@oss.qualcomm.com>

show more ...

1730647a26-Nov-2025 Alexander Hansen <alexander.hansen@9elements.com>

fix typo: Association endpoints

The `xyz.openbmc_project.Association` interface uses 'endpoints'
property and not 'Endpoints'.

It's created this way by the ObjectMapper and consumed that way by the

fix typo: Association endpoints

The `xyz.openbmc_project.Association` interface uses 'endpoints'
property and not 'Endpoints'.

It's created this way by the ObjectMapper and consumed that way by the
reactors.

```
root@s8030-bmc-30303035c0c1:~# busctl introspect xyz.openbmc_project.ObjectMapper /xyz/openbmc_project/software/bmc/functional
NAME TYPE SIGNATURE RESULT/VALUE FLAGS
xyz.openbmc_project.Association interface - - -
.endpoints property as 1 "/xyz/openbmc_project/software/a7e2... emits-change
```

Searching for "Endpoints" [1]
yields mostly results in bmcweb where the string is not used in DBus
context.

Searching for "endpoints" [2]
yields results in various repos where the string is used for the
property name.

References:
[1] https://github.com/search?q=org%3Aopenbmc+%2F%28%3F-i%29%5C%22Endpoints%5C%22%2F+&type=code&p=1
[2] https://github.com/search?q=org%3Aopenbmc+%2F%28%3F-i%29%5C%22endpoints%5C%22%2F+&type=code

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

show more ...

03bc262e20-Nov-2025 Alexander Hansen <alexander.hansen@9elements.com>

fix typo: reverse_names -> reverse_name

For a directed association, there is only one reverse name.

Fix the documentation to use `reverse_name` property consistently.
Otherwise the tooling will not

fix typo: reverse_names -> reverse_name

For a directed association, there is only one reverse name.

Fix the documentation to use `reverse_name` property consistently.
Otherwise the tooling will not process it without adding quirks there.

Also always put the associations as a list for the same reason.

Tested: Headers are generated using [1] without errors.

References:
[1] https://gerrit.openbmc.org/c/openbmc/sdbusplus/+/85421

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

show more ...

a341b2ae19-Nov-2025 Alexander Hansen <alexander.hansen@9elements.com>

fix typo: association -> associations

Use key `associations:` for consistency.

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

12345678910>>...36