History log of /openbmc/phosphor-watchdog/ (Results 101 – 111 of 111)
Revision Date Author Comments
(<<< Hide modified files)
(Show modified files >>>)
50c3094515-Jun-2017 Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>

Remove logging Watchdog reset request

Since watchdog reset comes in very often, it floods the journal
and hence it does not add any value.

Change-Id: If36374511f7993126244e7c06da4bfa2dfcd0991
Signe

Remove logging Watchdog reset request

Since watchdog reset comes in very often, it floods the journal
and hence it does not add any value.

Change-Id: If36374511f7993126244e7c06da4bfa2dfcd0991
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>

show more ...

f2309dd906-Jun-2017 Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>

Update Interval when timeRemaining is updated

A typical watchdog implementation would give these 2 features:
- Setting the interval
- Resetting the timer which also means poke

This watchdog imp

Update Interval when timeRemaining is updated

A typical watchdog implementation would give these 2 features:
- Setting the interval
- Resetting the timer which also means poke

This watchdog implementation does not provide a poke function
and the same can be achieved by clients making these dbus calls
in that order.

1) Get the Last set Interval
2) Set TimeRemaining field to result from #1

To achieve #1, this commit adds the support.

This would make sure that the new timer would expire after last
updated user interval from that time.

Fixes openbmc/openbmc#767

Change-Id: I7393eb32992d7a08518ef463fd0a442df0772392
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>

show more ...

f00d0db802-Jun-2017 Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>

Add .gitignore file

Change-Id: Ibbfcdea72f7cd9dc061fc1f77526121e3c1f34fa
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>

4d5ef3f931-May-2017 Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>

Commit error and exit the application on error scenarios

Typically sd_event* calls can not go wrong and if they do, better
would be to terminate the application so we get a coredump.

Change-Id: I89

Commit error and exit the application on error scenarios

Typically sd_event* calls can not go wrong and if they do, better
would be to terminate the application so we get a coredump.

Change-Id: I899177c369332cabf6d9bc22daaa142b50d758d0
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>

show more ...

00bd377e31-May-2017 Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>

Add Gtest to test watchdog

Change-Id: Ia0268b6b18999b6dd6cfd26bcadcff25734306f0
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>

3473d70d30-May-2017 Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>

Call systemd target on timer expiration

User can pass an optional command line argument stating which
systemd target needs to be called on timer expiration. The timeout
handler will make sure that t

Call systemd target on timer expiration

User can pass an optional command line argument stating which
systemd target needs to be called on timer expiration. The timeout
handler will make sure that the systemd target is started prior to
exiting.

Change-Id: I37213ab28ad4166a47920dcb3dc79769c7f2af1a
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>

show more ...

8c5a229830-May-2017 Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>

Invoke optional callback function on timer expiration

When the timer expires, it calls into it's own timeout
handler which matches with sd_event callback handler.

However, it is beneficial if the u

Invoke optional callback function on timer expiration

When the timer expires, it calls into it's own timeout
handler which matches with sd_event callback handler.

However, it is beneficial if the users of timer register
their own callback routine so that they can execute some
operations on timeout.

Change-Id: Ia88cb4e3c17f6dd8d4528fa193ec7927f083a92b
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>

show more ...

d7a3f13e29-May-2017 Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>

Implement Watchdog interface

This commit gives concrete implementation of the interface.

Change-Id: I3951c5811c8e6cff87c87842a1e3c538463bfde7
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.

Implement Watchdog interface

This commit gives concrete implementation of the interface.

Change-Id: I3951c5811c8e6cff87c87842a1e3c538463bfde7
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>

show more ...

7e14655729-May-2017 Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>

Add timer class support

Watchdog implementation uses sd_event_timer at the backend and this
commit has that timer backend support.

Change-Id: Ib6dbd5d6bb617c20d7361e0852a916aa506d5aad
Signed-off-by

Add timer class support

Watchdog implementation uses sd_event_timer at the backend and this
commit has that timer backend support.

Change-Id: Ib6dbd5d6bb617c20d7361e0852a916aa506d5aad
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>

show more ...

15b1dc1723-May-2017 Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>

Add code to accept command line arguments

Accepts command line arguments for dbus object path,
dbus service name and an optional systemd unit file
to be called into when the timer expires.

Change-I

Add code to accept command line arguments

Accepts command line arguments for dbus object path,
dbus service name and an optional systemd unit file
to be called into when the timer expires.

Change-Id: I3fbe59b36d73ed9f28de2596d77e6d2e99371622
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>

show more ...

7815425814-Dec-2016 Patrick Williams <patrick@stwcx.xyz>

Initial commit

12345