[PATCH] drm: allow IN_FENCE_FD and FB_DAMAGE_CLIPS to be changed with async commits

[André Almeida]

Hi Xaver,

Em 11/01/2024 13:56, Xaver Hugl escreveu:
> 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.hugl at gmail.com>

Reviewed-by: André Almeida <andrealmeid at igalia.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);