tree 8dffe6274af63a7a9846cac8a6bbaad4f1eb7f78
parent f3e6ff19da471f8dbdd31e17e2636819dfdfec9a
author Willy Tu <wltu@google.com> 1665521579 +0000
committer Patrick Williams <patrick@stwcx.xyz> 1666632215 +0000

mapper: Add Associated subtree method definition

Create new mapper function to make subtree call and association call at
the same time. With the association definitition, we will have more
endpoints to fetch and verify that it is actually the resource that we
are looking for. We need to verify that it has the expected interface to
confirm that it is right device. In the current workflow this will take
two dbus calls to the mapper to get the assocation and the subtree.

This change aims to reduce that down to one by combination the two
operations. It will not sigificant performance increase for the daemons,
but it can help reduce the load on the dbus-broker.service.

Tested:
```
Normal Call:
busctl call   "xyz.openbmc_project.ObjectMapper" \
    "/xyz/openbmc_project/object_mapper" \
    "xyz.openbmc_project.ObjectMapper" "GetSubTreePaths" sias \
     "/xyz/openbmc_project/inventory" 0 1 \
     "xyz.openbmc_project.Inventory.Item.Storage"
as 4 "/xyz/openbmc_project/inventory/storage_0" "/xyz/openbmc_project/inventory/storage_1"
     "/xyz/openbmc_project/inventory/storage_4" "/xyz/openbmc_project/inventory/storage_3"

Associated Call: (Only 0 and 1 is associated to the chassis)
busctl call   "xyz.openbmc_project.ObjectMapper" \
    "/xyz/openbmc_project/object_mapper" \
    "xyz.openbmc_project.ObjectMapper" "GetAssociatedSubTreePaths" ssias \
    "/xyz/openbmc_project/inventory/chassis_0/storage" \
     "/xyz/openbmc_project/inventory" 0 1 "xyz.openbmc_project.Inventory.Item.Storage"
as 2 "/xyz/openbmc_project/inventory/storage_0" "/xyz/openbmc_project/inventory/storage_1"
```

Signed-off-by: Willy Tu <wltu@google.com>
Change-Id: I079adf41a5775f80b9c773e8e9e319d46be924ea