Linux MIPS Architecture development
 help / color / mirror / Atom feed
* does CP0_CAUSE gets set by spurious interrupts..?.
@ 2003-11-14  8:46 ashish  anand
  2003-11-14 11:21 ` Dominic Sweetman
  0 siblings, 1 reply; 2+ messages in thread
From: ashish  anand @ 2003-11-14  8:46 UTC (permalink / raw)
  To: linux-mips

[-- Attachment #1: Type: text/html, Size: 418 bytes --]

[-- Attachment #2: Type: text/plain, Size: 147 bytes --]

Hello,

would a spurious interrupt ( edge vs. level trigger mismatching) cause CP0_CAUSE to show any pending interupts.?

Best Regards,
Ashish

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: does CP0_CAUSE gets set by spurious interrupts..?.
  2003-11-14  8:46 does CP0_CAUSE gets set by spurious interrupts..? ashish  anand
@ 2003-11-14 11:21 ` Dominic Sweetman
  0 siblings, 0 replies; 2+ messages in thread
From: Dominic Sweetman @ 2003-11-14 11:21 UTC (permalink / raw)
  To: ashish  anand; +Cc: linux-mips


Ashish,

> would a spurious interrupt ( edge vs. level trigger mismatching)
> cause CP0_CAUSE to show any pending interupts.?

CP0_CAUSE reflects the real-time inputs to the CPU, not the state of
those inputs at the time the interrupt was detected, nor is it
sensitive to the "mask" bits in the status register.

So it's perfectly possible to find no active bits in CP0_CAUSE which
account for your interrupt.  But it does all depend how your interrupt
controller works...

--
Dominic Sweetman
MIPS Technologies

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2003-11-14 11:22 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-11-14  8:46 does CP0_CAUSE gets set by spurious interrupts..? ashish  anand
2003-11-14 11:21 ` Dominic Sweetman

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox