Add schema for fw update of Infineon XDPE1X2XX class of devices

Add voltage regulators update schema such as:
- Name - Name of the regulator
- Type - Enum of supported devices or device classes.
- B

Add schema for fw update of Infineon XDPE1X2XX class of devices

Add voltage regulators update schema such as:
- Name - Name of the regulator
- Type - Enum of supported devices or device classes.
- Bus (I2C), which the VR is connected to
- Address(I2C) on the bus.
- FirmwareInfo (VendorIANA, Compatible)

Change-Id: I8a5979afa7cc2558829639fc31a8f6751ea2e161
Signed-off-by: Christopher Meis <christopher.meis@9elements.com>

show more ...

ProductId: remove property

At both the top-level and in Item.Board.Motherboard schemas was a
required property: "ProductId". This property has never been documented
in phosphor-dbus-interfaces and

ProductId: remove property

At both the top-level and in Item.Board.Motherboard schemas was a
required property: "ProductId". This property has never been documented
in phosphor-dbus-interfaces and is only used in exactly 1 OEM IPMI
provider (and no where else)[1, 2]. Strip this unused property out.

Test Plan: entity-manager schema validators pass. Search in code base
for usages.

[1]: https://github.com/openbmc/intel-ipmi-oem/blob/0fcc73f1cf8c486bb8079e68813c239c4cc41bbc/src/oemcommands.cpp#L2929
[2]: https://github.com/search?q=org%3Aopenbmc+%2F%28%3F-i%29ProductId%2F+-repo%3Aopenbmc%2Flinux+-repo%3Aopenbmc%2Fqemu&type=code

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

show more ...

schemas: mctp: Specify descriptions of MCTP I3C targets

8fd7afac1555 ("schemas: Specify descriptions of MCTP I2C targets")
introduced `MCTPI2CTarget` schema. According to this commit, add
`MCTPI3CTa

schemas: mctp: Specify descriptions of MCTP I3C targets

8fd7afac1555 ("schemas: Specify descriptions of MCTP I2C targets")
introduced `MCTPI2CTarget` schema. According to this commit, add
`MCTPI3CTarget` schema to support I3C targets.

Change-Id: I9fd2bcae9f39b9334107fb4b75c3ab5e837e0fec
Signed-off-by: Yikai Tsai <yikai.tsai.wiwynn@gmail.com>

show more ...

leak detector: json schema definition

Define the json schema for leak detector and use it in expose elements
in global.json schema. The leak detector schema defines various
properties such as type,

leak detector: json schema definition

Define the json schema for leak detector and use it in expose elements
in global.json schema. The leak detector schema defines various
properties such as type, subtype, gpio pin name, gpio polarity, etc as
per design https://gerrit.openbmc.org/c/openbmc/docs/+/73152.

Related PR:
https://gerrit.openbmc.org/c/openbmc/phosphor-dbus-interfaces/+/75999

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

show more ...

correct the name of Inventory.Item.Bmc interface

As defined in the PDIs [1], the correct name of this interface is
Inventory.Item.Bmc (not BMC). This commit corrects all configuration
that are using

correct the name of Inventory.Item.Bmc interface

As defined in the PDIs [1], the correct name of this interface is
Inventory.Item.Bmc (not BMC). This commit corrects all configuration
that are using incorrect interface name.

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

Change-Id: Icc9b4b33725999a72cd925fd0f0e5995aacadcdc
Signed-off-by: Thang Tran <thuutran@amperecomputing.com>

show more ...

cable: add cable type and cable decorator

Add cable type to the global schema types and cable decorator with
Length and Type properties.

Change-Id: I5368c16b91c94980be1b10cbfaf7969933e0507e
Signed-

cable: add cable type and cable decorator

Add cable type to the global schema types and cable decorator with
Length and Type properties.

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

show more ...

schemas: Specify descriptions of MCTP I2C targets

6fa0602db825 ("Add mctp eids configuration for Yosemite 4") introduced
an `EndpointId` property for assigning static MCTP endpoint IDs to an
exposed

schemas: Specify descriptions of MCTP I2C targets

6fa0602db825 ("Add mctp eids configuration for Yosemite 4") introduced
an `EndpointId` property for assigning static MCTP endpoint IDs to an
exposed device. This might work in very specific contexts, but
often more information is needed to configure a device for MCTP
communication.

Introduce the `MCTPI2CTarget` schema. Specifying `MCTPI2CTarget`
sets requirements such that a reactor can derive the physical address
encoding required to set up the endpoint.

For now we assume that all I2C controllers enabled for MCTP take the
role of bus owner.

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

show more ...

schemas: Add interfaces for Item.Accelerator and Item.Dimm

This commit add the interfaces as described in [1] and [2].

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

schemas: Add interfaces for Item.Accelerator and Item.Dimm

This commit add the interfaces as described in [1] and [2].

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

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

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

Change-Id: Id4db6ebd599e94ec23f9c5db96fa3e9143619299
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: 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: 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 ...

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 ...

schemas: Add Decorator.Revision interface

This adds property `Version` under `xyz.openbmc_project.Inventory.
Decorator.Revision` as described in [1]

[1] https://github.com/openbmc/phosphor-dbus-int

schemas: Add Decorator.Revision interface

This adds property `Version` under `xyz.openbmc_project.Inventory.
Decorator.Revision` as described in [1]

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

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

show more ...

schemas: Descriptions must be strings

```
$ python3 -c 'import json; import jsonschema; schema = json.load(open("schemas/global.json")); cls = jsonschema.validators.validator_for(schema); cls.check_

schemas: Descriptions must be strings

```
$ python3 -c 'import json; import jsonschema; schema = json.load(open("schemas/global.json")); cls = jsonschema.validators.validator_for(schema); cls.check_schema(schema)'
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/usr/lib/python3/dist-packages/jsonschema/validators.py", line 204, in check_schema
raise exceptions.SchemaError.create_from(error)
jsonschema.exceptions.SchemaError: ['The schema for an entity manager configuration file. An entity ', 'mananger configuration file can consist of a single object, or an ', 'array of objects. Objects must be of type EMConfig.'] is not of type 'string'

Failed validating 'type' in metaschema['properties']['description']:
{'type': 'string'}

On schema['description']:
['The schema for an entity manager configuration file. An entity ',
'mananger configuration file can consist of a single object, or an ',
'array of objects. Objects must be of type EMConfig.']
```

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

show more ...

schemas: Add Common.UUID interface

This adds UUID to under xyz.openbmc_project.Common in
openbmc-dbus.json which property UUID as described in [1].
This also adds xyz.openbmc_project.Common.UUID to

schemas: Add Common.UUID interface

This adds UUID to under xyz.openbmc_project.Common in
openbmc-dbus.json which property UUID as described in [1].
This also adds xyz.openbmc_project.Common.UUID to under
EMConfig in global.json so that the interface can be
configured in the board's Entity Manager configuration file.

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

Signed-off-by: Hieu Huynh <hieuh@os.amperecomputing.com>
Change-Id: I62492928c2268c88754b4946d307022ba63e4c01

show more ...

schemas: Add Decorator.Slot interface

This commit adds `Decorator.Slot` in openbmc-dbus.json with property
`SlotNumber` as described in
https://github.com/openbmc/phosphor-dbus-interfaces/blob/maste

schemas: Add Decorator.Slot interface

This commit adds `Decorator.Slot` in openbmc-dbus.json with property
`SlotNumber` as described in
https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/yaml\
/xyz/openbmc_project/Inventory/Decorator/Slot.interface.yaml.

This commit also adds `Decorator.Slot` to EMConfig so that the
interface can be configured in Entity Manager configuration file.

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

show more ...

schemas: Add Decorator.Compatible interface

This commit adds Compatible to under xyz.openbmc_project.Decorator in
openbmc-dbus.json with property Names as described in
https://github.com/openbmc/pho

schemas: Add Decorator.Compatible interface

This commit adds Compatible to under xyz.openbmc_project.Decorator in
openbmc-dbus.json with property Names as described in
https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/yaml/\
xyz/openbmc_project/Inventory/Decorator/Compatible.interface.yaml. This
commit also adds xyz.openbmc_project.Inventory.Decorator.Compatible to
under EMConfig in global.json so that the interface can be configured in
the board's Entity Manager configuration file. The usage of this
interface was mentioned in
https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/yaml/\
xyz/openbmc_project/Software/README.md#compatibility.

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

show more ...

schema: ibm: add default power mode props. schema

Add PowerModeProperties schema to define the factory default power mode
properties of a system:
- Power Mode
- Idle Power Saver Parameters

All of t

schema: ibm: add default power mode props. schema

Add PowerModeProperties schema to define the factory default power mode
properties of a system:
- Power Mode
- Idle Power Saver Parameters

All of these parameters are part of the version 2021.2 Redfish Schema
Supplement under the ComputerSystem 1.16.0 schema:
For details on the values and descriptions, see the PowerMode and
IdlePowerSaver schemas in the Redfish documentation:
https://www.dmtf.org/sites/default/files/standards/documents/DSP0268_2021.2.pdf

These are the factory default values as defined by the system architect.
All of these parameters are system-wide parameters and are used to
define the operation of that system as it relates to power.

These are the values will be used the first time a system is powered on.
They can also be used if the customer wants to restore these settings to
their factory defaults.

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

show more ...

aggregation: add satellite controller schema

This schema will be utilized to add remote satellite controllers to a
users system.

bmcweb already has extensive support for utilizing this object. More

aggregation: add satellite controller schema

This schema will be utilized to add remote satellite controllers to a
users system.

bmcweb already has extensive support for utilizing this object. More
information can be found in the following:
https://gerrit.openbmc.org/c/openbmc/bmcweb/+/57925

Tested:
- Confirmed a system utilizing new schema worked as expected

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

show more ...

Add FieldReplaceable field in twinlake.json

Added xyz.openbmc_project.Inventory.Decorator.Replaceable interface in
twinlake.json configuration file and FieldReplaceable boolean field.
This will disp

Add FieldReplaceable field in twinlake.json

Added xyz.openbmc_project.Inventory.Decorator.Replaceable interface in
twinlake.json configuration file and FieldReplaceable boolean field.
This will display FieldReplaceable in Redfish under chassis path.

Tested: Tested and verified in Facebook YosemiteV2 platform.

Change-Id: Idae9f16d14ef1938a0ec42f80d62a660e0844096
Signed-off-by: Kumar Thangavel <thangavel.k@hcl.com>

show more ...

format: reformat with latest openbmc-build-scripts

Run all the latest formatters from openbmc-build-scripts. Disable
prettier on the configurations subdirectory because these are
script-formatted a

format: reformat with latest openbmc-build-scripts

Run all the latest formatters from openbmc-build-scripts. Disable
prettier on the configurations subdirectory because these are
script-formatted already with the repo-local `format-code` extension.

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

show more ...

schemas: use lower_snake_case for filenames

To be consistent with lower_snake_case source code filenames, use
lower_snake_case for schema file names as well.

Signed-off-by: Brad Bishop <bradleyb@fu

schemas: use lower_snake_case for filenames

To be consistent with lower_snake_case source code filenames, use
lower_snake_case for schema file names as well.

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

show more ...