summaryrefslogtreecommitdiffstats
path: root/test/utility
Commit message (Collapse)AuthorAgeFilesLines
* utility/timer: Implement callback settingWilliam A. Kennington III2018-10-301-0/+7
| | | | | | | | | | | All of the other classes that take callbacks support having the callback updated. Tested: Builds and passed through the unit test suite. Change-Id: I0efcd074523fa6ec0cc84c7a930346dd9340f7ec Signed-off-by: William A. Kennington III <wak@google.com>
* utility/timer: Make movableWilliam A. Kennington III2018-10-291-0/+41
| | | | | | | | | | | | Now that we can update the callbacks of our sources, we can move the timer object freely by updating the callback when moved. Tested: Unit tests pass, and we no longer see any valgrind issues when moving the timer object. Change-Id: I15baf97538459ca8b9c48b75dba77d09b7b5075b Signed-off-by: William A. Kennington III <wak@google.com>
* utility/timer: Make it possible to get the EventWilliam A. Kennington III2018-10-181-0/+1
| | | | | | | | | | | | Other event sources expose the ability to get th event used for constructing the source. Since our timer is basically just a time source, we should be able to trivially get the event object. Tested: Built and run through unit tests Change-Id: I4b4192797652a903cba90d6e73771014df7702d6 Signed-off-by: William A. Kennington III <wak@google.com>
* utility/timer: Implement oneshot timersWilliam A. Kennington III2018-09-261-16/+166
| | | | | | | | | | | | | | | This change is meant to enable users of the old openbmc timer class to trivially use the timer if they only want single executions. It also makes setting up the timer less verbose if you do not already know the timeout interval. Tested: Run through unit tests and did a sample integration with phosphor-watchdog and phosphor-networkd. Verified that the new oneshot example works as expected. Change-Id: I2cd006d1f19fff99bce3f732a16eac9ca9553666 Signed-off-by: William A. Kennington III <wak@google.com>
* utility/timer: Callback should pass in the timerWilliam A. Kennington III2018-09-251-1/+1
| | | | | | | | | | | | | | This makes the timer better resemble the other source types, and makes it easier to access timer properties from the callback. Since we do not yet have any committed users of this API it is safe to change it. Tested: Unit tests were run and builds work fine. Change-Id: I9ecb24a20bc822b2ab55900e47a7cae834ba873d Signed-off-by: William A. Kennington III <wak@google.com>
* utility/timer: ImplementWilliam A. Kennington III2018-09-191-0/+263
We often need a continually ticking timer for our daemons. This utility wraps an sd_event time source as a convenience. This is meant to be a usable replacement for the timer.hpp found in other openbmc projects. Tested: New tests pass with full coverage. Changes to the phosphor-watchdog that rely on this utility work as expected. Change-Id: Id12aed9e5b018e7eca825c4a7ac7b4f46e2f04c6 Signed-off-by: William A. Kennington III <wak@google.com>
OpenPOWER on IntegriCloud