- 28 Dec, 2015 14 commits
-
-
Guenter Roeck authored
The device pointer in struct watchdog_device has a different lifetime than the driver code and should not be used in drivers. Use the pointer to the parent device instead. Signed-off-by:
Guenter Roeck <linux@roeck-us.net> Signed-off-by:
Wim Van Sebroeck <wim@iguana.be>
-
Guenter Roeck authored
The device pointer in struct watchdog_device should not be used by drivers and may be removed in the near future. Use the platform device pointer for info messages instead. Signed-off-by:
-
Guenter Roeck authored
Stopping a watchdog is a normal operation and does not warrant a log message. Signed-off-by:
-
Mans Rullgard authored
This adds a binding for the watchdog in Sigma Designs SMP8642 and similar devices. Signed-off-by:
Mans Rullgard <mans@mansr.com> Signed-off-by:
-
Mans Rullgard authored
This adds support for the Sigma Designs SMP86xx/SMP87xx family built-in watchdog. Signed-off-by:
-
Martyn Welch authored
This patchs adds documentation for the binding of the Zodiac RAVE Switch Watchdog Processor. This is an i2c based watchdog. Cc: Pawel Moll <pawel.moll@arm.com> Cc: Mark Rutland <mark.rutland@arm.com> Cc: Ian Campbell <ijc+devicetree@hellion.org.uk> Cc: Kumar Gala <galak@codeaurora.org> Cc: devicetree@vger.kernel.org Signed-off-by:
Martyn Welch <martyn.welch@collabora.co.uk> Acked-by:
Rob Herring <robh@kernel.org> Signed-off-by:
-
Martyn Welch authored
This patch adds a driver for the Zodiac Aerospace RAVE Watchdog Procesor. This device implements a watchdog timer, accessible over I2C. Signed-off-by:
-
Oleksij Rempel authored
Signed-off-by:
Oleksij Rempel <linux@rempel-privat.de> Signed-off-by:
-
Oleksij Rempel authored
Add WD support for Alphascale asm9260 SoC. This driver provide support for different function modes: - HW mode to trigger SoC reset on timeout - SW mode do soft reset if needed - DEBUG mode Signed-off-by:
-
Damien Riegel authored
This watchdog is instantiated in a FPGA that is memory mapped. It is made of only one register, called the feed register. Writing to this register will re-arm the watchdog for a given time (and enable it if it was disable). It can be disabled by writing a special value into it. It is part of a syscon block, and the watchdog register offset in this block varies from board to board. This offset is passed in the syscon property after the phandle to the syscon node. Signed-off-by:
Damien Riegel <damien.riegel@savoirfairelinux.com> Acked-by:
-
Guo Zeng authored
This patch adds watchdog driver for CSRatlas7 platform. On CSRatlas7, the 6th timer can act as a watchdog timer when the Watchdog mode is enabled. Signed-off-by:
Guo Zeng <Guo.Zeng@csr.com> Signed-off-by:
William Wang <William.Wang@csr.com> Signed-off-by:
Barry Song <Baohua.Song@csr.com> Signed-off-by:
-
Carlo Caione authored
Add SoC specific data in the watchdog driver for the meson8b SoC. Signed-off-by:
Carlo Caione <carlo@endlessm.com> Signed-off-by:
-
Carlo Caione authored
With this patch we refactor the driver code to enable watchdog support for all platforms based on Amlogic meson SoCs. The new default timeout is also now chosen considering the maximum timeout allowed by the SoC. Signed-off-by:
-
Mingarelli, Thomas authored
This patch is for the rebranding changes for the corporate split at HP. There are no functional changes with this patch. Signed-off-by:
Tom Mingarelli <thomas.mingarelli@hpe.com> Signed-off-by:
-
- 27 Dec, 2015 11 commits
-
-
Geliang Tang authored
Use to_platform_device() instead of open-coding it. Signed-off-by:
Geliang Tang <geliangtang@163.com> Signed-off-by:
-
Uwe Kleine-König authored
With the early_enable module parameter the watchdog can be started during driver probe time. If this is requested the bets are good that the timer is already running, so to narrow the gap where the timer is disabled only call the disable function when the timer shouldn't be started. Signed-off-by:
Uwe Kleine-König <u.kleine-koenig@pengutronix.de> Signed-off-by:
-
Uwe Kleine-König authored
omap_wdt_start calls pm_runtime_get_sync so dropping a reference just before calling omap_wdt_start doesn't make much sense. Moreover there is no point to use the synchronous variant of pm_runtime_put because the driver doesn't care if the clock is disabled before or after omap_wdt_probe returns. Signed-off-by:
-
Jisheng Zhang authored
On 64bit platforms, "(1 << (16 + top)) / clk_get_rate(dw_wdt.clk)" is sign-extended to 64bit then converted to unsigned 64bit, finally divide the clk rate. If the top is the maximum TOP i.e 15, "(1 << (16 +15))" will be sign-extended to 0xffffffff80000000, then converted to unsigned 0xffffffff80000000, which is a huge number, thus the final result is wrong. We fix this issue by giving usigned value(1U in this case) at first. Let's assume clk rate is 25MHZ, Before the patch: dw_wdt_top_in_seconds(15) = -864612050 After the patch: dw_wdt_top_in_seconds(15) = 85 Signed-off-by:
Jisheng Zhang <jszhang@marvell.com> Signed-off-by:
-
Li RongQing authored
the softdog has static variables which are accessed if its timer is still running after the driver is unloaded. and lead to crash: $modprobe softdog $echo 1 >/dev/watchdog $modprobe -r softdog CPU 20 Unable to handle kernel paging request at virtual address Oops[#1]: CPU: 20 PID: 0 Comm: swapper/20 Not tainted 4.1.13-WR8.0.0.0_standard ... Modules linked in: [last unloaded: softdog] .... Call Trace: [<ffffffff801e142c>] cascade+0x34/0xb0 [<ffffffff801e1964>] run_timer_softirq+0x30c/0x368 [<ffffffff80181044>] __do_softirq+0x1ec/0x418 [<ffffffff801815d0>] irq_exit+0x90/0x98 [<ffffffff8010749c>] plat_irq_dispatch+0xa4/0x140 [<ffffffff80152740>] ret_from_irq+0x0/0x4 [<ffffffff801529e0>] __r4k_wait+0x20/0x40 [<ffffffff801c2278>] cpu_startup_entry+0x2a0/0x368 [<ffffffff8015fa64>] start_secondary+0x444/0x4d8 add the module ref when timer is running to avoid to unload the softdog module Signed-off-by:Li RongQing <roy.qing.li@gmail.com> Signed-off-by:
-
Harald Geyer authored
This allows the system to actually halt even if userspace forgot to disable the watchdog first. Old behaviour was that the watchdog forced the system to boot again. Signed-off-by:
Harald Geyer <harald@ccbib.org> Signed-off-by:
-
Huang Rui authored
For SB800 and later chipsets, the register definitions are the same with SB800. And for SB700 and older chipsets, the definitions should be same with SP5100/SB7x0. Signed-off-by:
Huang Rui <ray.huang@amd.com> Cc: Denis Turischev <denis.turischev@compulab.co.il> Signed-off-by:
-
Huang Rui authored
sp5100_tco watchdog is also supported on AMD KernCZ chipset of Carrizo platform. Signed-off-by:
-
Denis Turischev authored
AMD Mullins watchdog is fully compatible to the previous Hudson chipset, reuse the existent sp5100_tco driver. Signed-off-by:
Denis Turischev <denis.turischev@compulab.co.il> Signed-off-by:
-
Pratyush Anand authored
This patch adds following attributes to watchdog device's sysfs interface to read its different status. * state - reads whether device is active or not * identity - reads Watchdog device's identity string. * timeout - reads current timeout. * timeleft - reads timeleft before watchdog generates a reset * bootstatus - reads status of the watchdog device at boot * status - reads watchdog device's internal status bits * nowayout - reads whether nowayout feature was set or not Testing with iTCO_wdt: # cd /sys/class/watchdog/watchdog1/ # ls bootstatus dev device identity nowayout power state subsystem timeleft timeout uevent # cat identity iTCO_wdt # cat timeout 30 # cat state inactive # echo > /dev/watchdog1 # cat timeleft 26 # cat state active # cat bootstatus 0 # cat nowayout 0 Signed-off-by:
Pratyush Anand <panand@redhat.com> Reviewed-by:
-
Pratyush Anand authored
We need few sysfs attributes to know different status of a watchdog device. To do that, we need to associate .dev_groups with watchdog_class. So convert it from pointer to static. Putting this static struct in watchdog_dev.c, so that static device attributes defined in that file can be attached to it. Signed-off-by:
-
- 13 Dec, 2015 15 commits
-
-
Damien Riegel authored
Get rid of the custom reboot notifier block registration and use the one provided by the watchdog core. Signed-off-by:
Vivien Didelot <vivien.didelot@savoirlinux.com> Reviewed-by:
-
Damien Riegel authored
Get rid of the custom reboot notifier block registration and use the one provided by the watchdog core. Signed-off-by:
-
Damien Riegel authored
Get rid of the custom reboot notifier block registration and use the one provided by the watchdog core. Note that this watchdog used to stop unconditionnaly on SYS_HALT and SYS_POWER_OFF. The core function now calls ops->stop on SYS_HALT and SYS_DOWN. To prevent the watchdog from being stopped on reboot, the "always-running" property must be set, otherwise it will now be stopped. Signed-off-by:
-
Damien Riegel authored
Get rid of the custom reboot notifier block registration and use the one provided by the watchdog core. Signed-off-by:
-
Damien Riegel authored
Get rid of the custom reboot notifier block registration and use the one provided by the watchdog core. Signed-off-by:
-
Damien Riegel authored
Many watchdog drivers register a reboot notifier in order to stop the watchdog on system reboot. Thus we can factorize this code in the watchdog core. For that purpose, a new notifier block is added in watchdog_device for internal use only, as well as a new watchdog_stop_on_reboot helper function. If this helper is called, watchdog core registers the related notifier block and will stop the watchdog when SYS_HALT or SYS_DOWN is received. Since this operation can be critical on some platforms, abort the device registration if the reboot notifier registration fails. Suggested-by:
Vivien Didelot <vivien.didelot@savoirfairelinux.com> Signed-off-by:
-
Damien Riegel authored
Get rid of the custom restart handler by using the one provided by the watchdog core. Signed-off-by:
-
Damien Riegel authored
Get rid of the custom restart handler by using the one provided by the watchdog core. Signed-off-by:
-
Damien Riegel authored
Get rid of the custom restart handler by using the one provided by the watchdog core. Signed-off-by:
-
Damien Riegel authored
Get rid of the custom restart handler by using the one provided by the watchdog core. Signed-off-by:
-
Damien Riegel authored
Get rid of the custom restart handler by using the one provided by the watchdog core. Signed-off-by:
-
Damien Riegel authored
Get rid of the custom restart handler by using the one provided by the watchdog core. Signed-off-by:
-
Damien Riegel authored
Get rid of the custom restart handler by using the one provided by the watchdog core. Signed-off-by:
-
Damien Riegel authored
Get rid of the custom restart handler by using the one provided by the watchdog core. Signed-off-by:
-
Damien Riegel authored
Get rid of the custom restart handler by using the one provided by the watchdog core. Signed-off-by:
-
