mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Andrew Victor" <avictor.za@gmail.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
	wim@iguana.be, linux-arm-kernel@lists.arm.linux.org.uk,
	linux-kernel@vger.kernel.org
Subject: Re: AT91SAM9/CAP9 watchdog driver
Date: Wed, 4 Jun 2008 21:02:30 +0200	[thread overview]
Message-ID: <cd73a99e0806041202v592c41e1ya3c9fa51918efb0f@mail.gmail.com> (raw)
In-Reply-To: <20080604192458.02f76022@core>

hi Alan ,

> Every other watchdog behaves as follows
>
> - If you specify a bogus value it doesn't load
> - If you specify no value you get a valid default
> - If you specify a valid value you get that
>
> I don't believe yours should be different.

I don't think any other in-kernel watchdog driver has to deal with
write-once hardware.  On these processors once the watchdog register
is programmed, it cannot be disabled or re-programmed.
If the above behaviour is required, then we might aswell remove the
ioctl(WDIOC_SETTIMEOUT) interface for this driver since if the user
wants anything other than the default timeout they would need to pass
it via the kernel command-line or module parameters.


Regards,
  Andrew Victor

  reply	other threads:[~2008-06-04 19:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-01 16:40 Andrew Victor
2008-06-02  6:58 ` Alan Cox
2008-06-03 21:23 ` Andrew Morton
2008-06-04  7:31   ` Andrew Victor
2008-06-04 11:36     ` Alan Cox
2008-06-04 18:36       ` Andrew Victor
2008-06-04 18:24         ` Alan Cox
2008-06-04 19:02           ` Andrew Victor [this message]
2008-06-04 19:18             ` Alan Cox
2008-06-07  6:39 ` David Brownell

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=cd73a99e0806041202v592c41e1ya3c9fa51918efb0f@mail.gmail.com \
    --to=avictor.za@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome