hc
2024-12-19 9370bb92b2d16684ee45cf24e879c93c509162da
kernel/Documentation/ABI/testing/sysfs-class-watchdog
....@@ -17,8 +17,13 @@
1717 Date: August 2015
1818 Contact: Wim Van Sebroeck <wim@iguana.be>
1919 Description:
20
- It is a read only file. While reading, it gives '1' if that
21
- device supports nowayout feature else, it gives '0'.
20
+ It is a read/write file. While reading, it gives '1'
21
+ if the device has the nowayout feature set, otherwise
22
+ it gives '0'. Writing a '1' to the file enables the
23
+ nowayout feature. Once set, the nowayout feature
24
+ cannot be disabled, so writing a '0' either has no
25
+ effect (if the feature was already disabled) or
26
+ results in a permission error.
2227
2328 What: /sys/class/watchdog/watchdogn/state
2429 Date: August 2015
....@@ -49,3 +54,63 @@
4954 Description:
5055 It is a read only file. It is read to know about current
5156 value of timeout programmed.
57
+
58
+What: /sys/class/watchdog/watchdogn/pretimeout
59
+Date: December 2016
60
+Contact: Wim Van Sebroeck <wim@iguana.be>
61
+Description:
62
+ It is a read only file. It specifies the time in seconds before
63
+ timeout when the pretimeout interrupt is delivered. Pretimeout
64
+ is an optional feature.
65
+
66
+What: /sys/class/watchdog/watchdogn/pretimeout_avaialable_governors
67
+Date: February 2017
68
+Contact: Wim Van Sebroeck <wim@iguana.be>
69
+Description:
70
+ It is a read only file. It shows the pretimeout governors
71
+ available for this watchdog.
72
+
73
+What: /sys/class/watchdog/watchdogn/pretimeout_governor
74
+Date: February 2017
75
+Contact: Wim Van Sebroeck <wim@iguana.be>
76
+Description:
77
+ It is a read/write file. When read, the currently assigned
78
+ pretimeout governor is returned. When written, it sets
79
+ the pretimeout governor.
80
+
81
+What: /sys/class/watchdog/watchdog1/access_cs0
82
+Date: August 2019
83
+Contact: Ivan Mikhaylov <i.mikhaylov@yadro.com>,
84
+ Alexander Amelkin <a.amelkin@yadro.com>
85
+Description:
86
+ It is a read/write file. This attribute exists only if the
87
+ system has booted from the alternate flash chip due to
88
+ expiration of a watchdog timer of AST2400/AST2500 when
89
+ alternate boot function was enabled with 'aspeed,alt-boot'
90
+ devicetree option for that watchdog or with an appropriate
91
+ h/w strapping (for WDT2 only).
92
+
93
+ At alternate flash the 'access_cs0' sysfs node provides:
94
+
95
+ ast2400:
96
+ a way to get access to the primary SPI flash
97
+ chip at CS0 after booting from the alternate
98
+ chip at CS1.
99
+ ast2500:
100
+ a way to restore the normal address mapping
101
+ from (CS0->CS1, CS1->CS0) to (CS0->CS0,
102
+ CS1->CS1).
103
+
104
+ Clearing the boot code selection and timeout counter also
105
+ resets to the initial state the chip select line mapping. When
106
+ the SoC is in normal mapping state (i.e. booted from CS0),
107
+ clearing those bits does nothing for both versions of the SoC.
108
+ For alternate boot mode (booted from CS1 due to wdt2
109
+ expiration) the behavior differs as described above.
110
+
111
+ This option can be used with wdt2 (watchdog1) only.
112
+
113
+ When read, the current status of the boot code selection is
114
+ shown. When written with any non-zero value, it clears
115
+ the boot code selection and the timeout counter, which results
116
+ in chipselect reset for AST2400/AST2500.