tree 8bc2acf0c41f4e245cd48ce118d18c12a3980ede
parent 39bd2ea553ea2434cad27452c45015cee03bd61f
author Pavithra Barithaya <pavithra.b@ibm.com> 1684405224 -0500
committer Andrew Jeffery <andrew@aj.id.au> 1686618530 +0930

pdr: Add APIs for creating and locating remote PDRs

In the current state, the tree_find() and tree_add() utilities work by
replacing the existing container ID that comes from the remote
endpoints. But we need the remote container ID when we do the PDR
normalization (merging) in BMC.

Two boolean properties are introduced:

* is_remote: used to indicate if the entity is BMC owned or of remote
  endpoint owned.

* is_update_container_id: used to indicate if the container id of the
  entity needs to be updated or not.

We handle 3 different combinations,

1. Both are false - when it is the parent node in the tree
   example: - https://github.com/ibm-openbmc/pldm/blob/1050/
   libpldmresponder/pdr_state_sensor.hpp#L136

2. is_remote is false and update_container_id is true - when it is
   a BMC entity but we have a container id change needed.
   example: - https://github.com/ibm-openbmc/pldm/blob/1050/
   libpldmresponder/fru.cpp#L130

3. is_remote is true and update_container_id is false - In IBM
   PLDM stack talks to two different remote firmware implementations
   over PLDM, and we had a conflicting requirement to not merge the
   container ID from one endpoint but merge the container ID from
   another endpoint. Example: -https://github.com/ibm-openbmc/
   pldm/blob/1050/host-bmc/host_pdr_handler.cpp#L509

Change-Id: I8541b76aa46ba23172ffbc4d72e686909b7147fc
Signed-off-by: Pavithra Barithaya <pavithra.b@ibm.com>
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>