Intel OpenBMC Linux kernel source tree (mirror) https://git.radix-linux.su/BMC/Intel-BMC/linux.git/atom?h=dev-4.10 2017-09-28T02:03:05+00:00 2017-09-28T02:03:05+00:00 Andrew Jeffery andrew@aj.id.au 2017-09-20T05:30:20+00:00 urn:sha1:a4c9af76ceec1d7f638da84dc8a0b8b7b3adb8ac Probing at device_initcall time lead to perverse cases where the watchdog was probed after, say, I2C devices, which then leaves a potentially running watchdog at the mercy of I2C device behaviour and bus conditions. Load the watchdog driver early to ensure that the kernel is patting it well before initialising peripherals. OpenBMC-Staging-Count: 1 Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Signed-off-by: Joel Stanley <joel@jms.id.au> 2017-09-28T02:03:03+00:00 Andrew Jeffery andrew@aj.id.au 2017-09-20T05:30:19+00:00 urn:sha1:0c62a91a9fbed30bc2132f5d9e2a0e4ae6c460e8 The driver also supports the watchdog in the AST25xx series, and may work on earlier SoCs as well. OpenBMC-Staging-Count: 1 Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Reviewed-by: Guenter Roeck <linux@roeck-us.net> Reviewed-by: Joel Stanley <joel@jms.id.au> Signed-off-by: Joel Stanley <joel@jms.id.au> 2017-09-28T02:02:59+00:00 Andrew Jeffery andrew@aj.id.au 2017-09-20T05:30:18+00:00 urn:sha1:4a702005d7abebf4a192f57161edacafceb84540 Apseed sounds like a good name for a web/mobile start-up incubator, but isn't a reflection of Aspeed themselves. OpenBMC-Staging-Count: 1 Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Reviewed-by: Guenter Roeck <linux@roeck-us.net> Reviewed-by: Joel Stanley <joel@jms.id.au> Signed-off-by: Joel Stanley <joel@jms.id.au> 2017-09-28T02:02:57+00:00 Andrew Jeffery andrew@aj.id.au 2017-09-20T05:30:17+00:00 urn:sha1:a6979cad6f5066a37ebd08d594e4b1c49446b29d An unintended post-condition of probe() is that the watchdog is disabled. This behaviour was introduced by an unnecessary write to the control register to configure the hardware based on the devicetree. The write is unnecessary because the cached control value that is manipulated by the code parsing the devicetree is eventually written by aspeed_wdt_enable(), which is when we care how the control register should be configured. Remove the write to restore expected behaviour. OpenBMC-Staging-Count: 1 Fixes: b7f0b8ad25f3 ("drivers/watchdog: ASPEED reference dev tree properties for config") Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Reviewed-by: Joel Stanley <joel@jms.id.au> Signed-off-by: Joel Stanley <joel@jms.id.au> 2017-07-31T23:42:24+00:00 Andrew Jeffery andrew@aj.id.au 2017-07-27T10:16:46+00:00 urn:sha1:daa8e9c37e3f4d1483b66f983a2e2a982720a46c Add support for configuring the drive strength and polarity on the AST2500, and the pulse duration on both the AST2400 and AST2500. OpenBMC-Staging-Count: 1 Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Tested-by: Matt Spinler <mspinler@linux.vnet.ibm.com> Signed-off-by: Joel Stanley <joel@jms.id.au> 2017-07-07T06:41:11+00:00 Christopher Bostic cbostic@linux.vnet.ibm.com 2017-07-07T00:49:00+00:00 urn:sha1:ede7ddfef3d95acf7ae992b0a313d691f99277f5 Reference the system device tree when configuring the watchdog engines. If property 'aspeed,reset_type' is present then set reset behavior based on the specified value. This can be one of three different mutually exclusive values * cpu - Reset CPU only on watchdog timeout * soc - Reset System on Chip * system - Full system reset No reset can also be specified by indicating: * none - No reset, assumes another watchdog is responsible for this. Add optional property 'aspeed,external-signal'. If present then configure to generate external signal on watchdog timeout. OpenBMC-Staging-Count: 1 Signed-off-by: Christopher Bostic <cbostic@linux.vnet.ibm.com> Signed-off-by: Joel Stanley <joel@jms.id.au> 2017-04-12T10:42:12+00:00 Krzysztof Kozlowski krzk@kernel.org 2017-04-04T19:32:35+00:00 urn:sha1:d0331c21a1a665f301529c47f5b626f135ab0f61 [ Upstream commit 0b445549ea6f91ffea78a976fe89b932db6e077a ] In soft (no-reboot) mode, the driver self-pings watchdog upon expiration of an interrupt. However the interrupt itself was not cleared thus on first hit, the system enters infinite interrupt handling loop. On Odroid U3 (Exynos4412), when booted with s3c2410_wdt.soft_noboot=1 argument the console is flooded: # killall -9 watchdog [ 60.523760] s3c2410-wdt 10060000.watchdog: watchdog timer expired (irq) [ 60.536744] s3c2410-wdt 10060000.watchdog: watchdog timer expired (irq) Fix this by writing something to the WTCLRINT register to clear the interrupt. The register WTCLRINT however appeared in S3C6410 so a new watchdog quirk and flavor are needed. Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org> Reviewed-by: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Sasha Levin <alexander.levin@verizon.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 2016-12-24T19:27:45+00:00 Linus Torvalds torvalds@linux-foundation.org 2016-12-24T19:27:45+00:00 urn:sha1:3a77fa854477a12fc543a69d00ff8a42adefc586 Pull watchdog updates from Wim Van Sebroeck and Guenter Roeck: - new driver for Add Loongson1 SoC - minor cleanup and fixes in various drivers * tag 'watchdog-for-linus-v4.10' of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging: watchdog: it87_wdt: add IT8620E ID watchdog: mpc8xxx: Remove unneeded linux/miscdevice.h include watchdog: octeon: Remove unneeded linux/miscdevice.h include watchdog: bcm2835_wdt: set WDOG_HW_RUNNING bit when appropriate watchdog: loongson1: Add Loongson1 SoC watchdog driver watchdog: cpwd: remove memory allocate failure message watchdog: da9062/61: watchdog driver intel-mid_wdt: Error code is just an integer intel-mid_wdt: make sure watchdog is not running at startup watchdog: mei_wdt: request stop on reboot to prevent false positive event watchdog: hpwdt: changed maintainer information watchdog: jz4740: Fix modular build watchdog: qcom: fix kernel panic due to external abort on non-linefetch watchdog: davinci: add support for deferred probing watchdog: meson: Remove unneeded platform MODULE_ALIAS watchdog: Standardize leading tabs and spaces in Kconfig file watchdog: max77620_wdt: fix module autoload watchdog: bcm7038_wdt: fix module autoload 2016-12-16T14:53:56+00:00 Maciej S. Szmigiero mail@maciej.szmigiero.name 2016-12-15T22:52:36+00:00 urn:sha1:067161281f428aa7c6e153e06aab7b5fe1ed1e98 This adds IT8620E chip ID to it87_wdt driver. Such chip is often found on current Gigabyte motherboards, it is allegedly custom made for this manufacturer. Upon testing it looks like it has a 16-bit timer and cannot be reset via game port (only via CIR), so it is similar to IT87{18,20,21,28,83} chips. Tested on GA-F2A88XM-HD3P board. Signed-off-by: Maciej S. Szmigiero <mail@maciej.szmigiero.name> Reviewed-by: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Guenter Roeck <linux@roeck-us.net> 2016-12-16T14:53:55+00:00 Corentin Labbe clabbe.montjoie@gmail.com 2016-12-15T18:03:44+00:00 urn:sha1:f01d74cc5a2aefa0ba16e2821086a1f2d0a2c899 watchdog/mpc8xxx_wdt.c does not use any miscdevice so this patch remove this unnecessary inclusion. Signed-off-by: Corentin Labbe <clabbe.montjoie@gmail.com> Reviewed-by: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Guenter Roeck <linux@roeck-us.net>