Both omapdrm and tidss give quite similar lockdep warnings ever since the "Annotate dma-fence critical section in commit path" patches. I've tried to look at this, but I haven't gotten far with understanding all this, and I feel that I'd need to really dive deep into the details to understand all the locking dependencies relevant here. With some git-log digging, I noticed this: https://patchwork.freedesktop.org/patch/462170/ So maybe the "fix" is just to revert the patches. If yes, great, we can apply the patches here. If not, not so great, and I'll just have to start the diving =). Signed-off-by: Tomi Valkeinen <tomi.valkeinen@xxxxxxxxxxxxxxxx> --- Tomi Valkeinen (2): Revert "drm/tidss: Annotate dma-fence critical section in commit path" Revert "drm/omapdrm: Annotate dma-fence critical section in commit path" drivers/gpu/drm/omapdrm/omap_drv.c | 9 ++++----- drivers/gpu/drm/tidss/tidss_kms.c | 4 ---- 2 files changed, 4 insertions(+), 9 deletions(-) --- base-commit: 9fc75c40faa29df14ba16066be6bdfaea9f39ce4 change-id: 20230920-dma-fence-annotation-revert-166d0efab368 Best regards, -- Tomi Valkeinen <tomi.valkeinen@xxxxxxxxxxxxxxxx>
