Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "ashish  anand" <ashish_ibm@rediffmail.com>
To: "Ralf Baechle" <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Assertion duration of edge interrupts can decrease spurious interrupts ..?
Date: 18 Nov 2003 06:57:41 -0000	[thread overview]
Message-ID: <20031118065741.27152.qmail@webmail29.rediffmail.com> (raw)

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

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

1.If i have a compulsion to use egde triggering peripheral on MIPS CP0,
would it be useful if i can increase the assertion duration of edge
interupts (this I can do) ..I mean to say probablity of loosing edge interrupts will decrasse.

2.does CP0 interrupt logic samples interrupts after each instruction or at some multiplication(..or division.?) of system clock.

Regards,
Ashish

On Mon, 17 Nov 2003 Ralf Baechle wrote :
>On Mon, Nov 17, 2003 at 11:40:11AM -0000, ashish  anand wrote:
>
> > I have a generic question regarding interrupt controler functionality
> > integrated in CP0 on mips architecture.
> > I don't see any interface to configure the edge/level triggering settings.
>
>MIPS only supports level triggered interrupts in coprocessor 0.
>
> > though in our BSP we take care of handling spurious interrupts , but is
> > this designed to be like that..?
>
>There is no handling needed.  If the processor takes an interrupt but none
>of the interrupt bits in c0_status is set, just return.  That's a legal
>condition.
>
> > I mean to ask , suppose I want to add a edge triggering peripheral.
> > to the extent of my understanding this will certainly generate the
> > spurious interrupts when coupled with a level triggering configuration
> > in CP0 (by default..?).
>
>You can directly sample the level of the edge irq in the interrupt bits in
>the cause register.  But that seems a fragile approach.
>
> > if i am handling through CP0_CAUSE or any other register inspection
> > that can work but I am loosing so many valid interupts which would have
> > been really valid with edge trigger pin of interrupt controller  .
> > further this type of handling is valid for actual spurious interrupts
> > not for those who are certain to be fired because of edge/level mismatching.
>
>If you really need to use an edge triggered interrupt on a MIPS then you
>probably want to use some circuit interrupt controller that converts the
>edge to a level triggered interrupt.
>
>   Ralf

             reply	other threads:[~2003-11-18  7:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-18  6:57 ashish  anand [this message]
2003-11-18 13:13 ` Assertion duration of edge interrupts can decrease spurious interrupts ..? Ralf Baechle

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=20031118065741.27152.qmail@webmail29.rediffmail.com \
    --to=ashish_ibm@rediffmail.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.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