All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jordan Crouse <jordan.crouse@amd.com>
To: Len Brown <lenb@kernel.org>
Cc: linux-acpi@vger.kernel.org,
	Marc Brooker <mbrooker@rrsg.ee.uct.ac.za>,
	Wim Van Sebroeck <wim@iguana.be>
Subject: Re: WDRT based watchdog timer
Date: Wed, 8 Oct 2008 14:44:22 -0600	[thread overview]
Message-ID: <20081008204422.GA2932@cosmic.amd.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0810081552220.3041@localhost.localdomain>

On 08/10/08 16:25 -0400, Len Brown wrote:
> 
> 
> On Fri, 26 Sep 2008, Jordan Crouse wrote:
> 
> > Attached is a patch to support watchdog timers as described
> > by the WDRT (Watch Dog Resource Table).  This has been tested on
> > the AMD SB600 chipset, but it should work for any chipset / BIOS
> > that implements the WDRT table.
> > 
> > I'm not in love with the name - but I couldn't think of anything
> > better, so I'm open to suggestions.  I have a limited number of
> > systems that implement this interface, so I would be very happy
> > to hear from other users, especially ones not using AMD chipsets.
> 
> While this driver depends on ACPI, it actually isn't part of ACPI.
> 
> Indeed, here is 100% of the ACPI spec support for this watchdog timer:
> 
> "WDRT" Watchdog Resource Table Watchdog Timer Hardware Requirements for
>                                Windows Server 2003
>                                http://www.microsoft.com/whdc/system/CEC/
>                                watchdog.mspx
> 
> so while the driver uses ACPI to enumerate the device,
> the device doesn't use any run-time ACPI support,
> and the Windows spec above actually defines the hardware.
> 
> > drivers/watchdog/acpiwdt.c
> 
> I'm not wild about having the string "acpi" be part of the driver name,
> config option, variable names etc.   Maybe the spec above which actually
> defines the timer would suggest a better name; or maybe simply
> name it after its configuration table, wrdt.c?

yeah - the string 'acpi' concerned as well.  I didn't want to really
call it win2k3wdt.c, though. :). 

> The spec URL should be in the driver comments or commit log, BTW.

Will do.

> I don't know who maintains /drivers/watchdog/,
> but Wim Van Sebroeck has scribbled there the most recently,
> and can probably weigh in on this.

Yeah - I forgot to CC him on my previous email, and I forwarded it
to him separately.  

> I searched my logs for WRDT and found only one,
> and it does happen to be one with an Intel processor --
> though an nvidia chipset:
> 
> http://bugzilla.kernel.org/show_bug.cgi?id=8950
> 
> so maybe Marc will be able to test the new driver?

Sure - once Wim sends his comments, I'll ping him.  Thanks.

Jordan

-- 
Jordan Crouse
Systems Software Development Engineer 
Advanced Micro Devices, Inc.


  parent reply	other threads:[~2008-10-08 20:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-26 23:27 [PATCH] WDRT based watchdog timer Jordan Crouse
2008-10-07  7:44 ` Andi Kleen
2008-10-07 15:39   ` Jordan Crouse
2008-10-08 20:25 ` [PATCH] " Len Brown
2008-10-08 20:36   ` Wim Van Sebroeck
2008-10-08 20:44   ` Jordan Crouse [this message]
2008-10-14 20:40     ` Wim Van Sebroeck
2008-10-15 13:33       ` Wim Van Sebroeck
2008-10-16 22:23         ` Len Brown
2008-10-16 22:40           ` Jordan Crouse
2009-01-12 20:27             ` Wim Van Sebroeck

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081008204422.GA2932@cosmic.amd.com \
    --to=jordan.crouse@amd.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mbrooker@rrsg.ee.uct.ac.za \
    --cc=wim@iguana.be \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.