Lines Matching +full:reset +full:- +full:on +full:- +full:timeout
7 * on the Sibyte 12XX and 11XX SoCs available to the user. There are two
8 * such devices available on the SoC, but it seems that there isn't an
13 * I have not tried this driver on a 1480 processor; it might work
18 * is reset and there is no way to redirect that NMI. Which could
19 * be problematic in some cases where this chip is sitting on the HT
21 * Since the reset can't be redirected to the external reset pin, it is
22 * possible that other HT connected processors might hang and not reset.
23 * For Linux, a soft reset would probably be even worse than a hard reset.
35 * Based on various other watchdog drivers, which are probably all
36 * loosely based on something Alan Cox wrote years ago.
74 __raw_writeq(t & 0x7fffffUL, wdog - 0x10); in sbwdog_set()
94 static unsigned long timeout = 0x7fffffUL; /* useconds: 8.3ish secs. */ variable
110 return -EBUSY; in sbwdog_open()
116 sbwdog_set(user_dog, timeout); in sbwdog_open()
142 * 42 - the answer
159 return -EFAULT; in sbwdog_write()
172 int ret = -ENOTTY; in sbwdog_ioctl()
179 ret = copy_to_user(argp, &ident, sizeof(ident)) ? -EFAULT : 0; in sbwdog_ioctl()
199 ret = -EINVAL; in sbwdog_ioctl()
202 timeout = time; in sbwdog_ioctl()
203 sbwdog_set(user_dog, timeout); in sbwdog_ioctl()
212 ret = put_user((u32)__raw_readq(user_dog - 8) / 1000000, p); in sbwdog_ioctl()
258 * code can use it to re-up the watchdog, thereby saving the kernel from
269 wd_init = __raw_readq(wd_cfg_reg - 8) & 0x7fffff; in sbwdog_interrupt()
275 pr_crit("%s in danger of initiating system reset " in sbwdog_interrupt()
308 pr_err("%s: failed to request irq 1 - %d\n", in sbwdog_init()
315 pr_info("%s: timeout is %ld.%ld secs\n", in sbwdog_init()
317 timeout / 1000000, (timeout / 100000) % 10); in sbwdog_init()
340 module_param(timeout, ulong, 0);
341 MODULE_PARM_DESC(timeout,
342 "Watchdog timeout in microseconds (max/default 8388607 or 8.3ish secs)");
357 pr_crit("Watchdog IRQ zero(0) failed to be requested - %d\n", ret);