Hi Martyn,
On 11/25/2015 07:36 AM, Martyn Welch wrote:
[ ... ]
+
+#define ZIIRAVE_REASON_POWER_UP 0x0
+#define ZIIRAVE_REASON_HW_WDT 0x1
+#define ZIIRAVE_REASON_HOST_REQ 0x4
+#define ZIIRAVE_REASON_IGL_CFG 0x6
+#define ZIIRAVE_REASON_IGL_INST 0x7
+#define ZIIRAVE_REASON_IGL_TRAP 0x8
+#define ZIIRAVE_REASON_UNKNOWN 0x9
+
+static char *ziirave_reasons[] = {"power cycle", "triggered", "host request",
+ "illegal configuration",
+ "illegal instruction", "illegal trap",
+ "unknown"};
+
I don't see mapping code from the reason values to the array.
"host request" is array index 2 but the defined value is 0x4.
Am I missing something ?
Whoops, missed that. I guess the simplest thing to do is pad out the array?
I thought you wanted to check if I really read your code :-).
Yes, padding would probably be the simplest solution, though question is
what to do with undefined values. Maybe pad with NULL and also check if
ziirave_reasons[x] is not NULL ?
+ /*
+ * The default value set in the watchdog should be perfectly valid, so
+ * pass that in if we haven't provided one via the module parameter or
+ * of property.
+ */
+ if (w_priv->wdd.timeout == 0) {
+ val = i2c_smbus_read_byte_data(client, ZIIRAVE_WDT_TIMEOUT);
+ if (val < 0)
+ return val;
+
+ w_priv->wdd.timeout = val;
What if the returned value is 0 ?
Minimum timeout is 3, device won't accept a value below that and should never return a value
below that.
Maybe add the following ?
if (val < ZIIRAVE_TIMEOUT_MIN)
return -ENODEV;
Thanks,
Guenter
--
To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
