From: "Hasan Rashid" <hasan@digitalpath.net>
To: linux-kernel@vger.kernel.org
Subject: Write to MFGPT_NR_MSR causes immediate hard reset
Date: Wed, 23 Jan 2008 15:37:29 -0800 (PST) [thread overview]
Message-ID: <2414.65.164.104.9.1201131449.squirrel@webmail.digitalpath.net> (raw)
Hi,
I back ported the CS5536 MFGPT based watchdog timer from Kernel 2.6 to
Kernel 2.4 (I have to). I am using the Alix2c0 board with TinyBios v0.99.
I have been following the discussion on this thread Re: 2.6.24-rc8 hangs
at mfgpt-timer". I disabled the MFGPT workaround in the BIOS and it seems
to load the module just fine (no more hangs). I get this when I load
geode-mfgpt.o:
################
Found vendor: 0x1022h, device: 0x2090h
reading from: 6206 reading from: 620e reading from: 6216 reading from:
621e reading from: 6226 reading from: 622e reading from: 6236 reading
from: 623e
geode-mfgpt: 8 timers available.
And when I load the watchdog module geodewdt.o:
geode-mfgpt: Registered timer 0
written to: 6206 -- just something I am doing to verify the write
operation written to: 6202
Everything seems to be fine except when I try to setup a bit in
MFGPT_NR_MSR that allows MFGPT0_CMP2 to perform a hard reset when the
event fires, it resets it right away.
/* Set up comparator 2 to reset when the event fires */
// geode_mfgpt_set_event(wdt_timer, MFGPT_CMP2, MFGPT_EVENT_RESET);
I am not sure if the Clock Switch section 5.16.3 in the CS5536 data book,
pointed by Willy Tarreau in one of his posts, is related to it. When the
API module is loaded, it only executes read instructions on the
MFGPT_REG_SETUP registers. Can anyone speculate as to why the board resets
as soon as the watchdog timer module executes the geode_mfgpt_set_event
function? Basically when this function is called, (0x100000)h is written
to the MFGPT_NR_MSR register.
TIA.
Regards,
Hasan Rashid
Embedded Systems Software Engineer
reply other threads:[~2008-01-23 23:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2414.65.164.104.9.1201131449.squirrel@webmail.digitalpath.net \
--to=hasan@digitalpath.net \
--cc=linux-kernel@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 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®