From: Wan ZongShun <mcuos.com@gmail.com>
To: Wim Van Sebroeck <wim@iguana.be>
Cc: linux-arm-kernel <linux-arm-kernel@lists.arm.linux.org.uk>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Add watchdog driver for w90p910
Date: Wed, 5 Aug 2009 18:44:57 +0800 [thread overview]
Message-ID: <e68bb3470908050344u73cdb1c0o3257febee77d9f9f@mail.gmail.com> (raw)
In-Reply-To: <20090805103127.GF30892@infomag.iguana.be>
Dear Wim,
2009/8/5, Wim Van Sebroeck <wim@iguana.be>:
> Hi Wan,
>
> > > I have an additional question: which timeout values can you set? is it 0, 1, 2 and 3 seconds?
> >
> > The 0, 1, 2 and 3 is not seconds, rather than 'level' , it means my
> > watchdog controller can only set four grades,
> > When WTIS bit of REG_WTCR was set one value of the 0, 1, 2 and 3, the
> > real time interval can be calculated via following formula .
> >
> > WTIS real time interval (formula)
> > 0x00 ((2^ 14 ) * ((external crystal freq) / 256))seconds
> > 0x01 ((2^ 16 ) * ((external crystal freq) / 256))seconds
> > 0x02 ((2^ 18 ) * ((external crystal freq) / 256))seconds
> > 0x03 ((2^ 20 ) * ((external crystal freq) / 256))seconds
> >
> > The external crystal freq is 15Mhz in w90p910 evaluation board. so I
> > set the '0x00' as a default value, it means the real time interval is
> > 0.28 second approximately.
>
> Hmm, the watchdog API works in seconds.
> A timer will need to be used like in similar watchdog drivers (like at91sam9_wdt.c, pcwd.c).
Do you mean that we should provide userspace a setting seconds api?
it like following:
ioctl(fd, WDIOC_SETTIMEOUT,&value);
the value must be seconds?
Hmm, but the w90p910 only provides four grades seconds setting, rather
than all seconds time can be set, if so, how to write the wdt driver
so that the patch can be accepted for you?any idea?
>
> Kind regards,
> Wim.
>
>
--
Wan z.s
next prev parent reply other threads:[~2009-08-05 10:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-24 15:06 Wan ZongShun
2009-07-30 1:17 ` Wan ZongShun
2009-07-30 5:00 ` Wim Van Sebroeck
2009-07-30 5:03 ` Wan ZongShun
2009-08-04 20:10 ` Wim Van Sebroeck
2009-08-05 2:55 ` Wan ZongShun
2009-08-05 7:08 ` Wim Van Sebroeck
2009-08-05 8:00 ` Wan ZongShun
2009-08-05 10:31 ` Wim Van Sebroeck
2009-08-05 10:44 ` Wan ZongShun [this message]
2009-08-05 13:20 ` [PATCH v2] " Wan ZongShun
2009-08-17 2:40 ` Wan ZongShun
2009-08-17 9:14 ` Wim Van Sebroeck
2009-08-17 9:19 ` Wan ZongShun
2009-08-17 10:00 ` Wan ZongShun
2009-08-17 11:02 ` Wim Van Sebroeck
2009-08-17 11:04 ` Wan ZongShun
2009-08-05 11:37 ` [PATCH] " Wan ZongShun
2009-08-20 12:16 ` 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=e68bb3470908050344u73cdb1c0o3257febee77d9f9f@mail.gmail.com \
--to=mcuos.com@gmail.com \
--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
all inboxes | Powered by JetHome®