From: Carsten Juttner <carjay@gmx.net>
To: linuxppc-embedded@ozlabs.org
Subject: Patch for 8xx watchdog handler for >=2.6.10
Date: Fri, 11 Feb 2005 07:16:43 +0100 [thread overview]
Message-ID: <420C4DCB.6030104@gmx.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 474 bytes --]
Hi,
our mpc 823 based embedded board (STB, dbox2) would hang with every
kernel starting from 2.6.10-rc1_linuxppc. I tracked the problem down to
the watchdog interrupt handler setup and the new generic interrupt
handling routines (which caused an uninitialized pointer because kmalloc
was used before the kmem_cache was initialized).
As said, this was only an issue if CONFIG_8xx_WDT was set.
I have attached a simple patch for the handler.
Regards,
Carsten Juttner
[-- Attachment #2: m8xx_wdt.diff --]
[-- Type: text/x-patch, Size: 1183 bytes --]
diff -Nru a/arch/ppc/syslib/m8xx_wdt.c b/arch/ppc/syslib/m8xx_wdt.c
--- a/arch/ppc/syslib/m8xx_wdt.c 2005-02-11 07:08:20 +01:00
+++ b/arch/ppc/syslib/m8xx_wdt.c 2005-02-11 07:08:20 +01:00
@@ -11,6 +11,7 @@
#include <linux/init.h>
#include <linux/interrupt.h>
+#include <linux/irq.h>
#include <linux/kernel.h>
#include <linux/sched.h>
#include <asm/8xx_immap.h>
@@ -18,6 +19,14 @@
static int wdt_timeout;
+static irqreturn_t m8xx_wdt_interrupt(int, void *, struct pt_regs *);
+static struct irqaction m8xx_wdt_irqaction = {
+ .handler = m8xx_wdt_interrupt,
+ .flags = 0,
+ .name = "watchdog",
+ .dev_id = NULL
+};
+
void m8xx_wdt_reset(void)
{
volatile immap_t *imap = (volatile immap_t *)IMAP_ADDR;
@@ -84,8 +93,8 @@
imap->im_sit.sit_piscr =
(mk_int_int_mask(PIT_INTERRUPT) << 8) | PISCR_PIE | PISCR_PTE;
- if (request_irq(PIT_INTERRUPT, m8xx_wdt_interrupt, 0, "watchdog", NULL))
- panic("m8xx_wdt: could not allocate watchdog irq!");
+ if (setup_irq(PIT_INTERRUPT, &m8xx_wdt_irqaction))
+ panic("m8xx_wdt: error setting up the watchdog irq!");
printk(KERN_NOTICE
"m8xx_wdt: keep-alive trigger installed (PITC: 0x%04X)\n", pitc);
reply other threads:[~2005-02-11 6:50 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=420C4DCB.6030104@gmx.net \
--to=carjay@gmx.net \
--cc=linuxppc-embedded@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).