diff options
| author | Afzal Mohammed <[email protected]> | 2014-04-25 17:38:11 -0500 |
|---|---|---|
| committer | Nishanth Menon <[email protected]> | 2014-05-05 14:34:03 -0500 |
| commit | 2100b595b756db29a0b71de49c3bf73ae76c679b (patch) | |
| tree | b32849d21bbb6f5f8d4997457b8a1109387d0b04 /tools/perf/scripts/python/bin/stackcollapse-report | |
| parent | e4be3f3a040432398225d3634d44fc21f4807b7a (diff) | |
bus: omap_l3_noc: ignore masked out unclearable targets
Errors that cannot be cleared (determined by reading REGERR register)
are currently handled by masking it. Documentation states that REGERR
"Checks which application/debug error sources are active" - it does not
indicate that this is "interrupt status" - masked out status represented
eventually in the irq line to MPU.
For example:
Lets say module 0 bit 8(0x100) was unclearable, we do the mask it from
generating further errors. However in the following cases:
a) bit 9 of Module 0
OR
b) any bit of Module 1+
occur, the interrupt handler wrongly assumes that the raw interrupt
status of module 0 bit 8 is the root cause of the interrupt, and
returns. This causes unhandled interrupt and resultant infinite
interrupts.
Fix this scenario by storing the events we masked out and masking raw
status with masked ones before identifying and handling the error.
Reported-by: Vaibhav Hiremath <[email protected]>
Signed-off-by: Afzal Mohammed <[email protected]>
Tested-by: Vaibhav Hiremath <[email protected]>
Signed-off-by: Sekhar Nori <[email protected]>
Signed-off-by: Nishanth Menon <[email protected]>
Tested-by: Sekhar Nori <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions