| commit | 1263c3dad3a723f4ebbd05e4031e4d5ff45f349c | [log] [tgz] |
|---|---|---|
| author | Bruce Lee <Bruce_Lee@quantatw.com> | Fri Jun 04 15:16:33 2021 +0800 |
| committer | Bruce Lee <Bruce_Lee@quantatw.com> | Fri Jun 04 15:16:33 2021 +0800 |
| tree | 232c4c1d118a6cd8f43ecae6dd5e936c495cf153 | |
| parent | 2f20c5ab30fcceb401be7a22b39a497eb7026670 [diff] |
Modify set-value function from external
Move Special mode from bmcweb to dbus-sensors, this will be handled via dbus-sensor when the user set-value f$
This is unlikely to break any users because the Intel special mode function is no change, only move to dbus-s$
The set value function is to filter the external set, excluding the internal set.
In the external set, if in INSECURE_UNRESTRICTED_SENSOR_OVERRIDE, no need to check before set value else add $
bmcweb needs to be merged at the same time.
bmcweb changes are pushed to Gerrit:
https://gerrit.openbmc-project.xyz/c/openbmc/bmcweb/+/42448
the mailing list discussion links:
https://lists.ozlabs.org/pipermail/openbmc/2021-March/025597.html
Signed-off-by: Bruce Lee <Bruce_Lee@quantatw.com>
Change-Id: I0919e4d2343e81045010a2b0d4bf01dc272bcb07
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