| #
391ade08 |
| 15-Jan-2021 |
Matthew Barth <msbarth@us.ibm.com> |
control: Add creating config object without a dbus object
For those configuration objects that do not need a dbus object, create
them using a similar method without requiring a dbus obje
control: Add creating config object without a dbus object
For those configuration objects that do not need a dbus object, create
them using a similar method without requiring a dbus object to be given.
Updated each object to correctly reflect their current need of a dbus
object which was driven by moving the creation of the available group
objects to within the event.
Change-Id: I8ce4ea7baf4cfd1ad86268b760a334fcf0a4f25e
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
show more ...
|
| #
9167c4d5 |
| 24-Aug-2020 |
Matthew Barth <msbarth@us.ibm.com> |
control: Complete profile configuration parsing
Profiles' have an active state that are determined by a given method
within the JSON configuration. Each method for determining a profile'
control: Complete profile configuration parsing
Profiles' have an active state that are determined by a given method
within the JSON configuration. Each method for determining a profile's
active state is mapped from its JSON configuration method name to the
handler function that is implemented to parse and return the profile's
active state based on the configuration. At this time, only an `all_of`
active state method is supported where all of the provided list of dbus
properties must match their given value for the profile to be active.
Tested:
Profile method parsed and active state set appropriately
Change-Id: I258ecabccb849b2fa2662a157d6cb108af2c9886
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
show more ...
|
| #
a56135b5 |
| 18-Aug-2020 |
Matthew Barth <msbarth@us.ibm.com> |
control: Add profile configuration class framework
The profile class will contain the configuration for each profile that
is configured within the "profiles.json" file. Profiles are opti
control: Add profile configuration class framework
The profile class will contain the configuration for each profile that
is configured within the "profiles.json" file. Profiles are optional,
therefore the "profiles.json" file is optionally present. When no
profiles exist, all configured fan control events are used, however if
one-or-more profiles exist, events configured for the specific profile
are used along with any events not configured under a profile.
Tested:
"profiles.json" file parsed and profile name retrieved
Change-Id: Ia450bc2a3f94f1449eb61c8ce46e6fe17aecf464
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
show more ...
|