diff options
Diffstat (limited to 'Documentation/watchdog/convert_drivers_to_kernel_api.txt')
| -rw-r--r-- | Documentation/watchdog/convert_drivers_to_kernel_api.txt | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/Documentation/watchdog/convert_drivers_to_kernel_api.txt b/Documentation/watchdog/convert_drivers_to_kernel_api.txt index ae1e90036d06..be8119bb15d2 100644 --- a/Documentation/watchdog/convert_drivers_to_kernel_api.txt +++ b/Documentation/watchdog/convert_drivers_to_kernel_api.txt | |||
| @@ -163,6 +163,25 @@ Here is a simple example for a watchdog device: | |||
| 163 | +}; | 163 | +}; |
| 164 | 164 | ||
| 165 | 165 | ||
| 166 | Handle the 'nowayout' feature | ||
| 167 | ----------------------------- | ||
| 168 | |||
| 169 | A few drivers use nowayout statically, i.e. there is no module parameter for it | ||
| 170 | and only CONFIG_WATCHDOG_NOWAYOUT determines if the feature is going to be | ||
| 171 | used. This needs to be converted by initializing the status variable of the | ||
| 172 | watchdog_device like this: | ||
| 173 | |||
| 174 | .status = WATCHDOG_NOWAYOUT_INIT_STATUS, | ||
| 175 | |||
| 176 | Most drivers, however, also allow runtime configuration of nowayout, usually | ||
| 177 | by adding a module parameter. The conversion for this would be something like: | ||
| 178 | |||
| 179 | watchdog_set_nowayout(&s3c2410_wdd, nowayout); | ||
| 180 | |||
| 181 | The module parameter itself needs to stay, everything else related to nowayout | ||
| 182 | can go, though. This will likely be some code in open(), close() or write(). | ||
| 183 | |||
| 184 | |||
| 166 | Register the watchdog device | 185 | Register the watchdog device |
| 167 | ---------------------------- | 186 | ---------------------------- |
| 168 | 187 | ||
