Like with FB_ID, the driver never has to do bandwidth validation to use
these properties, so there's no reason not to allow them.

Signed-off-by: Xaver Hugl <xaver.h...@gmail.com>
---
 drivers/gpu/drm/drm_atomic_uapi.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/drm_atomic_uapi.c 
b/drivers/gpu/drm/drm_atomic_uapi.c
index aee4a65d4959..06d476f5a746 100644
--- a/drivers/gpu/drm/drm_atomic_uapi.c
+++ b/drivers/gpu/drm/drm_atomic_uapi.c
@@ -1108,7 +1108,9 @@ int drm_atomic_set_property(struct drm_atomic_state 
*state,
                        break;
                }
 
-               if (async_flip && prop != config->prop_fb_id) {
+               if (async_flip && prop != config->prop_fb_id &&
+                       prop != config->prop_in_fence_fd &&
+                       prop != config->prop_fb_damage_clips) {
                        ret = drm_atomic_plane_get_property(plane, plane_state,
                                                            prop, &old_val);
                        ret = drm_atomic_check_prop_changes(ret, old_val, 
prop_value, prop);
-- 
2.43.0

Reply via email to