clang-format: re-format for clang-18

clang-format-18 isn't compatible with the clang-format-17 output, so we
need to reformat the code with the latest version. The way clang-18
handles lambda forma

clang-format: re-format for clang-18

clang-format-18 isn't compatible with the clang-format-17 output, so we
need to reformat the code with the latest version. The way clang-18
handles lambda formatting also changed, so we have made changes to the
organization default style format to better handle lambda formatting.

See I5e08687e696dd240402a2780158664b7113def0e for updated style.
See Iea0776aaa7edd483fa395e23de25ebf5a6288f71 for clang-18 enablement.

Change-Id: Ica590f8613f1fb89ab1ca676ac51c1cc7e38d67f
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>

show more ...

clang-format: copy latest and re-format

clang-format-17 has some backwards incompatible changes that require
additional settings for best compatibility and re-running the formatter.
Copy the latest

clang-format: copy latest and re-format

clang-format-17 has some backwards incompatible changes that require
additional settings for best compatibility and re-running the formatter.
Copy the latest .clang-format from the docs repository and reformat the
repository.

Change-Id: I3e9e6350864ac267819a4b8d670bef7d3746976e
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>

show more ...

clang-format: copy latest and re-format

clang-format-16 has some backwards incompatible changes that require
additional settings for best compatibility and re-running the formatter.
Copy the latest

clang-format: copy latest and re-format

clang-format-16 has some backwards incompatible changes that require
additional settings for best compatibility and re-running the formatter.
Copy the latest .clang-format from the docs repository and reformat the
repository.

Change-Id: I152f141a5e8343b92b5ce81d3ca16eec77b5606b
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>

show more ...

control: Actions use list of groups set on base object

Remove the reference to a group given when running an action and instead
have each action iterate over the list of groups configured/set on the

control: Actions use list of groups set on base object

Remove the reference to a group given when running an action and instead
have each action iterate over the list of groups configured/set on the
base action object. The group configured/set on the base action object
is the only set of groups that the action should use based on its
configuration in an event.

Change-Id: Ia298d270e782ad729b5a29f9cdfe9b6c9ea4bc45
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>

show more ...

control: Update base action object with zones and groups used

The base action object stores the groups and zones configured for an
action to use and run against. When a trigger fires, it will run th

control: Update base action object with zones and groups used

The base action object stores the groups and zones configured for an
action to use and run against. When a trigger fires, it will run the
action against each zone configured. Each action will have its list of
groups to use that it can iterate over appropriately. This will be
updated in the next commit to no longer pass a reference to a group when
running an action and to have each action iterate over the groups
configured for them to use.

Change-Id: Ifcd1a260e38af87c5f3bb2a3d44813e71743abc6
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>

show more ...

control: Extend actions from the config base object

Make actions also be base config objects to allow profiles to be defined
on an action. This also provides the parsing of variable values from the

control: Extend actions from the config base object

Make actions also be base config objects to allow profiles to be defined
on an action. This also provides the parsing of variable values from the
JSON of a configured action.

Included in this commit is an action parsing error exception class that
actions will use when a required attribute fails to be parsed from the
JSON for the given action.

Change-Id: I0fb040afb09d17830e7bb1a587de1b501b638eae
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>

show more ...

control: Add set target on missing owner action

Add the YAML based set_speed_on_missing_owner action function as an
action class for JSON configs to use.

Change-Id: Iebe0cc7bbaf063ef33ca0b918dd1d85

control: Add set target on missing owner action

Add the YAML based set_speed_on_missing_owner action function as an
action class for JSON configs to use.

Change-Id: Iebe0cc7bbaf063ef33ca0b918dd1d8576e2425eb
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>

show more ...

control: Use group objects in actions

Switch to use the group objects created from JSON in the actions which
allows the zone and fan YAML objects to be removed from the JSON based
binary. In switchi

control: Use group objects in actions

Switch to use the group objects created from JSON in the actions which
allows the zone and fan YAML objects to be removed from the JSON based
binary. In switching to the JSON based group objects, the
`default_floor` action required additional methods to be added to the
appropriate objects. These additional methods were copied over from the
associated YAML based object classes.

To reduce the amount of changes in this commit, the `requestIncrease`
method was not copied over and will be in a following commit. An
additional commit will also remove the use of YAML based objects from
the JSON based zone object.

Change-Id: I5fea29f099d0176b2ffe486e79f0c585e744d807
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>

show more ...

control: Update JSON action objects to run the action

A change in design direction for the JSON configuration path of fan
control is to have it separate than the YAML configuration
functionality. Th

control: Update JSON action objects to run the action

A change in design direction for the JSON configuration path of fan
control is to have it separate than the YAML configuration
functionality. This means that the JSON based action objects will run
the action function directly instead of returning the action function
which is done for YAML based configurations.

Update the default floor action to reflect this change in direction.

Change-Id: I75ade1c7e2e9698573c5ed2495c2f3b7e9cf52f0
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>

show more ...

control: Self registering action objects framework

Configured fan control events consist of actions that alter fan
control's overall algorithm in controlling fan speeds. The use of self
registering

control: Self registering action objects framework

Configured fan control events consist of actions that alter fan
control's overall algorithm in controlling fan speeds. The use of self
registering action objects allows quick inclusion of all supported
actions simply by giving the action object a name and extending the
registration framework. The registering of available actions are done
prior to main() starting to ensure they are ready to be
created/initialized if configured to be used. When a configured action
is requested, a single call to the ActionFactory::getAction() function
creates and returns the action object for use.

Included in this commit is a completed example use of this framework by
the "DefaultFloor" action object. Currently it is planned to have these
action objects driven by a JSON configuration use the already available
action function that was pulled into the YAML generated fan definitions
structure that was done at compile time.

Tested:
Derived action objects registered prior to main() starting
Action objects only created when included in the JSON config
Only a single action of a given name is allowed
Action objects correctly call their corresponding action function

Change-Id: Ia059d3c656aaaa9e585eec68812663dd0ee1125c
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>

show more ...