tree 97c098ffa5df9b255836118a77b06693993fe313
parent 7fd1de390723586dd94bd0b0119f8273d20ff46e
author Brad Bishop <bradleyb@fuzziesquirrel.com> 1633377071 -0400
committer Patrick Williams <patrick@stwcx.xyz> 1634939191 +0000

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>