Searched hist:ade0c377bab43810a4871676c2993c2ec363717e (Results 1 – 3 of 3) sorted by relevance
| /openbmc/phosphor-fan-presence/control/json/triggers/ |
| H A D | timer.cpp | diff ade0c377bab43810a4871676c2993c2ec363717e Thu Oct 28 16:09:44 CDT 2021 Matt Spinler <spinler@us.ibm.com> control: Timer trigger can preload groups
The timer trigger is used to run actions when it expires. This commit
adds the ability for it to preload group properties so the latest values
are in the cache before it runs the actions.
This means that there doesn't need to be propertiesChanged triggers for
the groups, instead the load just reads them straight from D-Bus.
One reason to use this is so an action can be run on a slower cadence than
propertiesChanged signals would be sent. An example is a virtual sensor
that has component sensors spread out across multiple daemons. Even if
the daemons all use the same poll rates, they can be staggered between
them so virtual sensor changes could occur faster then any component
sensor read interval.
The trade off is there will be D-Bus traffic every timer interval, even
in the case the group property values don't change.
To enable this, use the following in the trigger JSON:
"preload_groups": true
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I1a92007c10fdd8017c1a89d15983ae50134c852a
|
| /openbmc/phosphor-fan-presence/control/json/ |
| H A D | manager.hpp | diff ade0c377bab43810a4871676c2993c2ec363717e Thu Oct 28 16:09:44 CDT 2021 Matt Spinler <spinler@us.ibm.com> control: Timer trigger can preload groups
The timer trigger is used to run actions when it expires. This commit
adds the ability for it to preload group properties so the latest values
are in the cache before it runs the actions.
This means that there doesn't need to be propertiesChanged triggers for
the groups, instead the load just reads them straight from D-Bus.
One reason to use this is so an action can be run on a slower cadence than
propertiesChanged signals would be sent. An example is a virtual sensor
that has component sensors spread out across multiple daemons. Even if
the daemons all use the same poll rates, they can be staggered between
them so virtual sensor changes could occur faster then any component
sensor read interval.
The trade off is there will be D-Bus traffic every timer interval, even
in the case the group property values don't change.
To enable this, use the following in the trigger JSON:
"preload_groups": true
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I1a92007c10fdd8017c1a89d15983ae50134c852a
|
| H A D | manager.cpp | diff ade0c377bab43810a4871676c2993c2ec363717e Thu Oct 28 16:09:44 CDT 2021 Matt Spinler <spinler@us.ibm.com> control: Timer trigger can preload groups
The timer trigger is used to run actions when it expires. This commit
adds the ability for it to preload group properties so the latest values
are in the cache before it runs the actions.
This means that there doesn't need to be propertiesChanged triggers for
the groups, instead the load just reads them straight from D-Bus.
One reason to use this is so an action can be run on a slower cadence than
propertiesChanged signals would be sent. An example is a virtual sensor
that has component sensors spread out across multiple daemons. Even if
the daemons all use the same poll rates, they can be staggered between
them so virtual sensor changes could occur faster then any component
sensor read interval.
The trade off is there will be D-Bus traffic every timer interval, even
in the case the group property values don't change.
To enable this, use the following in the trigger JSON:
"preload_groups": true
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I1a92007c10fdd8017c1a89d15983ae50134c852a
|