Arm Community
Site
Search
User
Site
Search
User
Groups
Research Collaboration and Enablement
DesignStart
Education Hub
Innovation
Open Source Software and Platforms
Forums
AI and ML forum
Architectures and Processors forum
Arm Development Platforms forum
Arm Development Studio forum
Arm Virtual Hardware forum
Automotive forum
Compilers and Libraries forum
Graphics, Gaming, and VR forum
High Performance Computing (HPC) forum
Infrastructure Solutions forum
Internet of Things (IoT) forum
Keil forum
Morello Forum
Operating Systems forum
SoC Design and Simulation forum
中文社区论区
Blogs
AI and ML blog
Announcements
Architectures and Processors blog
Automotive blog
Graphics, Gaming, and VR blog
High Performance Computing (HPC) blog
Infrastructure Solutions blog
Innovation blog
Internet of Things (IoT) blog
Operating Systems blog
Research Articles
SoC Design and Simulation blog
Tools, Software and IDEs blog
中文社区博客
Support
Arm Support Services
Documentation
Downloads
Training
Arm Approved program
Arm Design Reviews
Community Help
More
Cancel
Support forums
Arm Development Studio forum
Question about prioritized ARM interrupt
Jump...
Cancel
Locked
Locked
Replies
4 replies
Subscribers
121 subscribers
Views
3015 views
Users
0 members are here
Options
Share
More actions
Cancel
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion
Question about prioritized ARM interrupt
Offline
Yang Fang
over 9 years ago
Note: This was originally posted on 3rd October 2011 at
http://forums.arm.com
One simple question but I did not find a clear answer. In the prioritized ARM interrupt, low and same priority interrupt will be masked out, so only higher priority interrupt can stop current interrupt. But will the lower interrupt flags also blocked? So another way to ask the question is whether lower interrupt will be ignored or there is a queue which will execute lower priority interrupt after current interrupt is serviced? Thank you.
Offline
Yang Fang
over 9 years ago
Note: This was originally posted on 5th October 2011 at
http://forums.arm.com
Thank you very much, folks.
Cancel
Up
0
Down
Cancel
Offline
Vaibhav Malik
over 9 years ago
Note: This was originally posted on 5th October 2011 at
http://forums.arm.com
Eric,
In case you are wondering around the software changing priority of the interrupt at run time before processor acknowledges the interrupt, then it is captured under spurious interrupt category (though it is unlikely from your question but just thought to share it)
Vaibhav
Cancel
Up
0
Down
Cancel
Offline
Vaibhav Malik
over 9 years ago
Note: This was originally posted on 5th October 2011 at
http://forums.arm.com
Eric,
There is another concept of interrupt nesting or preemption where the concept is signaling of higher priority pending interrupts to a target processor before an active interrupt completes. When this occurs, the initial active interrupt is said to have been preempted where the processor must save the context and later restore the same while resuming.
Vaibhav
Cancel
Up
0
Down
Cancel
Offline
Alban Rampon
over 9 years ago
Note: This was originally posted on 3rd October 2011 at
http://forums.arm.com
Hi Eric,
I'm afraid that would be depending on the type of interrupt/archi.
I would recommend the
ARM Generic Interrupt Controller - ARM IHI 0048B (PDF)
spec document.
Then, looking at page 16 and the
Interrupt States
and
Types
, you can first distinguish
edge
or
level senstive
interrupts. They would be handled differently...
I'm not sure about "blocked" word meaning and would advise you to look for "pending" keyword in that document.
Kindly,
Alban.
PS: Thanks Luke
Cancel
Up
0
Down
Cancel