docs/control/events.md

3 This file defines the events that dictate how fan control operates. Each event
61 property on each D-Bus object in the group, update the new value in the object
65 the Present property on each member of the group and set the fan target hold to
99 for each.
119 2. `name_has_owner` - Populates the service owned state from D-Bus for each
124 Signal triggers subscribe to certain D-Bus signals for each member of its
137    D-Bus interface and property specified in the group definition for each group
142    interface specified in the group definition for each group member. When the
147    D-Bus interface specified in the group definition for each group member. When
153    each group member. When the signal occurs, the service owned state will be
156 5. `member` - Subscribes to the signal listed on each group member. No caches
268 Calculates the net target increase to be requested based on the value of each
294 - For each member of the 'pcie temps' group:
319 - For each member of the 'proc 0 core temps' group:
331 Calculates the net target decrease to be requested based on the value of each
357 - For each member of the 'pcie temps' group:
382 - For each member of the 'proc 0 core temps' group:
407 The above config reads the configured D-Bus property on each group member
427 The above config reads the configured D-Bus property on each group member
682 group will be mapped to the "map" to get the output "target". Each configured
686 stored in that static map with its own key. Each time it calls this action
687 running for each event, after the new value is updated to the static map, the
696 compared against all members within each group to start/stop the timer. When all