commit | b1416efa8d6d1a14a51bd0590f5a5cb6399a10cf | [log] [tgz] |
---|---|---|
author | Thang Tran <thuutran@amperecomputing.com> | Wed Aug 02 13:57:09 2023 +0700 |
committer | Thang Tran <thuutran@amperecomputing.com> | Tue Nov 28 00:48:06 2023 +0000 |
tree | 24eaf25c484c79c5d077b8cbc27db28b9c54531c | |
parent | 7bb412f5a37ff3587a67610c022d781525b1a423 [diff] |
dbus-sdr: check instance start value in getSensorInfo function Issue: When users request to read DCMI sensor information via "ipmitool raw 0x2c 0x07 0xdc 0x01 0x07 0x00 <Instance_start>", the return values always are 8 first sensors even the "Instance_start" is not 0. Root cause: In the getSensorInfo function, it does not check the instance start parameter. It always returns 8 first sensors. Solution: Update the getSensorInfo function as below: - Get the list of Sensors based on the Entity ID. - Sort the list of Sensors. - Compare Sensor's Entity Instance with Instance start parameter Tested: 1. Get the list of DCMI sensors information with Instance start is not 0 "ipmitool raw 0x2c 0x07 0xdc 0x01 0x07 0x00 <Ins_Start>" 2. BMC returns sensor Record ID which have the Entity Instance are greater than Instance start. Change-Id: I10f7cf4e87cb5eb8fe1da81561263e1604418c45 Signed-off-by: Thang Tran <thuutran@amperecomputing.com>
meson builddir ninja -C builddir
meson builddir -Dbuildtype=minsize -Db_lto=true -Dtests=disabled ninja -C builddir
If any of the dependencies are not found on the host system during configuration, meson automatically gets them via its wrap dependencies mentioned in ipmid/subprojects
.
meson builddir -Dwrap_mode=nofallback ninja -C builddir
meson builddir -Dbuildtype=debug ninja -C builddir
meson builddir -Db_coverage=true -Dtests=enabled ninja -C builddir test ninja -C builddir coverage