linux-mips
[Top] [All Lists]

Re: IRQ problem on cobalt / 2.6.6

To: Ralf Baechle <ralf@linux-mips.org>
Subject: Re: IRQ problem on cobalt / 2.6.6
From: Peter Horton <phorton@bitbox.co.uk>
Date: Mon, 17 May 2004 09:40:33 +0100
Cc: Kieran Fulke <kieran@pawsoff.org>, linux-mips@linux-mips.org
In-reply-to: <20040516170445.GA4793@linux-mips.org>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20040513183059.GA25743@getyour.pawsoff.org> <40A478B0.3070005@bitbox.co.uk> <20040516113622.GA14049@getyour.pawsoff.org> <20040516152113.GA9390@convergence.de> <20040516170445.GA4793@linux-mips.org>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mozilla Thunderbird 0.6 (Windows/20040502)
Ralf Baechle wrote:

On Sun, May 16, 2004 at 05:21:13PM +0200, Johannes Stezenbach wrote:

In essence, I believe something other than the saa7146 must be asserting
irq 23.  Or is it possible that a bug in the PCI init stuff in
saa7146_core.c can
cause this? Any hints how we could debug this would be welcome.

arch/mips/cobalt/irq.c:cobalt_irq() looks pretty suspect.  It connects
CAUSEF_IP7 and interrupt 23 - but the CPU's builtin count / compare
interrupt already uses this bit.

Sharing the timer interrupt with something else isn't impossible but seems
a less than bright thing to do.  Somebody with production hw to test
should compare this interrupt dispatch function with old working code
from 2.2 or 2.4 ...


I've got no hardware here but the code looks roughly similiar

As the Cobalt's use Galileo timer 0 for clock interrupts we could use Galileo rather than count/compare for the HPT.

Precision would be 50MHz rather than 125MHz but that shouldn't be a problem :-)

P.

<Prev in Thread] Current Thread [Next in Thread>