summaryrefslogtreecommitdiff
path: root/include/uapi
diff options
context:
space:
mode:
authorPraveen Talari <praveen.talari@oss.qualcomm.com>2026-07-15 09:55:15 +0530
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2026-07-17 13:02:19 +0200
commit5d51a3958ae03e2eda5db9e32b4b224d17faf7d2 (patch)
tree987c29b09b2c6af47c20ddec002cb6d4fc312c07 /include/uapi
parentdbe2afb952bdb782450d8f678adeb502791e7edd (diff)
downloadlinux-5d51a3958ae03e2eda5db9e32b4b224d17faf7d2.tar.gz
linux-5d51a3958ae03e2eda5db9e32b4b224d17faf7d2.zip
serial: qcom_geni: Add panic notifier to stop UART on panic
When a VM crashes with an active UART DMA transfer in progress, the SMMU raises context faults as the DMA engine continues to access IOVAs that are invalidated when the VM's memory context is torn down. These faults can affect other VMs sharing the same SMMU instance and obscure the root cause of the crash. Additionally, a stuck TX transfer on the panic console UART can cause the panic handler to stall, dropping the panic output. Register a panic notifier to stop TX and RX. The notifier does not take the port lock, since panic can be entered with the lock already held by the interrupted context, and there is no safe way to detect that here; instead, the device's runtime PM status is checked first so that TX/RX are only stopped while the hardware is still clocked and accessible, and the register accesses are skipped entirely once the device is runtime suspended. Signed-off-by: Praveen Talari <praveen.talari@oss.qualcomm.com> Link: https://patch.msgid.link/20260715-add_shutdown_and_panic_notifier_serial-v1-2-23e3787c7109@oss.qualcomm.com Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'include/uapi')
0 files changed, 0 insertions, 0 deletions