|
@@ -41,6 +41,7 @@ The watchdog device structure looks like this:
|
|
|
struct watchdog_device {
|
|
|
const struct watchdog_info *info;
|
|
|
const struct watchdog_ops *ops;
|
|
|
+ unsigned int bootstatus;
|
|
|
void *driver_data;
|
|
|
unsigned long status;
|
|
|
};
|
|
@@ -49,6 +50,8 @@ It contains following fields:
|
|
|
* info: a pointer to a watchdog_info structure. This structure gives some
|
|
|
additional information about the watchdog timer itself. (Like it's unique name)
|
|
|
* ops: a pointer to the list of watchdog operations that the watchdog supports.
|
|
|
+* bootstatus: status of the device after booting (reported with watchdog
|
|
|
+ WDIOF_* status bits).
|
|
|
* driver_data: a pointer to the drivers private data of a watchdog device.
|
|
|
This data should only be accessed via the watchdog_set_drvadata and
|
|
|
watchdog_get_drvdata routines.
|
|
@@ -65,6 +68,7 @@ struct watchdog_ops {
|
|
|
int (*stop)(struct watchdog_device *);
|
|
|
/* optional operations */
|
|
|
int (*ping)(struct watchdog_device *);
|
|
|
+ unsigned int (*status)(struct watchdog_device *);
|
|
|
};
|
|
|
|
|
|
It is important that you first define the module owner of the watchdog timer
|
|
@@ -97,6 +101,8 @@ they are supported. These optional routines/operations are:
|
|
|
the watchdog timer driver core does: to send a keepalive ping to the watchdog
|
|
|
timer hardware it will either use the ping operation (when available) or the
|
|
|
start operation (when the ping operation is not available).
|
|
|
+* status: this routine checks the status of the watchdog timer device. The
|
|
|
+ status of the device is reported with watchdog WDIOF_* status flags/bits.
|
|
|
|
|
|
The status bits should (preferably) be set with the set_bit and clear_bit alike
|
|
|
bit-operations. The status bits that are defined are:
|