Fix format in HwmonMain.cpp to pass format check

Change-Id: I6b39dad6e00e1682cb7ed9bbafcc85999b073c44
Signed-off-by: Michael Shen <gpgpgp@google.com>

Fix PECI client creation flow

This commit fixes the PECI client creation flow to make it retry
the creation when the client is not exposed correctly.

Change-Id: I779cc1865e9ebb8fff90efcbac4503379ca

Fix PECI client creation flow

This commit fixes the PECI client creation flow to make it retry
the creation when the client is not exposed correctly.

Change-Id: I779cc1865e9ebb8fff90efcbac4503379cadea5a
Signed-off-by: Jae Hyun Yoo <jae.hyun.yoo@intel.com>
Signed-off-by: AppaRao Puli <apparao.puli@intel.com>
Signed-off-by: Oleksandr Shulzhenko <oleksandr.shulzhenko.viktorovych@intel.com>

show more ...

IntelCPUSensor: Use libpeci when communicating via peci-legacy

When using peci-legacy the general approach is to use libpeci as
the middleware to communicate with peci core from userspace.
Integrate

IntelCPUSensor: Use libpeci when communicating via peci-legacy

When using peci-legacy the general approach is to use libpeci as
the middleware to communicate with peci core from userspace.
Integrate libpeci with IntelCPUSensor and use library functions to issue
peci commands where necessary.

Tested: hwmons are succesfully created in the same way
they were created using ioctl.

Change-Id: I4ecd70e604d447a4066dc5fb8d902992cb97cadf
Signed-off-by: Oleksandr Shulzhenko <oleksandr.shulzhenko.viktorovych@intel.com>

show more ...

clang-tidy: reduce repo-specific flags

Adjust the clang-tidy settings so that it does not need to have
a bunch of values related to the libpeci subproject. In general
we should be ignoring any head

clang-tidy: reduce repo-specific flags

Adjust the clang-tidy settings so that it does not need to have
a bunch of values related to the libpeci subproject. In general
we should be ignoring any header files from any subprojects since
they are not under direct control of the repository-under-test.

Change-Id: I64d4e4bae20ca27aed68081b4270fa0ec8fc0543
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>

show more ...

fansensor: fix fan sensor service crash

fs::canonical can throw exception if the path does not exist,
which can happen for i2c fan type. Check for path exists before the
call.

Tested:
fan sensor se

fansensor: fix fan sensor service crash

fs::canonical can throw exception if the path does not exist,
which can happen for i2c fan type. Check for path exists before the
call.

Tested:
fan sensor service successfully detect i2c fan type and does not crash.

Fixes: 9a472e8 ("detect fan type by matching against 'compatible'")
Signed-off-by: Zhikui Ren <zhikui.ren@intel.com>
Change-Id: I395e4d47b16fc58eba777e88be304bf28993bec3

show more ...

MCUTempSensor: Fix PDB temparature reading show nan

Actually, i2c_smbus_read_word_data() return value is
not mapped correctly. So, fixed i2c_smbus_read_word_data()
return type to signed int32 from i

MCUTempSensor: Fix PDB temparature reading show nan

Actually, i2c_smbus_read_word_data() return value is
not mapped correctly. So, fixed i2c_smbus_read_word_data()
return type to signed int32 from int16_t.

Tested: Verified PDB temperature reading is getting
reported correctly via D-Bus.

Change-Id: I0a00d5b20c0576abe5635e96b3afadc572241f0a
Signed-off-by: Saitwal, Meghan <meghan.saitwal@intel.com>

show more ...

add support for hpe's gxpfan type

Adds basic support for handling HPE's GXPFan sensors

Tested: confirmed that HPE's GXP fans appear in webUI
with this change + appropriate entity-manager config ent

add support for hpe's gxpfan type

Adds basic support for handling HPE's GXPFan sensors

Tested: confirmed that HPE's GXP fans appear in webUI
with this change + appropriate entity-manager config entries

Change-Id: I0e2e3936575881972f536c80ffc2648a2b2a75e6
Signed-off-by: Chris Sides <christopher.sides@hpe.com>

show more ...

use std::map for fantype 'compatible' string checks

Switches to using a map of valid 'compatible'
strings + fanTypes instead of individual 'compatible'
string == conditionals

Tested: confirmed tha

use std::map for fantype 'compatible' string checks

Switches to using a map of valid 'compatible'
strings + fanTypes instead of individual 'compatible'
string == conditionals

Tested: confirmed that HPE's GXP fans appear in webUI
with this change + appropriate entity-manager config entries

Change was made based on Andrew J's comment @
https://gerrit.openbmc.org/c/openbmc/dbus-sensors/+/62008/comment/cf2f99d8_a3d1d111/

Change-Id: Ia74b1617d95148a9e6a08865146d000c06a65b47
Signed-off-by: Chris Sides <christopher.sides@hpe.com>

show more ...

detect fan type by matching against 'compatible'

Switches fan-type detection to key off well-known 'compatible' strings,
as documented
@ https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linu

detect fan type by matching against 'compatible'

Switches fan-type detection to key off well-known 'compatible' strings,
as documented
@ https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/hwmon/

Change was created in response to the comment:
"I'd much prefer we query compatible attribute through the
of_node symlink" as discussed with Andrew J. and Ed T. in the
gerrit review
@ https://gerrit.openbmc.org/c/openbmc/dbus-sensors/+/58458

Tested: confirmed fans appear in WebUI only when
valid 'compatible' strings are found

Change-Id: Ifae4abc64288e84023c045fc8b2c7a4f0d1b8498
Signed-off-by: Chris Sides <christopher.sides@hpe.com>

show more ...

Deassert thresholds when sensor is unavailable

Some dbus-sensors applications allows you to specify "PowerState"
parameter for its sensors in the configarition. With this parameter
sensor is sampled

Deassert thresholds when sensor is unavailable

Some dbus-sensors applications allows you to specify "PowerState"
parameter for its sensors in the configarition. With this parameter
sensor is sampled/checked against its thresholds only if certain
system conditions are met.
Therefore if sensor becomes unavailable because of the "PowerState"
parameter, all its threshold states must be deasserted.

Tested: tested on the AMD DaytonaX CRB. It is a 2-socket board. For
the test only 1 CPU was installed. In this case voltage sensors that
measure voltages for CPU2 and configured with '"PowerState": "On"'
assert their thresholds when the system is powered on.
Before the patch even if the system is powered off after that, these
voltage sensors stay with the asserted thresholds. Because of that
webui will continue to displays these sensors with a 'Critical' status.
After the patch if system is powered off, the voltage sensors deasset
all their thresholds and the sensors correctly change their status to
'OK' in webui.

Change-Id: Id6a33f15c18ca7aa30e8c449ab9c9e239673dd1f
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>

show more ...

PSUSensor: Add new PMBUS chip TDA38640

Add PMBUS compatible TDA38640 to the supported devices.
The chip has been added to hwmon-next on Sun, 29 Jan 2023.

Change-Id: Ie095359fd9ce223b41eccbc639b6722

PSUSensor: Add new PMBUS chip TDA38640

Add PMBUS compatible TDA38640 to the supported devices.
The chip has been added to hwmon-next on Sun, 29 Jan 2023.

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

show more ...

PSUSensor: Add more labels

The XDPE11280 exposes two PMBUS VIN channels as it has two
independent outputs. Add those labels to be able to read the
input voltage on that chip.

Added labels:
- vin1
-

PSUSensor: Add more labels

The XDPE11280 exposes two PMBUS VIN channels as it has two
independent outputs. Add those labels to be able to read the
input voltage on that chip.

Added labels:
- vin1
- vin2

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

show more ...

Fix for CpuSensor warning observed after bmc reset

In case of peci cdev open failed we are now exiting CpuSensor service
with error code. Since this is unexpected behaviour we will now retry
the det

Fix for CpuSensor warning observed after bmc reset

In case of peci cdev open failed we are now exiting CpuSensor service
with error code. Since this is unexpected behaviour we will now retry
the detectCpu function.

Tested: No warning observed on platform.

Change-Id: Icdf71b674cbdfcc70ca3bfae6d7863a04783d4ca
Signed-off-by: Jakub Nowacki <jakubx.nowacki@intel.com>

show more ...

intrusionsensor: Update object path

intrusionsensor is added to ObjectManager under the path
"/xyz/openbmc_project/sensors", but is registered under the object path
"/xyz/openbmc_project/Intrusion/C

intrusionsensor: Update object path

intrusionsensor is added to ObjectManager under the path
"/xyz/openbmc_project/sensors", but is registered under the object path
"/xyz/openbmc_project/Intrusion/Chassis_Intrusion". This makes it unable
to be found by other services via ObjectMapper's methods. Moreover,
intrusionsensor is not really a sensor in the dbus definitions (it does
not implement sensor interfaces), and the used interface is defined in
the Chassis folder in phosphor-dbus-interfaces. Therefore, this commit
adds it to ObjectManager under "/xyz/openbmc_project/Chassis", changes
the object path to "/xyz/openbmc_project/Chassis/Intrusion" in
dbus-sensors intrusionsensor.

Tested:
Object path for intrusionsensor can be received via GetSubTree:
$ busctl call -j xyz.openbmc_project.ObjectMapper \
/xyz/openbmc_project/object_mapper xyz.openbmc_project.ObjectMapper \
GetSubTree sias /xyz/openbmc_project 0 1 \
xyz.openbmc_project.Chassis.Intrusion

"/xyz/openbmc_project/Chassis/Intrusion" : {
"xyz.openbmc_project.IntrusionSensor" : [
"xyz.openbmc_project.Chassis.Intrusion"
]
}

Signed-off-by: Chau Ly <chaul@amperecomputing.com>
Change-Id: Iaf0369a9ee4ddf626968b4961941ae7025c83952

show more ...

IntelCPUSensor: Fix threshold hysteresis is nan

Threshold's hysteresis is set to nan as default in constructor, the
function parseThresholdsFromAttr will forcely update threshold's
hysteresis as nan

IntelCPUSensor: Fix threshold hysteresis is nan

Threshold's hysteresis is set to nan as default in constructor, the
function parseThresholdsFromAttr will forcely update threshold's
hysteresis as nan[1].

Because IntelCPUSensor will run parseThresholdsFromAttr in
IntelCPUSensor::handleResponse, this nan will not be updated by
hysteresisTrigger in function setInitialProperties[2].

When the threshold's hysteresis is always nan, the condition of
deassert will never be satisfied.

Update theshold's hysteresis to be 0 base on max/min chosed in
IntelCPUSensor[3] because the function parseThresholdsFromAttr is only
used by IntelCPUSensor for now.

Refs:
```
[1] https://github.com/openbmc/dbus-sensors/blob/master/src/Thresholds.cpp#L519
[2] https://github.com/openbmc/dbus-sensors/blob/master/src/sensor.hpp#L277
[3] https://github.com/openbmc/dbus-sensors/blob/master/src/IntelCPUSensor.cpp#L46
```

Tested:
DIMM_B0_CPU0 sensor with threshold 93/95 as UWT/UCT, respectively.
Enable flag 'insecure-sensor-override' and then set sensor value to
100 on dbus and then set sensor value to 50 on dbus.

Before change:
```
root@qbmc:~# busctl introspect xyz.openbmc_project.IntelCPUSensor /xyz/openbmc_project/sensors/temperature/DIMM_B0_CPU0
NAME TYPE SIGNATURE RESULT/VALUE FLAGS
org.freedesktop.DBus.Introspectable interface - - -
.Introspect method - s -
org.freedesktop.DBus.Peer interface - - -
.GetMachineId method - s -
.Ping method - - -
org.freedesktop.DBus.Properties interface - - -
.Get method ss v -
.GetAll method s a{sv} -
.Set method ssv - -
.PropertiesChanged signal sa{sv}as - -
xyz.openbmc_project.Association.Definitions interface - - -
.Associations property a(sss) 1 "chassis" "all_sensors" "/xyz/openb... emits-change
xyz.openbmc_project.Sensor.Threshold.Critical interface - - -
.CriticalAlarmHigh property b true emits-change
.CriticalAlarmLow property b false emits-change
.CriticalHigh property d 95 emits-change writable
.CriticalLow property d nan emits-change writable
xyz.openbmc_project.Sensor.Threshold.Warning interface - - -
.WarningAlarmHigh property b true emits-change
.WarningAlarmLow property b false emits-change
.WarningHigh property d 93 emits-change writable
.WarningLow property d nan emits-change writable
xyz.openbmc_project.Sensor.Value interface - - -
.MaxValue property d 127 emits-change
.MinValue property d -128 emits-change
.Unit property s "xyz.openbmc_project.Sensor.Value.Uni... emits-change
.Value property d 50 emits-change writable
xyz.openbmc_project.State.Decorator.Availability interface - - -
.Available property b true emits-change writable
xyz.openbmc_project.State.Decorator.OperationalStatus interface - - -
.Functional property b true emits-change
```
After:
```
root@qbmc:~# busctl introspect xyz.openbmc_project.IntelCPUSensor /xyz/openbmc_project/sensors/temperature/DIMM_B0_CPU0
NAME TYPE SIGNATURE RESULT/VALUE FLAGS
org.freedesktop.DBus.Introspectable interface - - -
.Introspect method - s -
org.freedesktop.DBus.Peer interface - - -
.GetMachineId method - s -
.Ping method - - -
org.freedesktop.DBus.Properties interface - - -
.Get method ss v -
.GetAll method s a{sv} -
.Set method ssv - -
.PropertiesChanged signal sa{sv}as - -
xyz.openbmc_project.Association.Definitions interface - - -
.Associations property a(sss) 1 "chassis" "all_sensors" "/xyz/openb... emits-change
xyz.openbmc_project.Sensor.Threshold.Critical interface - - -
.CriticalAlarmHigh property b false emits-change
.CriticalAlarmLow property b false emits-change
.CriticalHigh property d 95 emits-change writable
.CriticalLow property d nan emits-change writable
xyz.openbmc_project.Sensor.Threshold.Warning interface - - -
.WarningAlarmHigh property b false emits-change
.WarningAlarmLow property b false emits-change
.WarningHigh property d 93 emits-change writable
.WarningLow property d nan emits-change writable
xyz.openbmc_project.Sensor.Value interface - - -
.MaxValue property d 127 emits-change
.MinValue property d -128 emits-change
.Unit property s "xyz.openbmc_project.Sensor.Value.Uni... emits-change
.Value property d 50 emits-change writable
xyz.openbmc_project.State.Decorator.Availability interface - - -
.Available property b true emits-change writable
xyz.openbmc_project.State.Decorator.OperationalStatus interface - - -
.Functional property b true emits-change
```
and the signal "ThresholdAsserted" for deassert is triggered.

Change-Id: I107a2ac587f5791c47b9e7fd5a7c06ef4a312941
Signed-off-by: Jeff Lin <JeffLin2@quantatw.com>

show more ...

code-format fixes for PSUSensorMain

Accepting code-fromat changes as suggested by build CI following the
latest (as of today) code-format rules.

Change-Id: I0ff61cd6a30dbf15a338889ef5971984260cbc77

code-format fixes for PSUSensorMain

Accepting code-fromat changes as suggested by build CI following the
latest (as of today) code-format rules.

Change-Id: I0ff61cd6a30dbf15a338889ef5971984260cbc77
Signed-off-by: Chris Sides <christopher.sides@hpe.com>

show more ...

psusensor: Add CPU presence detection in psusensor

Add same CPU presence that's in ADCSensorMain into PSUSensorMain

Tested:
Sensors with non-present CPUs are not being added.
Sensors with present C

psusensor: Add CPU presence detection in psusensor

Add same CPU presence that's in ADCSensorMain into PSUSensorMain

Tested:
Sensors with non-present CPUs are not being added.
Sensors with present CPU or no CPURequired field still being added.

Change-Id: I772175a9eb3c0c6337f7fdc79c2de71e19a77349
Signed-off-by: Matt Simmering <matthew.simmering@intel.com>

show more ...

nvmesensor: Use slave address from configuration json

Replace hardcoded slave address with address from the configuration
This patch is for non-compliant nvme devices (e.g.
configurations/nvme_p4000

nvmesensor: Use slave address from configuration json

Replace hardcoded slave address with address from the configuration
This patch is for non-compliant nvme devices (e.g.
configurations/nvme_p4000.json).
Tested: Manually by verifying the slave address in Entity Manager
configuration is used by the nvmesensor binary

Change-Id: I56b8187578c22a9be98ccd2c50a7b9838a087e52
Signed-off-by: Nnamdi Ajah <nnamdi@cloudflare.com>

show more ...

Add Redfish logging for Chassis Intrusion

Add appropriate Redfish Chassis Intrusion logging calls
when there is a change in value

Tested: Toggled Chassis Intrusion jumper on platform and
saw each e

Add Redfish logging for Chassis Intrusion

Add appropriate Redfish Chassis Intrusion logging calls
when there is a change in value

Tested: Toggled Chassis Intrusion jumper on platform and
saw each event in the Redfish event logs

Change-Id: I26f777f7e937d87bf462cf49e8dbfef56b7be46a
Signed-off-by: Matt Simmering <matthew.simmering@intel.com>

show more ...

psusensor: Convert sensorTypes to I2CDeviceTypeMap

Similar to change
https://gerrit.openbmc.org/c/openbmc/dbus-sensors/+/56127.

Tested: same sensors get initialized before and after change.

Change

psusensor: Convert sensorTypes to I2CDeviceTypeMap

Similar to change
https://gerrit.openbmc.org/c/openbmc/dbus-sensors/+/56127.

Tested: same sensors get initialized before and after change.

Change-Id: I57aca3738b01aa22da4dab5d8b1ed251578d9123
Signed-off-by: Matt Simmering <matthew.simmering@intel.com>

show more ...

PSUSensor: Add device type ncp4200

Add device type ncp4200 to the allowed list.

Change-Id: I17f418b924bca26648b97c566afb8c23e398d2ea
Signed-off-by: Glukhov Mikhail <mikl@greenfil.ru>

Add support for slot hot plug/unplug of sdr sensors

Added support for slot hot plug/unplug of sdr sensors in
dbus-sensors and IpmbSensor dbus tree updated accordingly

TESTED : Verified hot plug/unp

Add support for slot hot plug/unplug of sdr sensors

Added support for slot hot plug/unplug of sdr sensors in
dbus-sensors and IpmbSensor dbus tree updated accordingly

TESTED : Verified hot plug/unplug of all hosts sdr sensors
are enabled and tested in Facebook YosemiteV2 platform

Test case 1 : hot unplugged/removed host1

root@yosemitev2:~# busctl tree xyz.openbmc_project.IpmbSensor
`-/xyz
`-/xyz/openbmc_project/sensors
|-/xyz/openbmc_project/sensors/current
| |-/xyz/openbmc_project/sensors/current/2_P1V05PCH_VR_Curr
| |-/xyz/openbmc_project/sensors/current/2_PVCCIN_VR_Curr
| |-/xyz/openbmc_project/sensors/current/2_PVCCIO_VR_Curr
| |-/xyz/openbmc_project/sensors/current/2_PVCCSA_VR_Curr
| |-/xyz/openbmc_project/sensors/current/2_PVDDQ_AB_VR_Curr
| |-/xyz/openbmc_project/sensors/current/2_PVDDQ_DE_VR_Curr
| |-/xyz/openbmc_project/sensors/current/2_PVNN_PCH_VR_Curr
| |-/xyz/openbmc_project/sensors/current/3_P1V05PCH_VR_Curr
| |-/xyz/openbmc_project/sensors/current/3_PVCCIN_VR_Curr
| |-/xyz/openbmc_project/sensors/current/3_PVCCIO_VR_Curr
| |-/xyz/openbmc_project/sensors/current/3_PVCCSA_VR_Curr
| |-/xyz/openbmc_project/sensors/current/3_PVDDQ_AB_VR_Curr
| |-/xyz/openbmc_project/sensors/current/3_PVDDQ_DE_VR_Curr
| |-/xyz/openbmc_project/sensors/current/3_PVNN_PCH_VR_Curr
| |-/xyz/openbmc_project/sensors/current/4_P1V05PCH_VR_Curr
| |-/xyz/openbmc_project/sensors/current/4_PVCCIN_VR_Curr
| |-/xyz/openbmc_project/sensors/current/4_PVCCIO_VR_Curr
| |-/xyz/openbmc_project/sensors/current/4_PVCCSA_VR_Curr
| |-/xyz/openbmc_project/sensors/current/4_PVDDQ_AB_VR_Curr
| |-/xyz/openbmc_project/sensors/current/4_PVDDQ_DE_VR_Curr
| `-/xyz/openbmc_project/sensors/current/4_PVNN_PCH_VR_Curr

Test case 2 : hot unplugged/removed host2

root@yosemitev2:~# busctl tree xyz.openbmc_project.IpmbSensor
`-/xyz
`-/xyz/openbmc_project/sensors
|-/xyz/openbmc_project/sensors/current
| |-/xyz/openbmc_project/sensors/current/1_P1V05PCH_VR_Curr
| |-/xyz/openbmc_project/sensors/current/1_PVCCIN_VR_Curr
| |-/xyz/openbmc_project/sensors/current/1_PVCCIO_VR_Curr
| |-/xyz/openbmc_project/sensors/current/1_PVCCSA_VR_Curr
| |-/xyz/openbmc_project/sensors/current/1_PVDDQ_AB_VR_Curr
| |-/xyz/openbmc_project/sensors/current/1_PVDDQ_DE_VR_Curr
| |-/xyz/openbmc_project/sensors/current/1_PVNN_PCH_VR_Curr
| |-/xyz/openbmc_project/sensors/current/3_P1V05PCH_VR_Curr
| |-/xyz/openbmc_project/sensors/current/3_PVCCIN_VR_Curr
| |-/xyz/openbmc_project/sensors/current/3_PVCCIO_VR_Curr
| |-/xyz/openbmc_project/sensors/current/3_PVCCSA_VR_Curr
| |-/xyz/openbmc_project/sensors/current/3_PVDDQ_AB_VR_Curr
| |-/xyz/openbmc_project/sensors/current/3_PVDDQ_DE_VR_Curr
| |-/xyz/openbmc_project/sensors/current/3_PVNN_PCH_VR_Curr
| |-/xyz/openbmc_project/sensors/current/4_P1V05PCH_VR_Curr
| |-/xyz/openbmc_project/sensors/current/4_PVCCIN_VR_Curr
| |-/xyz/openbmc_project/sensors/current/4_PVCCIO_VR_Curr
| |-/xyz/openbmc_project/sensors/current/4_PVCCSA_VR_Curr
| |-/xyz/openbmc_project/sensors/current/4_PVDDQ_AB_VR_Curr
| |-/xyz/openbmc_project/sensors/current/4_PVDDQ_DE_VR_Curr
| `-/xyz/openbmc_project/sensors/current/4_PVNN_PCH_VR_Curr

Signed-off-by: Kumar Thangavel <thangavel.k@hcl.com>
Change-Id: I1ac62c0ac374004b33104e2d4fb0d743d76b83b9

show more ...

dbus-sensors: Associate PSU sensors correctly

PSUSensors associate sensors with the inventory item that defined its
config in EM. It also needs to associate the sensor with the containing
chassis. T

dbus-sensors: Associate PSU sensors correctly

PSUSensors associate sensors with the inventory item that defined its
config in EM. It also needs to associate the sensor with the containing
chassis. Today, it associates the sensor with the object that defined
the config *and* with any all objects that implement Inventory.System.
In the situation where the sensor is defined in a PowerSupply
configuration, this works because the PowerSupply itself is not a
chassis. As a result, the "chassis" <-> "all_sensors" association
pointing to the power supply inventory object is ignored. However, if
the power supply is itself a chassis, this sensor is now associated with
at least two different chassis, which results in it showing up in two
different Redfish resources in bmcweb (the defining chassis and the
system chassis).

This change uses the defining object as the chassis if it is actually a
chassis or board (i.e. represented as a Redfish Chassis resource). If it
is not, it uses the system chassis. This will not work correctly if
there is more than one chassis which also implements Inventory.System,
but we presently assume that there is only one system in a number of
places. This should be fixed when we add support for multiple Systems.

Tested: Sensors on PSUs that are also chassis have a single "chassis"
association:

busctl get-property \
xyz.openbmc_project.PSUSensor \
/xyz/openbmc_project/sensors/power/hotswap_in_Input_Power \
xyz.openbmc_project.Association.Definitions Associations
a(sss) 2 "inventory" "sensors" "/xyz/openbmc_project/inventory/system/board/psu_chassis" "chassis" "all_sensors" "/xyz/openbmc_project/inventory/system/board/psu_chassis"

Changed PSU to PowerSupply type:
busctl get-property \
xyz.openbmc_project.PSUSensor \
/xyz/openbmc_project/sensors/power/hotswap_in_Input_Power \
xyz.openbmc_project.Association.Definitions Associations
a(sss) 2 "inventory" "sensors" "/xyz/openbmc_project/inventory/system/powersupply/psu_chassis" "chassis" "all_sensors" "/xyz/openbmc_project/inventory/system/board/mainboard"

Change-Id: I8a9e4191c427b441d96f0ab53ba59825eccee997
Signed-off-by: Shounak Mitra <shounak@google.com>

show more ...

PSUSensorMain: expanding the list, which changes frequently

This list is frequently updated, so it is convenient when it is expanded

Signed-off-by: Glukhov Mikhail <mikl@greenfil.ru>
Change-Id: Ib0

PSUSensorMain: expanding the list, which changes frequently

This list is frequently updated, so it is convenient when it is expanded

Signed-off-by: Glukhov Mikhail <mikl@greenfil.ru>
Change-Id: Ib0ae40b6f0c6d5df660baaa7ae4e9ea0f5465101

show more ...

Don't use deprecated asio functions

This code used a number of asio functions that have been deprecated.
This patch replaces them with their new equivalents, and enabled
BOOST_ASIO_NO_DEPRECATED.

C

Don't use deprecated asio functions

This code used a number of asio functions that have been deprecated.
This patch replaces them with their new equivalents, and enabled
BOOST_ASIO_NO_DEPRECATED.

Change-Id: I98bddba4c7d72a53ceca9455429828e60f06c5e0
Signed-off-by: Ed Tanous <edtanous@google.com>

show more ...