There is no documentation for the watchdog properties that are common among most of the watchdog drivers. Add document where these generic properties can be described and told how they should be used in drivers.
Signed-off-by: Timo Kokkonen <[email protected]> --- .../devicetree/bindings/watchdog/watchdog.txt | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 Documentation/devicetree/bindings/watchdog/watchdog.txt diff --git a/Documentation/devicetree/bindings/watchdog/watchdog.txt b/Documentation/devicetree/bindings/watchdog/watchdog.txt new file mode 100644 index 0000000..3781406 --- /dev/null +++ b/Documentation/devicetree/bindings/watchdog/watchdog.txt @@ -0,0 +1,20 @@ +These properties are common among most watchdog drivers. Any driver +that requires the functionality listed below should implement them +using these definitions. + +Optional properties: +- timeout-sec: Contains the watchdog timeout in seconds. +- early-timeout-sec: If present, specify the timeout in seconds for + how long it can take for the watchdog daemon to take over the + watchdog device. If driver supports this property it must ensure the + watchdog hardware is running during this period and a watchdog reset + must occur if user space fails to open the device in time. If left + zero, the driver only needs to guarantee the watchdog is not + stopped or is started during driver init. + +Example: + +watchdog { + timeout-sec = <60>; + early-timeout-sec = <120>; +}; -- 2.1.0 -- To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
