watchdog: Add millisecond-level capabilities
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest6 patches 7 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/6 | watchdog: Allow a driver to use milliseconds instead of secondsdrivers/ drivers/ include/ +1 more | +82 | 7 replies | |
| 2/6 | watchdog: Add ioctls for millisecond timeout handlingdrivers/ drivers/ drivers/ +1 more | +98 | 0 replies | |
| 3/6 | watchdog: Add millisecond precision device attributesdrivers/ | +24 | 0 replies | |
| 4/6 | watchdog: Add documentation for millisecond interfacesDocumentation/ Documentation/ | +78 | 0 replies | |
| 5/6 | watchdog:i6300: Convert to a millisecond watchdog devicedrivers/ | +56 | 0 replies | |
| 6/6 | watchdog:softdog: Convert to a millisecond watchdogdrivers/ | +7 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/6] watchdog: Add millisecond-level capabilities
As mentioned before in the list, this is work for the ELISA (Linux in safety critical systems) group. Some use cases require tight watchdog times so a system can recover quickly on a failure.
This patch series adds millisecond level capabilites that devices can use if they wish, new ioctls to use those interfaces, new device attributes with the higher precision, documentation, and it converts the i6300 and softdog watchdog to use milliseconds.
All existing user APIs should work as before. The interface between the watchdog subsystem and the driver is converted to be modal. If a flag is set in the options then all interactions are in milliseconds. If the flag is not set then they are in seconds.
It's all pretty straightforward except for the calculations in the i6300 driver, which required some thought.
Note that checkpatch gives warnings about there being no identifiers in the function arguments in the watchdog ops structure, but I tried to keep the style the same.
Thanks,
-corey