From: r.marek@sh.cvut.cz (Rudolf Marek)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] w83792d watchdog
Date: Wed, 29 Mar 2006 22:38:39 +0000 [thread overview]
Message-ID: <442B0C6F.4080604@sh.cvut.cz> (raw)
Hello all,
I begun to work on the watchdog support for w83792d. I have several questions about the watchdog device in w83792d. Please can
yuou forward them to responsible person?
I'm using ver 1.0 of datasheet
There are 4 watchdog regs:
CR01 handles the unlock codes
CR02 "Watch Dog Enable" -> this should be more likely called "Watch Dog Enable Status" - because this regs are RO only
CR03 is quite mystery for me
the "WDT stage" is not described in datasheet at all, I assume this has someting to do with hard mode of watchdog
the HARD_TO and SOFT_TO have following commnents:
HARD_TO: 1: a hard timeout occurs. This bit will be cleared while reading.
What I know:
1) this bit is not cleared on reading
2) I think the sentece should be: "a hard timeoud had occured"
because this is set when there was a timeout/reset it seems
This is so far to datasheet, now to real funcs:
1) What will happen if I enable hard and soft watchdog same time? (i'm disabling the hard watchdog timer in first place so
it should not be an issue but you never know)
2) I tried many ways to reset the watchdog timer but only seems to work is to write 0xAA to CR1 and then 0x55 to re-enable it.
This seems bit strange because the computer can fail just in between of this two writes Yes I know this is not probable, but
the best method is just to re-write the timeout value or rewrite the enable (0x55) - as others might do. Were there
some strange reason for this design?
And last thing, It seems that the device registers survive system power cycle. Maybe I was just too fast and the caps powered
the chip. I will investigate...
I hope you can understand my thought because I'm quite tired now.
regards
Rudolf
next reply other threads:[~2006-03-29 22:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-29 22:38 Rudolf Marek [this message]
2006-03-30 1:37 ` [lm-sensors] w83792d watchdog dezheng shen
2006-04-07 10:43 ` Rudolf Marek
2006-04-10 10:28 ` Ymu
2006-04-10 10:45 ` Rudolf Marek
2006-04-11 18:34 ` Rudolf Marek
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=442B0C6F.4080604@sh.cvut.cz \
--to=r.marek@sh.cvut.cz \
--cc=lm-sensors@vger.kernel.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 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.