<feed xmlns='http://www.w3.org/2005/Atom'>
<title>sdeventplus/test/utility, branch master</title>
<subtitle>OpenBMC systemd DBUS event API sources</subtitle>
<id>https://git.raptorcs.com/git/sdeventplus/atom?h=master</id>
<link rel='self' href='https://git.raptorcs.com/git/sdeventplus/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/sdeventplus/'/>
<updated>2018-10-30T20:23:25+00:00</updated>
<entry>
<title>utility/timer: Implement callback setting</title>
<updated>2018-10-30T20:23:25+00:00</updated>
<author>
<name>William A. Kennington III</name>
<email>wak@google.com</email>
</author>
<published>2018-10-30T20:21:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/sdeventplus/commit/?id=08ebb3993a2b5a82d0a5ead29a649c95632f7c64'/>
<id>urn:sha1:08ebb3993a2b5a82d0a5ead29a649c95632f7c64</id>
<content type='text'>
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 &lt;wak@google.com&gt;
</content>
</entry>
<entry>
<title>utility/timer: Make movable</title>
<updated>2018-10-30T03:43:21+00:00</updated>
<author>
<name>William A. Kennington III</name>
<email>wak@google.com</email>
</author>
<published>2018-10-30T03:15:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/sdeventplus/commit/?id=a5f8596add59b7ba5716abe5b0caba21ed84a0f7'/>
<id>urn:sha1:a5f8596add59b7ba5716abe5b0caba21ed84a0f7</id>
<content type='text'>
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 &lt;wak@google.com&gt;
</content>
</entry>
<entry>
<title>utility/timer: Make it possible to get the Event</title>
<updated>2018-10-18T08:15:03+00:00</updated>
<author>
<name>William A. Kennington III</name>
<email>wak@google.com</email>
</author>
<published>2018-10-18T08:12:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/sdeventplus/commit/?id=27b7301a3a18f5b8a77363f0f087d0cff960e9ff'/>
<id>urn:sha1:27b7301a3a18f5b8a77363f0f087d0cff960e9ff</id>
<content type='text'>
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 &lt;wak@google.com&gt;
</content>
</entry>
<entry>
<title>utility/timer: Implement oneshot timers</title>
<updated>2018-09-26T19:18:50+00:00</updated>
<author>
<name>William A. Kennington III</name>
<email>wak@google.com</email>
</author>
<published>2018-09-20T18:35:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/sdeventplus/commit/?id=ba04ffb5a94fd47d8acc57c7a6be4d31624d2c23'/>
<id>urn:sha1:ba04ffb5a94fd47d8acc57c7a6be4d31624d2c23</id>
<content type='text'>
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 &lt;wak@google.com&gt;
</content>
</entry>
<entry>
<title>utility/timer: Callback should pass in the timer</title>
<updated>2018-09-25T22:47:47+00:00</updated>
<author>
<name>William A. Kennington III</name>
<email>wak@google.com</email>
</author>
<published>2018-09-25T22:18:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/sdeventplus/commit/?id=4755818efb01787b7098bd17946fa85686aeeee5'/>
<id>urn:sha1:4755818efb01787b7098bd17946fa85686aeeee5</id>
<content type='text'>
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 &lt;wak@google.com&gt;
</content>
</entry>
<entry>
<title>utility/timer: Implement</title>
<updated>2018-09-20T06:30:27+00:00</updated>
<author>
<name>William A. Kennington III</name>
<email>wak@google.com</email>
</author>
<published>2018-09-20T01:28:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/sdeventplus/commit/?id=81282e1a2b8565dc4e005684bbb923f67e9a6b9d'/>
<id>urn:sha1:81282e1a2b8565dc4e005684bbb923f67e9a6b9d</id>
<content type='text'>
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 &lt;wak@google.com&gt;
</content>
</entry>
</feed>
