Cpu/PCIeSlot: Add {connecting, connected_to}

https://gerrit.openbmc.org/c/openbmc/phosphor-dbus-interfaces/+/64951
removes the current associated_pcie_slots, upstream_processor
association.

This co

Cpu/PCIeSlot: Add {connecting, connected_to}

https://gerrit.openbmc.org/c/openbmc/phosphor-dbus-interfaces/+/64951
removes the current associated_pcie_slots, upstream_processor
association.

This commit adds that association back but with an existing association.
Redfish is adding this link to the PCIeDevice so will have to do
something like Cpu -> Connected_to -> PCIeSlot -> Containing ->
PCIeDevice to fill this out in bmcweb. If instead we put this on
PCIeDevice wouldn't be able to have this link for empty PCIeSlots.

[1] was the original commit for Cpu, PCIeDevice association.

https://gerrit.openbmc.org/c/openbmc/bmcweb/+/61509 is the commit adding
this Link to Redfish, it should be refreshed with this newly named
association.

Redfish describes this as "An array of links to the processors that are
directly connected or directly bridged to this PCIe slot."

Took descriptions from [2].

[1] https://github.com/openbmc/phosphor-dbus-interfaces/commit/df55704398ec8fc3cc608206f05a2226f134c786
[2] https://github.com/openbmc/phosphor-dbus-interfaces/commit/df32eb57476e86044a996c5f2b6765a772c10de4

Change-Id: I7a5be817b565de035e6166b07743f0ec8e919950
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>

show more ...

cpu/pcie: remove deprecated association name

There are currently no users of this association in the OpenBMC
organization and the name chosen here does not match the association
naming design. Remo

cpu/pcie: remove deprecated association name

There are currently no users of this association in the OpenBMC
organization and the name chosen here does not match the association
naming design. Remove these associations.

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

show more ...

Cpu: Convert `Step` default value to maxint

https://gerrit.openbmc.org/c/openbmc/bmcweb/+/57143/3/redfish-core/lib/processor.hpp
makes the bmcweb ignore `Step` if its value is default (0 in this cas

Cpu: Convert `Step` default value to maxint

https://gerrit.openbmc.org/c/openbmc/bmcweb/+/57143/3/redfish-core/lib/processor.hpp
makes the bmcweb ignore `Step` if its value is default (0 in this case).
For a new processor, it's possible that the stepping is really `0`. In
this case, the `Step` will still be ignored which is not expected.
Changing its default to maxint can avoid this issue.

Change-Id: I0e40c65c943f1deb62b8d81f4b5259385af06700
Signed-off-by: Michael Shen <gpgpgp@google.com>

show more ...

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

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

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

cpu: add family default

Implementations need not provide the family information.

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

cpu: add socket default

Implementations need not provide the socket information.

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

Rename the reverse_name to reverse_names in associations.

It will allow two different associations with the same name and
different reverse_names.

For example:
associations:
- name: forward_nam

Rename the reverse_name to reverse_names in associations.

It will allow two different associations with the same name and
different reverse_names.

For example:
associations:
- name: forward_name
reverse_names:
- reverse_name_A
- reverse_name_B
required_endpoint_interfaces:
- endpoint
Will have two associations:
- [forward_name, reverse_name_A, endpoint]
- [forward_name, reverse_name_B, endpoint]

Change-Id: Ia01ae59b7dba1556e7c7f8e56ccede47d623c1a1
Signed-off-by: Zhenwei Chen <zhenweichen0207@gmail.com>

show more ...

yaml: format with prettier

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

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 Model property to Cpu Interface

Follow the Redfish Schema for ProcessorId - EffectiveModel:
https://redfish.dmtf.org/schemas/v1/Processor.v1_12_0.json

Signed-off-by: Brandon Kim <brandonkim@goo

Add Model property to Cpu Interface

Follow the Redfish Schema for ProcessorId - EffectiveModel:
https://redfish.dmtf.org/schemas/v1/Processor.v1_12_0.json

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

show more ...

Add Step and Microcode properties to Cpu Interface

Add Step and Microcode properties to follow the Redfish Schema for
ProcessorId:
https://redfish.dmtf.org/schemas/v1/Processor.v1_12_0.json

Signed-

Add Step and Microcode properties to Cpu Interface

Add Step and Microcode properties to follow the Redfish Schema for
ProcessorId:
https://redfish.dmtf.org/schemas/v1/Processor.v1_12_0.json

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

show more ...

treewide: Create yaml directory

This allows the propagated yamldir paramter to work correctly in
subproject style builds. We don't want other files in the project
conflicting with tools that scan th

treewide: Create yaml directory

This allows the propagated yamldir paramter to work correctly in
subproject style builds. We don't want other files in the project
conflicting with tools that scan the yamldir.

Change-Id: Ie2759c7f3baf399392cdda0e507055ceb262d2e1
Signed-off-by: William A. Kennington III <wak@google.com>

show more ...