irq: Use lowest priority not a hard-coded priority 2
In this file was found an assumption about how many priorities are being used. This is configurable with CONFIG_NUM_IRQ_PRIO_LEVELS, however, so it should be using that instead. This line of code changes: or r3,r3,(1<<(CONFIG_NUM_IRQ_PRIO_LEVELS-1)) so as to use the correct bit to OR. Change-Id: I8c6297e98b5163aa27460a68b203e8a27d1e2506 Signed-off-by: Chuck Jordan <cjordan@synopsys.com>
This commit is contained in:
parent
8e5c813a24
commit
e57b21c78c
1 changed files with 2 additions and 2 deletions
|
@ -205,9 +205,9 @@ _trap_reschedule:
|
|||
lr r3, [_ARC_V2_STATUS32]
|
||||
and r3,r3,(~_ARC_V2_STATUS32_AE)
|
||||
kflag r3
|
||||
/* pretend priority 1 int happened to use common handler */
|
||||
/* pretend lowest priority interrupt happened to use common handler */
|
||||
lr r3, [_ARC_V2_AUX_IRQ_ACT]
|
||||
or r3,r3,2
|
||||
or r3,r3,(1<<(CONFIG_NUM_IRQ_PRIO_LEVELS-1)) /* use lowest */
|
||||
sr r3, [_ARC_V2_AUX_IRQ_ACT]
|
||||
|
||||
/* Assumption: r2 has current thread */
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue