diff options
| author | Carl Huang <[email protected]> | 2021-11-19 15:36:26 +0200 |
|---|---|---|
| committer | Kalle Valo <[email protected]> | 2021-11-22 13:11:00 +0200 |
| commit | 87b4072d7ef818e368b0f4162a1af2fb4727f51c (patch) | |
| tree | 8d98b4a5ecbfc644ae5d0dffb91ee100dc30db0b /tools/perf/scripts/python/failed-syscalls-by-pid.py | |
| parent | 728e26c3ac89427de181c1e8400d27d7b6c3a8a5 (diff) | |
ath11k: get msi_data again after request_irq is called
The reservation mode of interrupts in kernel assigns a dummy vector
when the interrupt is allocated and assigns a real vector when the
request_irq is called. The reservation mode helps to ease vector
pressure when devices with a large amount of queues/interrupts
are initialized, but only a minimal subset of those queues/interrupts
is actually used.
So on reservation mode, the msi_data may change after request_irq
is called, so ath11k reads msi_data again after request_irq is called,
and then the correct msi_data is programmed into QCA6390 hardware
components. Without this change, spurious interrupt occurs in case of
one MSI vector. When VT-d in BIOS is enabled and ath11k can get 32 MSI
vectors, ath11k always get the same msi_data before and after request_irq,
that's why this change is only required when one MSI vector is to be
supported.
Tested-on: QCA6390 hw2.0 PCI WLAN.HST.1.0.1-01740-QCAHSTSWPLZ_V2_TO_X86-1
Signed-off-by: Carl Huang <[email protected]>
Signed-off-by: Kalle Valo <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'tools/perf/scripts/python/failed-syscalls-by-pid.py')
0 files changed, 0 insertions, 0 deletions