From: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc: Fix Book-E watchdog timer interval setting
Date: Thu, 7 Aug 2008 16:04:07 +0200 [thread overview]
Message-ID: <200808071604.07477.matthias.fuchs@esd-electronics.com> (raw)
In-Reply-To: <A4CCB071-0FCE-490A-B563-399FCA74C71E@kernel.crashing.org>
Sure,
the former line:
mtspr(SPRN_TCR, (mfspr(SPRN_TCR)&~WDTP(0))|WDTP(booke_wdt_period));
tries to mask the wdt interval period bits by and'ing with ~WDTP(0) which
is 0xffffffff. So no bits are cleared and or'ing a new value does not change anything.
The default interval is '3' which is the maximum, so any attempt to set a new
interval keeps the former '3'.
The patch correctly masks the period bits in SPRN_TCR before writing the new value.
That's all.
Matthias
On Thursday 07 August 2008 15:19, Kumar Gala wrote:
>
> On Aug 7, 2008, at 7:48 AM, Matthias Fuchs wrote:
>
> > This patch fixes the setting of the Book-E watchdog timer interval
> > setup
> > on initialization and by ioctl().
> >
> > Tested on PPC440EPx sequoia evaluation board.
> >
> > Signed-off-by: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
> > ---
> > drivers/watchdog/booke_wdt.c | 6 +++++-
> > 1 files changed, 5 insertions(+), 1 deletions(-)
>
> can you be more explicit about what the bug was.
>
> - k
>
>
next prev parent reply other threads:[~2008-08-07 14:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 12:48 [PATCH] powerpc: Fix Book-E watchdog timer interval setting Matthias Fuchs
2008-08-07 13:19 ` Kumar Gala
2008-08-07 14:04 ` Matthias Fuchs [this message]
2008-09-19 21:28 ` Matthias Fuchs
2008-09-19 21:44 ` Kumar Gala
2008-09-23 15:04 ` [PATCH V2] " Matthias Fuchs
2008-09-23 16:31 ` Timur Tabi
2008-11-03 8:56 ` Matthias Fuchs
2008-11-03 16:28 ` Timur Tabi
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=200808071604.07477.matthias.fuchs@esd-electronics.com \
--to=matthias.fuchs@esd-electronics.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).