schemas: chassis types for Inventory.Item.Chassis

This commit add the chassis types and corresponding interface as
described in [1].

[1] https://github.com/openbmc/phosphor-dbus-interfaces/blob/mas

schemas: chassis types for Inventory.Item.Chassis

This commit add the chassis types and corresponding interface as
described in [1].

[1] https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/yaml/xyz/openbmc_project/Inventory/Item/Chassis.interface.yaml

Tested:
Interfaces are added with the corresponding properties RackMount
and Blade under the related path.

Change-Id: Id0cb2b2450b290d0d2af994d07cec301b441ab2d
Signed-off-by: Sean He <sean.he.wiwynn@gmail.com>

show more ...

configurations: yosemite4: Support for CPU Configurations

- Configurations type support CPU
- Displays CPU serial number

Change-Id: I3fe7da27b1729bd11c267849e2154629b65638b6
Signed-off-by: Ingrid C

configurations: yosemite4: Support for CPU Configurations

- Configurations type support CPU
- Displays CPU serial number

Change-Id: I3fe7da27b1729bd11c267849e2154629b65638b6
Signed-off-by: Ingrid Chen <ingrid.chen.wiwynn@gmail.com>

show more ...

configurations: yv4 sentinel dome: add interface

Add ManagedHost interface to yv4 sentinel dome, which will be
used by bmcweb for system discovery and other dbus operations.

Change-Id: I633722ccfa7

configurations: yv4 sentinel dome: add interface

Add ManagedHost interface to yv4 sentinel dome, which will be
used by bmcweb for system discovery and other dbus operations.

Change-Id: I633722ccfa7d957d976ef7dc37fdda12df35d59e
Signed-off-by: Oliver Brewka <mox669.dev@gmail.com>

show more ...

schemas: legacy: Extend PSUSensor properties

PSUSensor now supports a new sensor type named smpro_hwmon and the
sensor can report more sensors inside its sysfs. This commit extends the
properties s

schemas: legacy: Extend PSUSensor properties

PSUSensor now supports a new sensor type named smpro_hwmon and the
sensor can report more sensors inside its sysfs. This commit extends the
properties so the sensor can be configured in Entity-Manager with full
support for the component sensors.

Tested: on Mt.Jade platform with config "Type": "smpro_hwmon" and
necessary _Min, _Max, _Name, _Scale configs
=> The CI build passes and the sensor can be created successfully on
D-Bus.

Signed-off-by: Chau Ly <chaul@amperecomputing.com>
Change-Id: Ica45569eb349169efa3032267b4bfd4368e7aadd

show more ...

configurations: minerva_cmm: add calibration for HSC sensor

Add the calibration formula for the HSC sensor according to the power
team's measurement result.

Change-Id: I79ec9c74dc4d25204748b3883ef3

configurations: minerva_cmm: add calibration for HSC sensor

Add the calibration formula for the HSC sensor according to the power
team's measurement result.

Change-Id: I79ec9c74dc4d25204748b3883ef377d1606db201
Signed-off-by: Yang Chen <yang.chen@quantatw.com>

show more ...

schemas: virtual sensor: Add average and sum for calculation sensor

Average and Sum are implemented in phosphor-virtual-sensors [1]. This
commit supports Average and Sum types in schemas.

[1]: http

schemas: virtual sensor: Add average and sum for calculation sensor

Average and Sum are implemented in phosphor-virtual-sensors [1]. This
commit supports Average and Sum types in schemas.

[1]: https://gerrit.openbmc.org/c/openbmc/phosphor-virtual-sensor/+/74716

Signed-off-by: George Liu <liuxiwei@ieisystem.com>
Change-Id: I726b7a853b5b42bea9c5ea266d5c5a7be6addd83

show more ...

configurations: catalina_pdb: add max/min value for vdrop sensor

We noticed that the vdrop sensor values ​​were not updating correctly
and we discovered this was due to incorrect MaxValue and MinVal

configurations: catalina_pdb: add max/min value for vdrop sensor

We noticed that the vdrop sensor values ​​were not updating correctly
and we discovered this was due to incorrect MaxValue and MinValue
settings.
The value of the vdrop sensor is usually between 1 and -1 volts. Add
in0_Max and in0_Mix definitions for the vdrop sensor.

Tested results:
```
root@bmc:~# busctl introspect xyz.openbmc_project.PSUSensor /xyz/openbmc_project/sensors/voltage/PDB_POSITIVE_VDROP_VOLT_V xyz.openbmc_project.Sensor.Value
NAME TYPE SIGNATURE RESULT/VALUE FLAGS
.MaxValue property d 1 emits-change
.MinValue property d -1 emits-change
.Unit property s "xyz.openbmc_project.Sensor.Value.Unit.… emits-change
.Value property d 0.104 emits-change writable
root@bmc:~# busctl introspect xyz.openbmc_project.PSUSensor /xyz/openbmc_project/sensors/voltage/PDB_RETURN_VDROP_VOLT_V xyz.openbmc_project.Sensor.Value
NAME TYPE SIGNATURE RESULT/VALUE FLAGS
.MaxValue property d 1 emits-change
.MinValue property d -1 emits-change
.Unit property s "xyz.openbmc_project.Sensor.Value.Unit.… emits-change
.Value property d 0.107 emits-change writable
```

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

show more ...

schemas: Add Inventory.Item.Storage interface

This commit adds the Item.Storage interface as described in [1].

Support the BSM with the `xyz.openbmc_project.Inventory.Item.Storage`
interface to lab

schemas: Add Inventory.Item.Storage interface

This commit adds the Item.Storage interface as described in [1].

Support the BSM with the `xyz.openbmc_project.Inventory.Item.Storage`
interface to label the hardware type.

[1] https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/yaml/xyz/openbmc_project/Inventory/Item/Storage.interface.yaml

Change-Id: I0655987262cd13aff32b376f8aa8baeff498afa4
Signed-off-by: Ingrid Chen <ingrid.chen.wiwynn@gmail.com>

show more ...

json: adjust definitions alias

JSON Schema suggests[1] using "$defs" rather than "definitions" as
the location for reusable definitions in a schema. While, this
isn't strictly required, there is so

json: adjust definitions alias

JSON Schema suggests[1] using "$defs" rather than "definitions" as
the location for reusable definitions in a schema. While, this
isn't strictly required, there is some implication that using it
lends to better schema validation error reporting[2].

Adjust all the schema files to use "$defs" rather than "definitions".

[1]: https://json-schema.org/understanding-json-schema/structuring#defs
[2]: https://github.com/orgs/json-schema-org/discussions/151

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

show more ...

schemas: Add Inventory.Item.BMC interface

This commit adds the Item.BMC interface as described in [1].

[1] https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/yaml/xyz/openbmc_project/I

schemas: Add Inventory.Item.BMC interface

This commit adds the Item.BMC interface as described in [1].

[1] https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/yaml/xyz/openbmc_project/Inventory/Item/Bmc.interface.yaml

Change-Id: I905fb12434df5280e71d7472666ad646c6b74911
Signed-off-by: Ingrid Chen <ingrid.chen.wiwynn@gmail.com>

show more ...

schemas: virtual sensor: Add Minimum for calculation sensor uses

Minimum has been implemented in phosphor-virtual-sensors [1]. This
commit supports Minimum type in schemas.

[1] https://gerrit.openb

schemas: virtual sensor: Add Minimum for calculation sensor uses

Minimum has been implemented in phosphor-virtual-sensors [1]. This
commit supports Minimum type in schemas.

[1] https://gerrit.openbmc.org/c/openbmc/phosphor-virtual-sensor/+/74099

Signed-off-by: George Liu <liuxiwei@ieisystem.com>
Change-Id: I2370c22c487caaaaaf812b6b91024d82c96388fb

show more ...

configurations: yosemite4: Add PowerState to Medusa Board

To let psusensor get real value of MEDUSA_MBX_ sensors while
corresponding chassis power state is ON.
Add "SlotId" in schemas/legacy.json to

configurations: yosemite4: Add PowerState to Medusa Board

To let psusensor get real value of MEDUSA_MBX_ sensors while
corresponding chassis power state is ON.
Add "SlotId" in schemas/legacy.json to indicate corresponding chassis
slot number.

Test plan:
1. Modify property "CurrentPowerState" to
xyz.openbmc_project.State.Chassis.PowerState.Off, the sensor value of
corresponding slot should be nan.
2. Change property "CurrentPowerState" to
xyz.openbmc_project.State.Chassis.PowerState.Off, the sensor value of
corresponding slot should be real value.

Change-Id: I2d3a5f33a6091b69cb6a78357692e6066a72dcbc
Signed-off-by: Bright Cheng <bright.cheng.wiwynn@gmail.com>

show more ...

configurations: yosemite4: Support second sources Spider board

To support second sources spider board
Test Case: sensor config and sensors can be loaded and read.

Change-Id: Ic28f2fd4a9942ef2b1aa69

configurations: yosemite4: Support second sources Spider board

To support second sources spider board
Test Case: sensor config and sensors can be loaded and read.

Change-Id: Ic28f2fd4a9942ef2b1aa698c6f862b0149584eaf
Signed-off-by: Ian Chien <ianchien.wiwynn@gmail.com>

show more ...

configurations: yosemite4: Set fan current sensors max value

Set fan current sensors max value to an appropriate value.
Otherwise, fan current sensors value might remain unchanged when the fan
maint

configurations: yosemite4: Set fan current sensors max value

Set fan current sensors max value to an appropriate value.
Otherwise, fan current sensors value might remain unchanged when the fan
maintains a constant speed.

Test Case: Maxvalue is set and can be read from PSU sensor service.

Change-Id: I1b63eca5b8a16bc1babfb068ab764722f15f421d
Signed-off-by: Ian Chien <ianchien.wiwynn@gmail.com>

show more ...

schema: Add physical topology fields

Add ConnectsToType and PowerPort to the schema. Code support was added
awhile ago with
https://gerrit.openbmc.org/c/openbmc/entity-manager/+/68030 and
https://g

schema: Add physical topology fields

Add ConnectsToType and PowerPort to the schema. Code support was added
awhile ago with
https://gerrit.openbmc.org/c/openbmc/entity-manager/+/68030 and
https://gerrit.openbmc.org/c/openbmc/entity-manager/+/57133.

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

show more ...

configurations: yosemite4: Support second sources fan board

Support second sources fan board config.
Test case: Fan board config can be loaded and fan sensors can be read.

Change-Id: I7c67f782f45bd

configurations: yosemite4: Support second sources fan board

Support second sources fan board config.
Test case: Fan board config can be loaded and fan sensors can be read.

Change-Id: I7c67f782f45bddbfa034e35ecd1b01dba259c686
Signed-off-by: Ian Chien <ianchien.wiwynn@gmail.com>

show more ...

schemas: Add CheckHysteresisWithSetpoint for PID

Adding CheckHysteresisWithSetpoint, an optional boolean parameter,
which has already been implemented and merged:
https://gerrit.openbmc.org/c/openbm

schemas: Add CheckHysteresisWithSetpoint for PID

Adding CheckHysteresisWithSetpoint, an optional boolean parameter,
which has already been implemented and merged:
https://gerrit.openbmc.org/c/openbmc/phosphor-pid-control/+/58009

And changed the naming in:
https://gerrit.openbmc.org/c/openbmc/phosphor-pid-control/+/71460

Change-Id: Iee6a12c9f3510fb9ba4a886c071cd85a358156e5
Signed-off-by: Delphine CC Chiu <Delphine_CC_Chiu@wiwynn.com>

show more ...

schemas: Ease Exposes constraint to "anyOf"

Allow schemas with optional properties to alias without error.

Without this change exposing an `MCTPI2CTarget` _without_ the _optional_
`StaticEndpointID

schemas: Ease Exposes constraint to "anyOf"

Allow schemas with optional properties to alias without error.

Without this change exposing an `MCTPI2CTarget` _without_ the _optional_
`StaticEndpointID` property results in the following validation error:

```
{'Bus': '$bus', 'Exposes': [{'Address': '$address', 'Bus': '$bus', 'Name': 'NVMe $index FRU', 'Type': 'EEPROM'}, {'Address': '0x1d', 'Bus': '$bus', 'Name': 'NVMe MI', 'Type': 'MCTPI2CTarget'}], 'Logging': 'Off', 'Name': 'NVMe $index', 'Probe': "xyz.openbmc_project.FruDevice({'PRODUCT_PART_NUMBER': '^Micron_7450_.*'})", 'Type': 'NVMe', 'xyz.openbmc_project.Inventory.Decorator.Asset': {'Manufacturer': '$PRODUCT_MANUFACTURER', 'Model': '7450', 'PartNumber': '$PRODUCT_PART_NUMBER', 'SerialNumber': '$PRODUCT_SERIAL_NUMBER'}, 'xyz.openbmc_project.Inventory.Item.Chassis': {}} is not valid under any of the given schemas
```

This error is not particularly intuitive to me. However.

Experience shows that specifying the `StaticEndpointID` property on the
node in question resolves the issue, but requiring it be specified is
not in the spirit of it being an optional property.

Alternatively, reducing the `oneOf` constraint to `anyOf` in the
`EMExposesElement` schema also resolves the error, without requiring
that `StaticEndpointID` be specified.

The working hypothesis is that an `EMExposesElement` node can validate
under the legacy schema with the same the set of properties specified
by the `MCTPI2CTarget` schema if the node is specified without
`StaticEndpointID`. The node effectively aliases to multiple schemas,
which violates the `oneOf` constraint.

Perhaps a longer-term solution is to more rigorously specify valid
device schemas for use in board configs so that we can eventually remove
the legacy schema. A possible source of inspiration is the devicetree
org's use of jsonschema for specifying and validating devicetrees:

https://github.com/devicetree-org/dt-schema/

Change-Id: Iabd445365637f8c0ce58d4a6bafb654fe17caf2d
Signed-off-by: Andrew Jeffery <andrew@codeconstruct.com.au>

show more ...

configurations: harma_mb: Add Power State

The MB_P1V8_CPU_RT_VOLT_V is DC sensor, so
add power status to avoid touch threshold.

Change-Id: Idfa1def185e1886f436ff7c9268845cb95963d35
Signed-off-by: P

configurations: harma_mb: Add Power State

The MB_P1V8_CPU_RT_VOLT_V is DC sensor, so
add power status to avoid touch threshold.

Change-Id: Idfa1def185e1886f436ff7c9268845cb95963d35
Signed-off-by: Peter Yin <peter.yin@quantatw.com>

show more ...

schemas: Add BuildDate property

This commit adds property `BuildDate` under under interface
`xyz.openbmc_project.Inventory.Decorator.Asset` as described in [1].

[1] https://github.com/openbmc/phosp

schemas: Add BuildDate property

This commit adds property `BuildDate` under under interface
`xyz.openbmc_project.Inventory.Decorator.Asset` as described in [1].

[1] https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/yaml/xyz/openbmc_project/Inventory/Decorator/Asset.interface.yaml

Change-Id: Idde43c1d86967dc9beb67acf795429002d7e9bb8
Signed-off-by: Yi-Shum <EasonChen1@quantatw.com>

show more ...

Revert "Add mctp eids configuration for Yosemite 4"

This reverts commit 6fa0602db8250905808991e5f7206151dd28b346.

MCTP support in the backend is nowhere near functional, or complete, as
discussions

Revert "Add mctp eids configuration for Yosemite 4"

This reverts commit 6fa0602db8250905808991e5f7206151dd28b346.

MCTP support in the backend is nowhere near functional, or complete, as
discussions on discord and gerrit[1] make clear.

The tested statement on this patch wasn't really acceptable, and while
normally it doesn't matter what configurations someone sets, they should
at least have code backing them that works.

Therefore, reverting this patch until here are actually MCTP capable
backends, and we've resolved the discussion around MCTP static EID
assignment.

[1] https://gerrit.openbmc.org/c/openbmc/entity-manager/+/69600

Change-Id: Idc0e3c31f7683fd5ac968ca18d1b7239e8bb0c77

show more ...

schemas: Add SparePartNumber property

This commit adds property `SparePartNumber` under under interface
`xyz.openbmc_project.Inventory.Decorator.Asset` as described in [1].

[1] https://github.com/o

schemas: Add SparePartNumber property

This commit adds property `SparePartNumber` under under interface
`xyz.openbmc_project.Inventory.Decorator.Asset` as described in [1].

[1] https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/yaml/xyz/openbmc_project/Inventory/Decorator/Asset.interface.yaml

Change-Id: Id3c70edf0939404a25fd218190a044e1768a0ae0
Signed-off-by: Delphine CC Chiu <Delphine_CC_Chiu@wiwynn.com>

show more ...

configurations: Add IBM's BlueRidge chassis

These chassis are similar enough to the Rainier ones that the Rainier
compatible names can be at the bottom of the compatible list. This way
code that ne

configurations: Add IBM's BlueRidge chassis

These chassis are similar enough to the Rainier ones that the Rainier
compatible names can be at the bottom of the compatible list. This way
code that needs the name but doesn't need to tell the difference between
a Rainier and a BlueRidge doesn't have to change anything.

The IBMCompatibleSystem interface is being deprecated in favor of the
Decorator.Compatible one, but not all of the code has been changed over
yet so just use both for now.

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

show more ...

configurations: Add IBM's Fuji chassis

This chassis is similar enough to the Everest one that the Everest
compatible names can be at the bottom of the compatible list. This way
code that needs the

configurations: Add IBM's Fuji chassis

This chassis is similar enough to the Everest one that the Everest
compatible names can be at the bottom of the compatible list. This way
code that needs the name but doesn't need to tell the difference between
an Everest and a Fuji doesn't have to change anything.

The IBMCompatibleSystem interface is being deprecated in favor of the
Decorator.Compatible one, but not all of the code has been changed over
yet so just use both for now.

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

show more ...

schemas: Add Inventory.Item.NetworkInterface

For phosphor-networkd's sync-mac feature [1] to work,
phosphor-networkd must be able to find an object with
xyz.openbmc_project.Inventory.Item.NetworkInt

schemas: Add Inventory.Item.NetworkInterface

For phosphor-networkd's sync-mac feature [1] to work,
phosphor-networkd must be able to find an object with
xyz.openbmc_project.Inventory.Item.NetworkInterface interface.

This commit adds the property `MACAddress` under the interface
`xyz.openbmc_project.Inventory.Item.NetworkInterface` to the
openbmc-dbus.json schema, and adds the interface to under
"EMConfig"/"properties" in global.json to expose the Board's MAC
Address to D-Bus.

Tested:
Add below config to Mt.Mitchell BMC board's EM configuration:
"xyz.openbmc_project.Inventory.Item.NetworkInterface": {
"MACAddress": "$BOARD_INFO_AM1"
}
=> Successfully pass CI build

$ busctl get-property xyz.openbmc_project.EntityManager \
/xyz/openbmc_project/inventory/system/board/Mt_Mitchell_BMC \
xyz.openbmc_project.Inventory.Item.NetworkInterface MACAddress
s "xx:xx:xx:xx:xx:xx"

=> phosphor-network-manager manages to get MAC address from inventory on
first boot, or when FORCE_SYNC_MAC_FROM_INVENTORY is set

$ journalctl | grep -i network
...
phosphor-network-manager: Check VPD for MAC: Force sync enabled
phosphor-network-manager: Registering the Inventory Signals Matcher
phosphor-network-manager: Setting MAC xx:xx:xx:xx:xx:xx on interface
eth0
...

$ busctl get-property xyz.openbmc_project.Network \
/xyz/openbmc_project/network/eth0 \
xyz.openbmc_project.Network.MACAddress MACAddress
s "xx:xx:xx:xx:xx:xx"

[1]: https://github.com/openbmc/phosphor-networkd/commit/cc099a855ab517deb563ceb6821a8a414362132e

Signed-off-by: Chau Ly <chaul@amperecomputing.com>
Change-Id: I2b9ea2a250e3b98d811154955e09130a00682baf

show more ...