Lines Matching refs:L2
169 ; if L2 IRQ interrupted a L1 ISR, disable preemption
171 ; This is to avoid a potential L1-L2-L1 scenario
173 ; -L2 interrupts L1 (before L1 ISR could run)
176 ; Returns from L2 context fine
177 ; But both L1 and L2 re-enabled, so another L1 can be taken
182 ; L2 interrupting L1 implies both L2 and L1 active
187 bbit0 r9, STATUS_A1_BIT, 1f ; L1 not active when L2 IRQ, so normal
226 ; out of the L2 interrupt context (drop to pure kernel mode) and jump
349 ; use the same priorty as rtie: EXCPN, L2 IRQ, L1 IRQ, None
364 ; However the context returning might not have taken L2 intr itself
365 ; e.g. Task'A' user-code -> L2 intr -> schedule -> 'B' user-code ret
366 ; Special considerations needed for the context which took L2 intr
368 ld r9, [sp, PT_event] ; Ensure this is L2 intr context
372 ; if L2 IRQ interrupted an L1 ISR, we'd disabled preemption earlier
375 ; things to what they were, before returning from L2 context
379 bbit0 r9, STATUS_A1_BIT, 149f ; L1 not active when L2 IRQ, so normal