On Mon, Nov 16, 2026 at 11:30:27AM +0100, Maxime Ripard wrote:
> drm_mode_config_reset() has a dual role: it creates the initial KMS
> state at probe time, and resets hardware and software state during
> suspend/resume cycles.
> 
> Since the two roles need different behaviors (notably for objects like
> drm_private_obj that must persist across suspend/resume),
> drm_mode_config_create_initial_state() was introduced to handle only
> the initial state creation at probe time.
> 
> Switch to drm_mode_config_create_initial_state().
> 
> Signed-off-by: Maxime Ripard <[email protected]>

Acked-by: Hamza Mahfooz <[email protected]>

> ---
> Cc: Dexuan Cui <[email protected]>
> Cc: Long Li <[email protected]>
> Cc: Saurabh Sengar <[email protected]>
> Cc: [email protected]
> ---
>  drivers/gpu/drm/hyperv/hyperv_drm_modeset.c | 4 +---
>  1 file changed, 1 insertion(+), 3 deletions(-)
> 
> diff --git a/drivers/gpu/drm/hyperv/hyperv_drm_modeset.c 
> b/drivers/gpu/drm/hyperv/hyperv_drm_modeset.c
> index 759952f4ff19..73938303e663 100644
> --- a/drivers/gpu/drm/hyperv/hyperv_drm_modeset.c
> +++ b/drivers/gpu/drm/hyperv/hyperv_drm_modeset.c
> @@ -500,9 +500,7 @@ int hv_drm_mode_config_init(struct hv_drm_device *hv)
>  
>       ret = drm_vblank_init(dev, 1);
>       if (ret)
>               return ret;
>  
> -     drm_mode_config_reset(dev);
> -
> -     return 0;
> +     return drm_mode_config_create_initial_state(dev);
>  }
> 
> -- 
> 2.56.1
> 

Reply via email to