diff options
author | Connor Abbott <cwabbott0@gmail.com> | 2025-05-20 15:08:54 -0400 |
---|---|---|
committer | Will Deacon <will@kernel.org> | 2025-05-21 10:43:05 +0100 |
commit | 1650620774fa83135e39cc5778684dd516c11c3e (patch) | |
tree | 4f648c103c6bcdfdde2f4070ae96047938c248c6 /net/lapb/lapb_timer.c | |
parent | 3318f7b5cefbff96b1bb49584ac38d2c9997a830 (diff) |
iommu/arm-smmu-qcom: Enable threaded IRQ for Adreno SMMUv2/MMU500
The recommended flow for stall-on-fault in SMMUv2 is the following:
1. Resolve the fault.
2. Write to FSR to clear the fault bits.
3. Write RESUME to retry or fail the transaction.
MMU500 is designed with this sequence in mind. For example,
experimentally we have seen on MMU500 that writing RESUME does not clear
FSR.SS unless the original fault is cleared in FSR, so 2 must come
before 3. FSR.SS is allowed to signal a fault (and does on MMU500) so
that if we try to do 2 -> 1 -> 3 (while exiting from the fault handler
after 2) we can get duplicate faults without hacks to disable
interrupts.
However, resolving the fault typically requires lengthy operations that
can stall, like bringing in pages from disk. The only current user,
drm/msm, dumps GPU state before failing the transaction which indeed can
stall. Therefore, from now on we will require implementations that want
to use stall-on-fault to also enable threaded IRQs. Do that with the
Adreno MMU implementations.
Signed-off-by: Connor Abbott <cwabbott0@gmail.com>
Link: https://lore.kernel.org/r/20250520-msm-gpu-fault-fixes-next-v8-1-fce6ee218787@gmail.com
Signed-off-by: Will Deacon <will@kernel.org>
Diffstat (limited to 'net/lapb/lapb_timer.c')
0 files changed, 0 insertions, 0 deletions