| b013c5f8 | 06-Feb-2023 |
Logananth Sundararaj <logananth_s@hcl.com> |
Add support for HotPluggable
This property describes if item can be hotplugged.
Tested: Tested and verified in YosemiteV2 platform.
Change-Id: I37dc08f57de3bcc7148f5bf8c7309f08a330890b
Signed-off-
Add support for HotPluggable
This property describes if item can be hotplugged.
Tested: Tested and verified in YosemiteV2 platform.
Change-Id: I37dc08f57de3bcc7148f5bf8c7309f08a330890b
Signed-off-by: Logananth Sundararaj <logananth_s@hcl.com>
show more ...
|
| 7b1b723d | 24-Oct-2022 |
Chau Ly <chaul@amperecomputing.com> |
Chassis.Intrusion: Add Rearm property
This patch adds Rearm property under
"xyz.openbmc_project.Chassis.Intrusion" interface, to specify
the method for rearming the chassis cover and updating the
"S
Chassis.Intrusion: Add Rearm property
This patch adds Rearm property under
"xyz.openbmc_project.Chassis.Intrusion" interface, to specify
the method for rearming the chassis cover and updating the
"Status" property. As defined in Redfish schema specification,
this property is optional and can take "Automatic" or "Manual".
If not set, "Rearm" will default to "Automatic", which will
directly update the raw chassis intrusion status to the "Status"
property. If set to "Manual", after an intrusion event, the
"Status" property will be kept to "HardwareIntrusion", no update
accepted, until a reset event happends for it to be updated normally
again.
Signed-off-by: Chau Ly <chaul@amperecomputing.com>
Change-Id: I73f6404a03184bea828727dcab4c38cbe2bdf35f
show more ...
|
| 67b0abdc | 31-Jan-2023 |
Pavithra Barithaya <pavithra.b@ibm.com> |
Add additional variant types for Notify D-Bus method
Add uint16_t and array[string] as variant types for
Notify method
Change-Id: Ic3c7accfb872815d60d1aef18c627abefc9e4c99
Signed-off-by: Pavithra B
Add additional variant types for Notify D-Bus method
Add uint16_t and array[string] as variant types for
Notify method
Change-Id: Ic3c7accfb872815d60d1aef18c627abefc9e4c99
Signed-off-by: Pavithra Barithaya <pavithra.b@ibm.com>
show more ...
|
| d1d7824e | 19-Jan-2023 |
Jayashree Dhanapal <jayashree-d@hcl.com> |
Add a new chassisType for Redfish
ChassisType "Blade" is added under Chassis interface to represent
the multihost system chassis which can be plugged in OCP platform.
Tested: Tested in Facebook Yos
Add a new chassisType for Redfish
ChassisType "Blade" is added under Chassis interface to represent
the multihost system chassis which can be plugged in OCP platform.
Tested: Tested in Facebook YosemiteV2 platform.
Change-Id: Ia3ca61b01b96e4febd0d2054ad19d01c70bfed24
Signed-off-by: Jayashree Dhanapal <jayashree-d@hcl.com>
show more ...
|
| 0f08d970 | 30-Dec-2022 |
Tim Lee <timlee660101@gmail.com> |
add Enabled properties and remove unused methods nmiEnable
Currently, x86-power-control is using property "Enabled"
to monitor NMI Source. But, NMISource.interface.yaml didn't
have this "Enabled" pr
add Enabled properties and remove unused methods nmiEnable
Currently, x86-power-control is using property "Enabled"
to monitor NMI Source. But, NMISource.interface.yaml didn't
have this "Enabled" property and the methods "nmiEnable" seems
unused in current openbmc design, remove it avoid usage confusion.
Signed-off-by: Tim Lee <timlee660101@gmail.com>
Change-Id: I1d7751cfe0de6c919ecd0deaea4a801db4d8b86e
show more ...
|
| ef9be234 | 11-Jan-2023 |
Sui Chen <suichen@google.com> |
Add ObjectManager path requirement for Voltage Regulator interfaces
Add the requirement/expectation of org.freedesktop.DBus.ObjectManager on
services implementing Control.VoltageRegular{Mode,Control
Add ObjectManager path requirement for Voltage Regulator interfaces
Add the requirement/expectation of org.freedesktop.DBus.ObjectManager on
services implementing Control.VoltageRegular{Mode,Control}.
The ObjectManager is expected to be implemented at
/xyz/openbmc_project/vr.
Currently, dbus-sdr specifically calls out the paths it uses to find the
ObjectManager, instead of using "/" which would find any ObjectManager
implemented at any location. "/xyz/openbmc_project/sensors" is listed in
dbus-sdr and in phosphor-dbus-interfaces now. This changes adds
"/xyz/openbmc_project/vr".
Change-Id: I6c74323189b74958301b445d6dc9a993a495e62f
Signed-off-By: Sui Chen <suichen@google.com>
show more ...
|
| 85d0c902 | 09-Jan-2023 |
Patrick Williams <patrick@stwcx.xyz> |
gen: update due to sdbusplus-gen-meson change
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I5cacaf5d4ce9b7ed40a46b8d9075be1eb093d40a |
| 27b83c43 | 12-Oct-2022 |
Hieu Huynh <hieuh@os.amperecomputing.com> |
bootprogress: add OEM value for ProgressStages enumerations
This commit adds the OEM enumerations for the ProgressStages to
indicate the last stage is OEM as defined in the DSP0268_2021.2
Redfish Sc
bootprogress: add OEM value for ProgressStages enumerations
This commit adds the OEM enumerations for the ProgressStages to
indicate the last stage is OEM as defined in the DSP0268_2021.2
Redfish Schema Supplement.pdf specification and DEN0069D_SBMR_2.0.pdf
document section F.2.2.
Signed-off-by: Hieu Huynh <hieuh@os.amperecomputing.com>
Change-Id: I5a2b5943df54d5208fb847c7b9e89c09af3b73cd
show more ...
|
| a1347418 | 06-Dec-2022 |
Patrick Williams <patrick@stwcx.xyz> |
reformat with latest settings
Reformat with the latest settings from openbmc-build-scripts (and
copy latest config files where appropriate). Fix a few minor
markdownlint issues.
Signed-off-by: Pat
reformat with latest settings
Reformat with the latest settings from openbmc-build-scripts (and
copy latest config files where appropriate). Fix a few minor
markdownlint issues.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I55205817c29dc3f182a165ddf9cd5d4e07b90063
show more ...
|
| 3c7b858a | 08-Oct-2021 |
Vijay F Lobo <vflobo@us.ibm.com> |
Convert ServiceProviderNotify to enum
Converted ServiceProviderNotify to an enum.
Supported options are - "NotSupported", "Notify" and "Inhibit".
Changes in phosphor-logging are at the link below
h
Convert ServiceProviderNotify to enum
Converted ServiceProviderNotify to an enum.
Supported options are - "NotSupported", "Notify" and "Inhibit".
Changes in phosphor-logging are at the link below
https://gerrit.openbmc.org/c/openbmc/phosphor-logging/+/58815
For more details on the discussion look at the link below.
https://gerrit.openbmc-project.xyz/c/openbmc/bmcweb/+/46886/7/redfish-core/lib/log_services.hpp#1411
Signed-off-by: Vijay F Lobo <vflobo@us.ibm.com>
Change-Id: Iefe95a5531792bc79e363923deb7fc894774ee67
Signed-off-by: Lakshmi Yadlapati <lakshmiy@us.ibm.com>
show more ...
|
| 380bb024 | 09-Nov-2022 |
George Liu <liuxiwei@inspur.com> |
Fix the association between Item and PowerSupply
PowerSupply should be associated with an Item, instead of Chassis.
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: If2e7dbea6f1cf0eb2e598
Fix the association between Item and PowerSupply
PowerSupply should be associated with an Item, instead of Chassis.
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: If2e7dbea6f1cf0eb2e5984bb83bea252fd7f94cf
show more ...
|
| 1a891d32 | 24-Oct-2022 |
Nan Zhou <nanzhoumails@gmail.com> |
User: add interfaces and errors for groups
As proposed in the following design,
[1] https://github.com/openbmc/docs/blob/master/designs/redfish-authorization.md
The UserManager interface needs to e
User: add interfaces and errors for groups
As proposed in the following design,
[1] https://github.com/openbmc/docs/blob/master/designs/redfish-authorization.md
The UserManager interface needs to expose new interfaces to add/delete
secondary groups, which are then used to model Redfish roles and
privileges.
An implementation is in the follow code review,
[1] https://gerrit.openbmc.org/c/openbmc/phosphor-user-manager/+/58143.
Signed-off-by: Nan Zhou <nanzhoumails@gmail.com>
Change-Id: I252e56dc03e694e3aedf3ae6fdda64edc947fc06
show more ...
|
| 219368be | 26-Oct-2022 |
William A. Kennington III <wak@google.com> |
Network/VLAN: Remove InterfaceName
Having the interface name is redundant with EthernetInterface and
nothing currently relies on this version of the value.
Change-Id: I53e700dae937059c2fd415bf7d546
Network/VLAN: Remove InterfaceName
Having the interface name is redundant with EthernetInterface and
nothing currently relies on this version of the value.
Change-Id: I53e700dae937059c2fd415bf7d546a8c887b68d4
Signed-off-by: William A. Kennington III <wak@google.com>
show more ...
|
| e7c10bd5 | 03-Nov-2022 |
George Liu <liuxiwei@inspur.com> |
Item, LED: add fault_identifying association
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: Ibc9d0859498fafbc1647179357d5d38926f302d9 |
| 9eb460c6 | 31-Oct-2022 |
George Liu <liuxiwei@inspur.com> |
Item, LED: add identifying association
Create association documentation between LED and Item.
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: I121cd09cd3eb032400200e51a1c94e2dfcc872cc |
| d0aa13b4 | 31-Oct-2022 |
George Liu <liuxiwei@inspur.com> |
Fan, Item: add cooling association
Create association documentation between Fan and Item.
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: Ifc3f38958c00f432a741774dbf570f39dd817966 |
| 63190140 | 07-Nov-2022 |
DelphineCCChiu <Delphine_CC_Chiu@wiwynn.com> |
Add PowerCycleError parameter in Chassis Error yaml
A new system is being designed which will utilize phosphor-state-manager
and it requires the chassis system power cycle feature.
When chassis powe
Add PowerCycleError parameter in Chassis Error yaml
A new system is being designed which will utilize phosphor-state-manager
and it requires the chassis system power cycle feature.
When chassis power cycle target failed to complete,
it need a parameter to represent chassis system power error status.
Test plan:
Build success and check the chassis system power parameter in configuration.
Change-Id: I0de438b63f6221ec4fbffcdc070a65a48a2dafde
Signed-off-by: Bonnie Lo <Bonnie_Lo@wiwynn.com>
show more ...
|
| 36b527af | 02-Nov-2022 |
Benjamin Fair <benjaminfair@google.com> |
Inventory: Add "containing" Association for Item
This Association indicates that an Item (usually a Chassis or Board
object) physically contains other objects.
Also remove the duplicate definition
Inventory: Add "containing" Association for Item
This Association indicates that an Item (usually a Chassis or Board
object) physically contains other objects.
Also remove the duplicate definition from Cpu and CpuCore since it's now
covered by Item.
Signed-off-by: Benjamin Fair <benjaminfair@google.com>
Change-Id: I6df06b1dddfd9408ff39e8917d269a2cba22668d
show more ...
|
| 484f6c45 | 01-Nov-2022 |
Patrick Williams <patrick@stwcx.xyz> |
Item: remove documentation for non-conforming association
The association for CPU/Slot does not conform to the documented
association rules, so remove it from the readme so as to not mislead
others.
Item: remove documentation for non-conforming association
The association for CPU/Slot does not conform to the documented
association rules, so remove it from the readme so as to not mislead
others.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I00fd61d13c9d75609221698118225f6dab5fe56f
show more ...
|
| fc5546ea | 25-Oct-2022 |
Sui Chen <suichen@google.com> |
Item: Add description for associations involving Bmc
Change-Id: I9aa0fe58c5ab0c47f168c1340fd8c328ad7f6e9e
Signed-off-by: Sui Chen <suichen@google.com> |
| 8c79b1dc | 08-Aug-2022 |
Nikhil Namjoshi <nikhilnamjoshi@google.com> |
Inventory : Add Association interface for Cpu and Core
The change #38570 in bmcweb, uses associations between Cpu and CpuCore.
So document those associations in phosphor-dbus-interfaces
Change-Id:
Inventory : Add Association interface for Cpu and Core
The change #38570 in bmcweb, uses associations between Cpu and CpuCore.
So document those associations in phosphor-dbus-interfaces
Change-Id: I5b12ca5a89c094e2a5b47a7fbc39482d6286e9d3
Signed-off-by: Nikhil Namjoshi <nikhilnamjoshi@google.com>
show more ...
|
| b78a0704 | 24-Oct-2022 |
Patrick Williams <patrick@stwcx.xyz> |
treewide: use more specific object_path type
The sdbus++ tool allows the YAML to specify either "path" or
"object_path". Switch to "object_path" everywhere for consistency
and clarity.
Signed-off-
treewide: use more specific object_path type
The sdbus++ tool allows the YAML to specify either "path" or
"object_path". Switch to "object_path" everywhere for consistency
and clarity.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I60c51b2ece5fc4cb23d05ce5151301db3dcddf3a
show more ...
|
| 8e56f4cd | 11-Oct-2022 |
Willy Tu <wltu@google.com> |
mapper: Add Associated subtree method definition
Create new mapper function to make subtree call and association call at
the same time. With the association definitition, we will have more
endpoints
mapper: Add Associated subtree method definition
Create new mapper function to make subtree call and association call at
the same time. With the association definitition, we will have more
endpoints to fetch and verify that it is actually the resource that we
are looking for. We need to verify that it has the expected interface to
confirm that it is right device. In the current workflow this will take
two dbus calls to the mapper to get the assocation and the subtree.
This change aims to reduce that down to one by combination the two
operations. It will not sigificant performance increase for the daemons,
but it can help reduce the load on the dbus-broker.service.
Tested:
```
Normal Call:
busctl call "xyz.openbmc_project.ObjectMapper" \
"/xyz/openbmc_project/object_mapper" \
"xyz.openbmc_project.ObjectMapper" "GetSubTreePaths" sias \
"/xyz/openbmc_project/inventory" 0 1 \
"xyz.openbmc_project.Inventory.Item.Storage"
as 4 "/xyz/openbmc_project/inventory/storage_0" "/xyz/openbmc_project/inventory/storage_1"
"/xyz/openbmc_project/inventory/storage_4" "/xyz/openbmc_project/inventory/storage_3"
Associated Call: (Only 0 and 1 is associated to the chassis)
busctl call "xyz.openbmc_project.ObjectMapper" \
"/xyz/openbmc_project/object_mapper" \
"xyz.openbmc_project.ObjectMapper" "GetAssociatedSubTreePaths" ssias \
"/xyz/openbmc_project/inventory/chassis_0/storage" \
"/xyz/openbmc_project/inventory" 0 1 "xyz.openbmc_project.Inventory.Item.Storage"
as 2 "/xyz/openbmc_project/inventory/storage_0" "/xyz/openbmc_project/inventory/storage_1"
```
Signed-off-by: Willy Tu <wltu@google.com>
Change-Id: I079adf41a5775f80b9c773e8e9e319d46be924ea
show more ...
|
| f3e6ff19 | 24-Oct-2022 |
Patrick Williams <patrick@stwcx.xyz> |
ACPIPowerState: set default property values
The property values should default to 'Unknown' instead of 'S0' (the
first enum).
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ida5362e
ACPIPowerState: set default property values
The property values should default to 'Unknown' instead of 'S0' (the
first enum).
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ida5362ec29238a14e6b5ce078ad0c0951993dd8b
show more ...
|
| 78f3103d | 20-Oct-2022 |
Chris Cain <cjcain@us.ibm.com> |
Control.Power.CapLimits: Add power cap limits interface
This interface will provide the minimum and maximum power cap values
supported. This will be hosted/written by OCC.Control and is replacing
th
Control.Power.CapLimits: Add power cap limits interface
This interface will provide the minimum and maximum power cap values
supported. This will be hosted/written by OCC.Control and is replacing
the same properties from Control.Power.Cap.
The properties in Control.Power.Cap are hosted by Settings and the cap
limits had to temporarily be made writable so that OCC.Control could
write them.
Change-Id: Id24be182f7af8bfdc66d312a72b56afe172f8543
Signed-off-by: Chris Cain <cjcain@us.ibm.com>
show more ...
|