drm/panthor: Don't add write fences to the shared BOsdrm-misc-fixes-2024-10-02
commitf9e7ac6e2e9986c2ee63224992cb5c8276e46b2a
authorBoris Brezillon <boris.brezillon@collabora.com>
Thu, 5 Sep 2024 07:01:54 +0000 (5 09:01 +0200)
committerBoris Brezillon <boris.brezillon@collabora.com>
Tue, 1 Oct 2024 16:41:02 +0000 (1 18:41 +0200)
tree3b1459d2d20f74c81a21a7d624d33e2d460d2194
parent7a1f30afe97294281a2ba05977688385744f9844
drm/panthor: Don't add write fences to the shared BOs

The only user (the mesa gallium driver) is already assuming explicit
synchronization and doing the export/import dance on shared BOs. The
only reason we were registering ourselves as writers on external BOs
is because Xe, which was the reference back when we developed Panthor,
was doing so. Turns out Xe was wrong, and we really want bookkeep on
all registered fences, so userspace can explicitly upgrade those to
read/write when needed.

Fixes: 4bdca1150792 ("drm/panthor: Add the driver frontend block")
Cc: Matthew Brost <matthew.brost@intel.com>
Cc: Simona Vetter <simona.vetter@ffwll.ch>
Cc: <stable@vger.kernel.org>
Signed-off-by: Boris Brezillon <boris.brezillon@collabora.com>
Reviewed-by: Steven Price <steven.price@arm.com>
Reviewed-by: Liviu Dudau <liviu.dudau@arm.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20240905070155.3254011-1-boris.brezillon@collabora.com
drivers/gpu/drm/panthor/panthor_sched.c