Re: ARM Interrupts

Andrew Blackburn wrote:
Hi there

Looking at several processors at the moment but ARM7 and Coldfire in particular. I like the popularity of ARM and associated tools, but cant get over the fact that the interrupt structure within them (only two priority levels) is pants. Coldfire has 7 or 8 nestable levels.

I would appreciate anyones view on this.


Please remember thet the ARM is a processor core only.
It is usually embedded as part of a larger chip containing
a bunch of necessary peripherals, including an interrupt
controller.

For examples, get the data for Atmel AT91 series chips.

The need for several nested interrupt levels usually
comes from an attempt to avoid a thread scheduler or
attempt to do wrong things in the interrupt service.

--

Tauno Voipio
tauno voipio (at) iki fi

.

Relevant Pages

  • Re: ARM Interrupts
    ... I like the popularity of ARM and associated tools, ... over the fact that the interrupt structure within them (only two priority ... Coldfire has 7 or 8 nestable levels. ... really be task bodies at above user level. ...
    (comp.arch.embedded)
  • Re: ARM Interrupts
    ... I like the popularity of ARM and associated tools, ... Coldfire has 7 or 8 nestable levels. ... a very capable interrupt controller. ...
    (comp.arch.embedded)
  • tricky challenge for getting round level-driven interrupt problem: help!
    ... ARM processor. ... this stupid hardware design - in order to make a RELIABLE, ... in on the ARM's 8-bit port. ... a "write" interrupt can be asserted to the ARM. ...
    (Linux-Kernel)
  • Re: tricky challenge for getting round level-driven interrupt problem: help!
    ... > Assuming you are using the core Linux IRQ code ... > So an implementation is much like a serial port fifo, ... that's connected to the ARM only has *one* interrupt. ...
    (Linux-Kernel)
  • [PATCH BK][ARM] Various ARM updates for 2.6.9
    ... This pull contains a set of ARM updates that have been pending in my ... specific to IOC/IOMD machines. ... IXP4xx and IXP2000 had params-phys when it should be params_phys ... The current timer interrupt implementation can cause time to skip ...
    (Linux-Kernel)