| commit | 49d12d8955495d4091b4520605c9e4510fcd743b | [log] [tgz] |
|---|---|---|
| author | Ed Tanous <edtanous@google.com> | Thu Feb 11 13:44:15 2021 -0800 |
| committer | Ed Tanous <ed@tanous.net> | Thu Feb 11 22:19:36 2021 +0000 |
| tree | 66daee1a63d2f80a82a1e750d172328f42b421b4 | |
| parent | 495855861648f082a73d4ba4afe23262d6fb0ad0 [diff] |
Fix mcu option If the mcu temp sensor is not included in a build, it isn't showing up. This is due to meson_options.txt having 2 different names for mcu; mcu, and mcu-temp. The upstream recipe uses mcu to key, so lets just do that. Signed-off-by: Ed Tanous <edtanous@google.com> Change-Id: Ib84c96b97c534c81e9e4e83c838dffe4e26b6957
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