| commit | 13b63f8f597d396db8b5bd182ac2e5814d599e2f | [log] [tgz] |
|---|---|---|
| author | Ed Tanous <edtanous@google.com> | Tue May 11 16:12:52 2021 -0700 |
| committer | Ed Tanous <edtanous@google.com> | Tue May 11 16:12:52 2021 -0700 |
| tree | 0152b79e116e3b510df1d817c64766e5737f9bf2 | |
| parent | 5636d52baad683fbb51447a716d66cb06959e52f [diff] |
Make a string copy explicit The newest version of gcc seems to flag on patterns like what was included there, where we implicitly construct a string, then take a reference to it. So far as I'm aware, this has never caused an issue in practice, but seems to be undefined behavior. In a perfect world, I would change the left side of this to match the input type of const char*, but that would require some interface changes that I'd like to avoid to keep this change small and self contained while we try to fix the build. Signed-off-by: Ed Tanous <edtanous@google.com> Change-Id: Ic1ff16c02f6461894834432ccad285526ae41b3f
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