Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759209AbeAIXhI (ORCPT + 1 other); Tue, 9 Jan 2018 18:37:08 -0500 Received: from mail-pg0-f68.google.com ([74.125.83.68]:41646 "EHLO mail-pg0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758448AbeAIXhG (ORCPT ); Tue, 9 Jan 2018 18:37:06 -0500 X-Google-Smtp-Source: ACJfBosAb9x6JaOV0QozJ57RDmX7GoXMpDrpMj1EPXX/XdoEWl9WjP1q9DhOkgysmmghkZgJdGfkWQ== Date: Tue, 9 Jan 2018 15:37:03 -0800 From: Guenter Roeck To: Lyude Paul Cc: Wim Van Sebroeck , linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org, =?iso-8859-1?B?Wm9sdOFuIEL2c3r2cm3pbnlp?= Subject: Re: [11/12] watchdog: sp5100-tco: Abort if watchdog is disabled by hardware Message-ID: <20180109233703.GD26819@roeck-us.net> References: <1514149457-20273-12-git-send-email-linux@roeck-us.net> <1515538687.4373.18.camel@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1515538687.4373.18.camel@redhat.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: Hi, On Tue, Jan 09, 2018 at 05:58:07PM -0500, Lyude Paul wrote: > Hi! I'm the one from the Fedora bugzilla who said they'd help review these > patches. I might end up responding to this with a real review comment after > this message, but first: > > mind cc'ing me future versions of this patchset and also, is there any way you Sure. > know of that one could figure out whether or not the sp5100_tco wdt is > actually disabled by the OEM on a board? I tried testing these patches with my That is what the code is trying to do today. > system and it appears to be convinced that it's disabled on my system, but I'm > hoping something in this patch is just broken… > I tested the driver on three different boards. MSI B350M MORTAR, MSI B350 TOMAHAWK, and Gigabyte AB350M-Gaming 3. CPU is Ryzen 1700X on all boards. On the MSI boards, the watchdog is reported as disabled. Enabling it and letting it expire does not have an effect. I am using the Super-IO watchdog instead on those boards (and it works). On the Gigabyte board, the watchdog is reported as enabled, and it works (and the watchdog on the Super-IO chips does not work). Feel free to play with the driver. Maybe there is a means to enable the watchdog if it is disabled. Unfortunately, I was unable to figure out how to do it, so I thought it is better to report the fact and not instantiate the watchdog if it doesn't work. Hope this helps, Guenter