diff options
| author | Jinjie Ruan <[email protected]> | 2024-09-14 16:25:32 +0800 |
|---|---|---|
| committer | Nishanth Menon <[email protected]> | 2024-10-25 08:58:18 -0500 |
| commit | 10b8a0cc84d28decb75bfc91f4395e176228a4ff (patch) | |
| tree | 598ba9853313b73883d7f6d788d8d700aa09c390 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 9852d85ec9d492ebef56dc5f229416c925758edc (diff) | |
soc: ti: knav_qmss_queue: Use IRQF_NO_AUTOEN flag in request_irq()
As commit cbe16f35bee6 ("genirq: Add IRQF_NO_AUTOEN for request_irq/nmi()")
said, reqeust_irq() and then disable_irq() is unsafe. In the small time gap
between request_irq() and disable_irq(), interrupts can still come.
IRQF_NO_AUTOEN flag can be used by drivers to request_irq(). It prevents
the automatic enabling of the requested interrupt in the same
safe way. With that the usage can be simplified and corrected.
Compile-tested only.
Signed-off-by: Jinjie Ruan <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Nishanth Menon <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions