diff options
| author | Manivannan Sadhasivam <[email protected]> | 2023-07-26 20:59:31 +0530 |
|---|---|---|
| committer | Krzysztof Wilczyński <[email protected]> | 2023-08-29 11:59:35 +0000 |
| commit | 823de40c94d680ec8d57a660ac96a653acadb0a5 (patch) | |
| tree | facf1af0652063c527d699a8dd562251102955e4 /lib/test_fortify/write_overflow-strncpy-src.c | |
| parent | 06c2afb862f9da8dc5efa4b6076a0e48c3fbaaa5 (diff) | |
PCI: qcom-ep: Treat unknown IRQ events as an error
Sometimes, the Qcom PCIe EP controller can receive some interrupts
unknown to the driver, like safety interrupts in newer SoCs. In those
cases, if the driver doesn't clear the interrupts, it will end up in an
interrupt storm. However, the users will not know about it because the
log is treated as a debug message.
So let's treat the unknown event log as an error so that it at least
makes the user aware, thereby getting fixed eventually.
[kwilczynski: commit log]
Link: https://lore.kernel.org/linux-pci/[email protected]
Signed-off-by: Manivannan Sadhasivam <[email protected]>
Signed-off-by: Krzysztof Wilczyński <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strncpy-src.c')
0 files changed, 0 insertions, 0 deletions