On Tue, 07 Jul 2026 17:05:48 -0300, Maíra Canal wrote:
> v3d_clean_caches() and v3d_flush_l2t() both write the single L2TCACTL
> register and poll its status bits. The mutex cache_clean_lock exists to
> serialize them, but v3d_clean_caches() only took the lock around its final
> FLM_CLEAN write.
>
> These functions run concurrently: v3d_flush_l2t() is issued from the
> BIN/RENDER/CSD invalidate path while v3d_clean_caches() runs from the
> CACHE_CLEAN queue, and each queue's scheduler uses its own ordered
> workqueue, so their run_job callbacks execute in parallel.
>
> [...]
Applied, thanks!
[1/1] drm/v3d: Widen cache_clean_lock over the whole L2TCACTL sequence
commit: 994ba6e5c87d6a3d471ea987fe8622168f092334
Best regards,
- Maíra
