| commit | 445efe3393f42f1103c96c41f147a850cc06e871 | [log] [tgz] |
|---|---|---|
| author | Yuan Li <yuan.li@linux.intel.com> | Fri Jun 14 22:58:32 2019 +0800 |
| committer | Yuan Li <yuan.li@linux.intel.com> | Wed Jun 19 22:48:06 2019 +0000 |
| tree | bf08faea7d55e2d4fa89572d8f34c178d8f712dc | |
| parent | be73e6a4d11f6c9f6f6887918404901cd87386b8 [diff] |
Support temp sensor on MCU which is available from I2C
Chassis MCU exposes register to report temperature for the peripheral board.
The MCU access is configurable as below:
{
"Bus": $bus,
"Address": "0xAA",
"Reg": "0xBB",
"Class": "MCUTemp",
"Name": "MCU Temp",
"Thresholds": [
xxx
]
"Type": "MCUTempSensor"
}
Tested:
The below interface was found under temperature sensor namespace:
└─/xyz/openbmc_project/sensors/temperature/MCU_Temp
Run ipmitool sensor and check below from list:
MCU Temp | 30.175 | degrees C | cr | na | 0.000 | 5.000 | 110.000 | 115.000 | na
Change-Id: I8d54455ccc39ea4f60a5b4aee5c68be092d39a72
Signed-off-by: Yuan Li <yuan.li@linux.intel.com>
dbus-sensors is a collection of sensor applications that provide the xyz.openbmc_project.Sensor collection of interfaces. They read sensor values from hwmon, d-bus, or direct driver access to provide readings. Some advance non-sensor features such as fan presence, pwm control, and automatic cpu detection (x86) are also supported.
runtime re-configurable from d-bus (entity-manager or the like)
isolated: each sensor type is isolated into its own daemon, so a bug in one sensor is unlikely to affect another, and single sensor modifications are possible
async single-threaded: uses sdbusplus/asio bindings
multiple data inputs: hwmon, d-bus, direct driver access