diff options
| author | Marc Zyngier <[email protected]> | 2014-12-02 16:05:25 +0000 |
|---|---|---|
| committer | Olof Johansson <[email protected]> | 2014-12-04 23:24:48 -0800 |
| commit | e2fd06f6be690a1a9697c0c6338843a35cbd70a3 (patch) | |
| tree | c91fa0f3308390d904174db5c6fdd8c3cae5173c /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 7e8f403fecd38d018a2c1868b29e9c1ef7d6fc56 (diff) | |
ARM: imx: irq: fix buggy usage of irq_data irq field
mach-imx directly references to the irq field in
struct irq_data, and uses this to directly poke hardware register.
But irq is the *virtual* irq number, something that has nothing
to do with the actual HW irq (stored in the hwirq field). And once
we put the stacked domain code in action, the whole thing explodes,
as these two values are *very* different.
Just replacing all instances of irq with hwirq fixes the issue.
Tested-by: Fabio Estevam <[email protected]>
Acked-by: Shawn Guo <[email protected]>
Signed-off-by: Marc Zyngier <[email protected]>
Signed-off-by: Olof Johansson <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions