<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ks_c_5601-1987">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Hi Andrei,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I figured out the root cause is the sensor type I am using is ADT75 rather than TMP75. So it works after I changed the "Type": "ADT75" in the JSON configuration file and added ADT75 in the devices.hpp.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
================</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
[ 33.154935] lm75 6-0049: hwmon1: sensor 'adt75'
<div>[ 33.160287] i2c i2c-6: new_device: Instantiated device adt75 at 0x49</div>
<div>[ 33.169894] lm75 6-004c: hwmon2: sensor 'adt75'</div>
<div>[ 33.175201] i2c i2c-6: new_device: Instantiated device adt75 at 0x4c</div>
<div>[ 33.184658] lm75 6-004d: hwmon3: sensor 'adt75'</div>
[ 33.190007] i2c i2c-6: new_device: Instantiated device adt75 at 0x4d<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
root@hudsonbay-obmc:~# cat /sys/bus/i2c/devices/6-004d/hwmon/hwmon3/temp1_input
<div>41312</div>
<div>root@hudsonbay-obmc:~# cat /sys/bus/i2c/devices/6-004d/hwmon/hwmon3/temp1_input</div>
41375<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<span style="margin:0px;font-size:12pt">================</span><br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Thank you for your support.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Regards,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Chris Chen</div>
<div>
<div id="appendonsend"></div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>ÐöËìíº:</b> Andrei Kartashev <a.kartashev@yadro.com><br>
<b>ÐöËììíÑ¢:</b> 2021Ò´10êÅ29ìí ù»çí 05:45<br>
<b>â¥Ëìíº:</b> Chris Chen (TPI) <Chris.Chen3@flex.com><br>
<b>ñ«ò©:</b> Re: üÞÜÝ: [entity-manager] Question about temperature sensor stops update</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt">
<div class="PlainText">Oh, that sounds really strange. Are you sure? <br>
When you read it raw (cat /sys/bus/i2c/devices/6-<br>
004d/hwmon/hwmon3/temp1_input) is it also always same? If yes, then, it<br>
is something in kernel - try to experiment with new_device sysfs<br>
interface.<br>
<br>
On Fri, 2021-10-29 at 08:50 +0000, Chris Chen (TPI) wrote:<br>
> Hi Andrei,<br>
> <br>
> Thanks for your prompt reply and the explanation of #2, I understood<br>
> now. <br>
> <br>
> For question #1, let me rephrase it, please. I mean the temperature<br>
> value I read is always the same. The value always shows 40.187, it<br>
> wouldn't be changed even I read it again after a while. But if I<br>
> declare the temp sensors on the I2C bus node in my dts, the value will<br>
> change all the time. Do you have any idea about this?<br>
> <br>
> <br>
> Regards,<br>
> Chris Chen<br>
> <br>
> ÐöËìíº: Andrei Kartashev <a.kartashev@yadro.com><br>
> ÐöËììíÑ¢: 2021Ò´10êÅ29ìí ù»çí 04:33<br>
> â¥Ëìíº: Chris Chen (TPI) <Chris.Chen3@flex.com>; openbmc@lists.ozlabs.org<br>
> <openbmc@lists.ozlabs.org><br>
> ñ«ò©: Re: [entity-manager] Question about temperature sensor stops<br>
> update <br>
> Hello,<br>
> <br>
> I didn't catch, what is your problem. As I see from the logs,<br>
> everything is fine: temp sensors instantiated, dbus objects created,<br>
> readings present. What's wrong?<br>
> <br>
> As for FruDevice: yes, it's kind of weird behaviour: it exposes not<br>
> only actual FRU devices but also other I2C devices. You can introspect<br>
> that objects and see that they exposes<br>
> xyz.openbmc_project.Inventory.Item.I2CDevice interface instead of<br>
> xyz.openbmc_project.FruDevice<br>
> <br>
> On Fri, 2021-10-29 at 08:02 +0000, Chris Chen (TPI) wrote:FruDevice<br>
> > Hi everyone,<br>
> > <br>
> > Actually, I have 2 questions as below:<br>
> > 1. I got understood from others on the mailing list, that I don't<br>
> > have to declare EEPROM or temp sensors on the I2C bus node in my dts,<br>
> > and it should be fine even I did it at the beginning. So I tried to<br>
> > remove this declaration in dts, then the sensor value I got is fixed,<br>
> > no update. Can someone help to take look at why it is?<br>
> > Here are some logs that appeared automatically after the<br>
> > system booted up. It looks like that entity-manager works fine. And<br>
> > the commands I used to check value.<br>
> > =======================================<br>
> > [ 23.713596] lm75 6-0049: hwmon1: sensor 'tmp75'<br>
> > [ 23.718894] i2c i2c-6: new_device: Instantiated<br>
> > device tmp75 at 0x49<br>
> > [ 23.728520] lm75 6-004c: hwmon2: sensor 'tmp75'<br>
> > [ 23.733779] i2c i2c-6: new_device: Instantiated<br>
> > device tmp75 at 0x4c<br>
> > [ 23.743707] lm75 6-004d: hwmon3: sensor 'tmp75'<br>
> > [ 23.749042] i2c i2c-6: new_device: Instantiated device<br>
> > tmp75 at 0x4d<br>
> > <br>
> > # busctl introspect xyz.openbmc_project.HwmonTempSensor<br>
> > /xyz/openbmc_project/sensors/temperature/DIMM_P1_EFGH<br>
> > xyz.openbmc_project.Sensor.Value <br>
> > interface - - -<br>
> > .MaxValue <br>
> > property d 127 emits-<br>
> > change<br>
> > .MinValue <br>
> > property d -128 emits-<br>
> > change<br>
> > .Unit <br>
> > property s "xyz.openbmc_project.Sensor.Value.Uni... emits-<br>
> > change<br>
> > .Value <br>
> > property d 40.187 emits-<br>
> > change writable<br>
> > <br>
> > # cat /sys/bus/i2c/devices/6-<br>
> > 004d/hwmon/hwmon3/temp1_input<br>
> > 40187<br>
> > =======================================<br>
> > 1. From my understanding, there is "detection daemon" which scans<br>
> > I2C bus looking for EEPROMs with IPMI FRU data. However, I found all<br>
> > devices on the I2C buses would be listed, not only Fru devices, when<br>
> > I used the command below. Is this correct?<br>
> > # busctl tree xyz.openbmc_project.FruDevice<br>
> > `-/xyz<br>
> > `-/xyz/openbmc_project<br>
> > `-/xyz/openbmc_project/FruDevice<br>
> > |-/xyz/openbmc_project/FruDevice/0_80<br>
> > |-/xyz/openbmc_project/FruDevice/0_88<br>
> > |-/xyz/openbmc_project/FruDevice/2_108<br>
> > |-/xyz/openbmc_project/FruDevice/2_112<br>
> > |-/xyz/openbmc_project/FruDevice/2_68<br>
> > |-/xyz/openbmc_project/FruDevice/2_72<br>
> > |-/xyz/openbmc_project/FruDevice/3_22<br>
> > |-/xyz/openbmc_project/FruDevice/3_50<br>
> > |-/xyz/openbmc_project/FruDevice/4_56<br>
> > |-/xyz/openbmc_project/FruDevice/5_48<br>
> > |-/xyz/openbmc_project/FruDevice/5_81<br>
> > |-/xyz/openbmc_project/FruDevice/6_73<br>
> > |-/xyz/openbmc_project/FruDevice/6_76<br>
> > |-/xyz/openbmc_project/FruDevice/6_77<br>
> > |-/xyz/openbmc_project/FruDevice/7_80<br>
> > |-/xyz/openbmc_project/FruDevice/7_88<br>
> > |-/xyz/openbmc_project/FruDevice/8_101<br>
> > `-/xyz/openbmc_project/FruDevice/hudsonbay ©¬<br>
> > this is the probe name we define in JSON configuration<br>
> > <br>
> > Thanks.<br>
> > <br>
> > Regards,<br>
> > Chris Chen<br>
> > Legal Disclaimer :<br>
> > The information contained in this message may be privileged and<br>
> > confidential. <br>
> > It is intended to be read only by the individual or entity to whom it<br>
> > is addressed <br>
> > or by their designee. If the reader of this message is not the<br>
> > intended recipient, <br>
> > please immediately notify the sender and delete or destroy any copy<br>
> > of this message!<br>
> <br>
<br>
-- <br>
Best regards,<br>
Andrei Kartashev<br>
<br>
<br>
</div>
</span></font></div>
</div>
</body>
</html>