PSU Sensors - Associations
Lei YU
mine260309 at gmail.com
Thu Oct 24 13:03:59 AEDT 2019
On Thu, Oct 24, 2019 at 1:39 AM Patrick Venture <venture at google.com> wrote:
>
> So, I flipped the association interface addition and the property
> initialization to match other sensors, and then it started working. I
> was curious if you had any suggestions on how to find the matching
> sensor given the paths, for instance:
>
> busctl get-property xyz.openbmc_project.PSUSensor
> /xyz/openbmc_project/sensors/temperature/alt2_Temperature
> xyz.openbmc_project.Association.Definitions Associations
> a(sss) 1 "chassis" "all_sensors"
> "/xyz/openbmc_project/inventory/system/board/Altie"
>
> busctl tree --no-pager xyz.openbmc_project.EntityManager|grep Altie
> |-/xyz/openbmc_project/inventory/system/board/Altie
> | |-/xyz/openbmc_project/inventory/system/board/Altie/al_temp_0
> | |-/xyz/openbmc_project/inventory/system/board/Altie/al_temp_1
> | |-/xyz/openbmc_project/inventory/system/board/Altie/al_temp_2
> | `-/xyz/openbmc_project/inventory/system/board/Altie/alt1
>
> No alt2 -- so how do I know this? I can walk every subordinate object
> to find the name match, but I was curious if you had a faster idea?
It looks like buggy, I think mapper shall make sure the association
object is created only when the associated object exists.
@Matt Spinler could you confirm that?
More information about the openbmc
mailing list