#
8bd711ed |
| 29-Apr-2024 |
Archana Kakani <archana.kakani@ibm.com> |
Inventory-item: Add PCIe Switch interface
Add association between pcie switch to pcie slots
PCIe switches enable the expansion of the system's I/O (Input/Output) capabilities, so adding optional as
Inventory-item: Add PCIe Switch interface
Add association between pcie switch to pcie slots
PCIe switches enable the expansion of the system's I/O (Input/Output) capabilities, so adding optional association between PCIe Switch and PCIe Slots.
Change-Id: I66a26a85ef9df11fac245c60872d4daf191c2b09 Signed-off-by: Archana Kakani <archana.kakani@ibm.com>
show more ...
|
#
3f8d0197 |
| 17-Jul-2023 |
Gunnar Mills <gmills@us.ibm.com> |
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 ...
|
#
8daf5ff7 |
| 13-Jul-2023 |
Patrick Williams <patrick@stwcx.xyz> |
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 ...
|
#
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 ...
|
#
453957cd |
| 31-Mar-2022 |
Zhenwei Chen <zhenweichen0207@gmail.com> |
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 ...
|
#
8da396ca |
| 14-Mar-2022 |
Patrick Williams <patrick@stwcx.xyz> |
yaml: format with prettier
Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I193f690f3612fe72ec69030f81f4d5096a761601
|
#
df557043 |
| 04-Oct-2021 |
Brad Bishop <bradleyb@fuzziesquirrel.com> |
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 ...
|
#
b1b4d261 |
| 05-Jun-2021 |
William A. Kennington III <wak@google.com> |
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 ...
|