TDA2x : MaskingOption_ALL vs hwi_disable()

Abhishek Singh Sisodia

Other Parts Discussed in Thread: SYSBIOS

Hello

I am working on TDA2x with sysbios 6.

I have faced an interesting problem where an ISR running (DSP) is preempted by another ISR and both these ISR's are invoked by the hardware interrupts. One of the hardware interrupt is caused by mailbox module between DSP and IPU and other by the DSP and EVE.

Unfortunately, both these ISR's share a critical section and thus the data corruption happens.

When i try using a HWI_disable() and HWI_enable() at the start of ISR routines then everything works fine.Also when i use MaskingOption_ALL in BIOS configuration of HWI things work fine but not with the default option MaskingOption_SELF.

My question is :

Q1. Is MaskingOption_ALL is fundamentally same as hwi_disable()?

Q2. If not then what is a better option to use and Why?

Q3. In case my critical section in ISR is small, then can i use hwi_disable() instead of MaskingOption_ALL (assuming later is better fundamentally).

Regards

Abhishek

over 8 years ago

0 Eric Hackett over 8 years ago

TI__Guru 74252 points

Abhishek,

I have moved this thread to the TDAx forum for more appropriate support.

Regards,

0 Mariya Petkova over 8 years ago in reply to Eric Hackett

TI__Expert 4885 points

Hi, Abhishek,

I forwarded your question to experts.

Mariya

0 Yogesh Marathe over 8 years ago in reply to Mariya Petkova

TI__Expert 7765 points

Abhishek,

The DSP in TDA2x has Event Combiner. You need to use Event Combiner to register interrupts for DSP. By default it doesn't allow nested interrupts.

Module under sysbios
ti/sysbios/family/c64p/EventCombiner

API
EventCombiner_dispatchPlug()
EventCombiner_enableEvent()

More information on Event Combiner block
"Interrupt Controller" section in www.ti.com/lit/pdf/sprugw0

If you have vision sdk you can look for EventCombiner_dispatchPlug and you will see manu examples.

Processors

Processors forum

TDA2x : MaskingOption_ALL vs hwi_disable()