#
9b06243d |
| 26-Jan-2023 |
Matt Spinler <spinler@us.ibm.com> |
Add explicit keyword to 1 arg constructors
The cppcheck tool complains about it otherwise.
Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: Id977a6c349b0b49354b52ac994ea7742e0a39307
|
#
2541f99c |
| 16-Aug-2022 |
Matt Spinler <spinler@us.ibm.com> |
control: Display locked targets in debug dump
The override_fan_target action can lock individual fan targets to a value that is different than the zone target that the rest of the fans are set to.
control: Display locked targets in debug dump
The override_fan_target action can lock individual fan targets to a value that is different than the zone target that the rest of the fans are set to.
This change adds those locked target values to the 'zones' section of the debug dump:
"target_locks": { "fan0": [ 11300 ], "fan3": [ 11300 ] }
And when there are no locks:
"target_locks": {}
Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I2c4cfa317028db8843d361e79b270d612aacdd87
show more ...
|
#
cb356d48 |
| 22-Jul-2022 |
Patrick Williams <patrick@stwcx.xyz> |
sdbusplus: use shorter type aliases
The sdbusplus headers provide shortened aliases for many types. Switch to using them to provide better code clarity and shorter lines. Possible replacements are
sdbusplus: use shorter type aliases
The sdbusplus headers provide shortened aliases for many types. Switch to using them to provide better code clarity and shorter lines. Possible replacements are for: * bus_t * exception_t * manager_t * match_t * message_t * object_t * slot_t
Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I9029cc722e7712633c15436bd3868d8c3209f567
show more ...
|
#
762e858b |
| 07-Oct-2021 |
Mike Capps <mikepcapps@gmail.com> |
control: action to override a single fan in a zone - Lock fan in Zone
The override Action can only reference fans by name. Thus, Zone is modified to apply a target lock to a specific fan given by na
control: action to override a single fan in a zone - Lock fan in Zone
The override Action can only reference fans by name. Thus, Zone is modified to apply a target lock to a specific fan given by name. Additionally, the unlock method must pass the target value to allow support for concurrent locks.
Signed-off-by: Mike Capps <mikepcapps@gmail.com> Change-Id: Ic2ea81f318fb2c866198a4b24e38cc679147afc5
show more ...
|
#
70c26b2b |
| 07-Oct-2021 |
Mike Capps <mikepcapps@gmail.com> |
control: action to override a single fan in a zone - ability to lock Fan
This change modifies Fan to accept one or more override targets which prevent Fan from accepting regular target updates until
control: action to override a single fan in a zone - ability to lock Fan
This change modifies Fan to accept one or more override targets which prevent Fan from accepting regular target updates until all locks have been cleared using unlockTarget().
Multiple locks are supported, however only the higest locked target will ever be active. For instance, if targets are locked at 9000 and 10000 (in either order), the 10000 lock will be active until it is cleared, at which point the 2nd lowest lock (9000) will become active. When it is cleared, Fan will become unlocked and resume its target from temperature control. If the first locked target happens to be lower than its current target, the lock will take precedence even though it's lower.
Signed-off-by: Mike Capps <mikepcapps@gmail.com> Change-Id: Iba73aa06eed25452117eb138768ed300bc45b0d9
show more ...
|
#
9403a217 |
| 17-May-2021 |
Matthew Barth <msbarth@us.ibm.com> |
control: Switch to using static instance of bus Update main to use the static reference of the bus from util::SDBusPlus.getBus() and have each object that needs the bus call that sam
control: Switch to using static instance of bus Update main to use the static reference of the bus from util::SDBusPlus.getBus() and have each object that needs the bus call that same util::SDBusPlus.getBus() function to retrieve the same static reference. Change-Id: Icd5a0e61819bf1bec8b46daae05443fdcc542b05 Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
show more ...
|
#
603ef164 |
| 24-Mar-2021 |
Matthew Barth <msbarth@us.ibm.com> |
control: Update config loading Change the method used to load objects' JSON configuration where a list of arguments specific to the object's class is given. This allows each class to
control: Update config loading Change the method used to load objects' JSON configuration where a list of arguments specific to the object's class is given. This allows each class to be constructed with its specific set of required arguments. With this change, the zones require a pointer to their manager object along with a reference to the event loop for their increment and decrement timers. The manager object stores the cache for all zones, each zone needs a pointer to its manager to be able to provide access to that cache. With the change in how the objects are created from their JSON configuration files, loading the information into the YAML based ZoneDefinitions structure is no longer needed. Change-Id: I4f70cbeb3a708b985ca01a1f3df14ad78da053fb Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
show more ...
|
#
e47c9588 |
| 09-Mar-2021 |
Matthew Barth <msbarth@us.ibm.com> |
control: Remove references to "speed" in JSON objects Fan control can be configured to control any type of fan where "speed" implies a fan control by setting RPMs. However, fans that are
control: Remove references to "speed" in JSON objects Fan control can be configured to control any type of fan where "speed" implies a fan control by setting RPMs. However, fans that are PWM driven, can also be configured to be controlled so the preference would be to not specific refer to setting "speeds". Change-Id: Ia8920832ea29b519bf408c850febb3fed04ad3f9 Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
show more ...
|
#
a3a8cc57 |
| 15-Jan-2021 |
Matthew Barth <msbarth@us.ibm.com> |
control: Add all fan functionality to JSON fan object In transitioning to JSON based configuration support, the objects created based on the JSON will eventually replace the similar obje
control: Add all fan functionality to JSON fan object In transitioning to JSON based configuration support, the objects created based on the JSON will eventually replace the similar objects used for YAML based configurations. This adds all the functionality from the current fan class used for YAML configs to the fan class used for JSON configs. Change-Id: I50bdd218fc964a4b75126643727f1c3f4d27966b Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
show more ...
|
#
08576c59 |
| 27-Aug-2020 |
Matthew Barth <msbarth@us.ibm.com> |
control: Remove storing bus reference on fan objects Remove the sdbusplus bus reference since its currently not needed within the JSON fan object. Change-Id: I2028a0ad4bd1881f0b
control: Remove storing bus reference on fan objects Remove the sdbusplus bus reference since its currently not needed within the JSON fan object. Change-Id: I2028a0ad4bd1881f0b3d442e063e3785cf9795d5 Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
show more ...
|
#
ce957268 |
| 27-Aug-2020 |
Matthew Barth <msbarth@us.ibm.com> |
control: Pair profiles with name as key Include the profiles of a configuration object in combination with its name to construct a unique key for building the complete fan control co
control: Pair profiles with name as key Include the profiles of a configuration object in combination with its name to construct a unique key for building the complete fan control configuration. This is necessary for supporting the zones, groups, and events configurations. Tested: Object name and list of profiles construct key Profile objects always contain an empty list of profiles Fan objects may or may not contain a list of profiles Change-Id: I4be7229e3fb695d845d60159d0f08f601512c812 Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
show more ...
|
#
bff10804 |
| 25-Aug-2020 |
Matthew Barth <msbarth@us.ibm.com> |
control: Complete fan configuration parsing Fan control's complete configuration includes a configuration of the fan(s) that will be controlled. These fan(s) are made up of configura
control: Complete fan configuration parsing Fan control's complete configuration includes a configuration of the fan(s) that will be controlled. These fan(s) are made up of configuration attributes that determine what zones they are included in and how to interface with their sensor(s) that control their speeds. Tested: Fan object created for each entry within "fans.json" A "fans.json" configuration is required Each supported attribute is parsed and stored on each fan object Change-Id: Ic5db2a685d672a6f5fb642a1dc0ec67cc6ac16a3 Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
show more ...
|
#
fcfa0527 |
| 24-Aug-2020 |
Matthew Barth <msbarth@us.ibm.com> |
control: Add fan configuration class framework The fan class will contain the configuration for each fan to be controlled within the system. A minimum of 1 fan is required to be conf
control: Add fan configuration class framework The fan class will contain the configuration for each fan to be controlled within the system. A minimum of 1 fan is required to be configured. Tested: Fan JSON configuration able to be loaded Fan objects created, each with a name as configured Change-Id: I5f90377453cf7d5d85e1c7c570325c2d97a6060b Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
show more ...
|