public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Padraig Brady <padraig@antefacto.com>
To: Matt_Domsch@Dell.com
Cc: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org,
	nils@kernelconcepts.de, giometti@ascensit.com, pb@nexus.co.uk,
	chowes@vsol.net, gorgo@itc.hu, info@itc.hu,
	lethal@chaoticdreams.org, woody@netwinder.org,
	johnsonm@redhat.com
Subject: Re: [CFT][PATCH] watchdog nowayout and timeout module parameters
Date: Tue, 15 Jan 2002 12:23:06 +0000	[thread overview]
Message-ID: <3C441F2A.50203@antefacto.com> (raw)
In-Reply-To: <71714C04806CD5119352009027289217022C4115@ausxmrr502.us.dell.com>

Matt_Domsch@Dell.com wrote:

>>Timeout has been moved to an ioctl more by other diffs so Im not sure
>>timeout= is too important
>>
> 
> Of the seven drivers I added this parm to, six do not offer such a method
> via ioctl:
> eurotechwdt.c provides WDIOC_SETTIMEOUT.


And was the first to provide it:
http://marc.theaimsgroup.com/?l=linux-kernel&m=100619600900700&w=2


> acquirewdt.c, advantechwdt.c, ib700wdt.c, pcwd.c, wdt.c, wdt_pci.c do not
> provide a set timeout ioctl.


I think all should? As it would be nice/more consistent for all


> 
> These already offer a timeout parm, but no set timeout ioctl:
> i810-tco.c, softdog.c, wdt285.o
> 
> The other drivers I didn't add timeout parm to anyhow, but they don't have a
> set timeout ioctl either:
> machzwd.c, mixcomwd.c, shwdt.c, wdt977.c


new version of wdt977 in patch does provide WDIOC_SETTIMEOUT


> 
> Unless there are strong objections or a push to make it an ioctl everywhere
> instead/also, I'd like to leave it in.


Personally I'm undecided whether param or ioctl is preferable.

I don't think many would need to change the timeout parameter
at runtime, but if you do it's a pain to reload the module,
so I vote for providing both interfaces?


> 
>>Rest looks good
>>
> 
> Thanks for reviewing and approving.  14 drivers modified, 5 drivers
> approved, one investigating, two email addresses invalid, leaving 6 to hear
> from.
> 
> -Matt

What about the following though?

cpwatchdog.c
riowatchdog.c
sbc60xxwdt.c

Actually I think there should be a drivers/char/watchdog directory ?
(there are now around 18 seperate watchdog drivers).
Then the out of date watchdog.txt could be updated to point users
at this directory to see what's available, rather than the current
out of date list:

	ICS	WDT501-P
	ICS	WDT501-P (no fan tachometer)
	ICS	WDT500-P
	Software Only
	SA1100 Internal Watchdog
	Berkshire Products PC Watchdog Revision A & C (by Ken Hollis)

ALso I've drivers here for {IBASE, Portwell} SBC watchdogs.
[Who] will I submit them to?

cheers,
Padraig.


  reply	other threads:[~2002-01-15 12:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-18 20:08 [CFT][PATCH] watchdog nowayout and timeout module parameters Matt_Domsch
2002-01-15 12:23 ` Padraig Brady [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-03 23:05 Matt_Domsch
2001-12-17 18:32 Matt Domsch
2001-12-18 15:08 ` Alan Cox

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=3C441F2A.50203@antefacto.com \
    --to=padraig@antefacto.com \
    --cc=Matt_Domsch@Dell.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=chowes@vsol.net \
    --cc=giometti@ascensit.com \
    --cc=gorgo@itc.hu \
    --cc=info@itc.hu \
    --cc=johnsonm@redhat.com \
    --cc=lethal@chaoticdreams.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nils@kernelconcepts.de \
    --cc=pb@nexus.co.uk \
    --cc=woody@netwinder.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox