tree 7b6e312ab1cace6334a2d57542a3209e56fc144c
parent 6e6618fa09d9ff873999822cbfc982e6a6a419e8
author Patrick Rudolph <patrick.rudolph@9elements.com> 1712753495 +0200
committer Zhikui Ren <zhikui.ren@intel.com> 1720797742 +0000

PSUSensor: Fix CPU presence detection

Currently the CPU presence, indicated by 'CPURequired' property, is
board specific and there are boards making use of 0 based and boards
making use of 1 based CPU indices. It really doesn't matter as long
as the inventory uses the same indices and the inventory is board
specific as well.

Within dbus-sensors the indices read from the inventory are assumed
to be 0 based in one place and 1 based in another place.

This patch addresses CPUs that define the CPURequired property. CPUs
that don't have it were and are still unaffected and behavior is still
the same.

For CPUs that define the value, it depends when the CPU presence was
updated on dbus and when psusensors service was started. It's actually
undefined behavior since dbus-sensors race with the CPU presence
detection service.

- Fix that by always using the actual index read from the inventory,
  making dbus-sensors consistent within itself and support 0 and 1 based
  entity-manager configurations.
- Fix parsing intelcpusensor provided presence since it has an
  underscore between 'cpu' and the digit.

Fixes PSU sensors missing for CPU0 when psusensors was started after
the CPU presence was updated on dbus and the board had 0 based CPU
indices in entity-manager configuration.

This change might regress on platforms when both conditions are true:
- psusensors was started after CPU presence was updated on dbus
- that use mixed indices (0 and 1 based) in inventory and
  entity-manager configuration

Change-Id: Ieeb5989ef819f2d0a4a2aa9b593cb25b30e0194e
Signed-off-by: Patrick Rudolph <patrick.rudolph@9elements.com>