On Wed, 28 Jan 2026 13:43:46 +0100, Maxime Ripard wrote: > The drm_private_obj initialization was inconsistent with the rest of the > KMS objects. Indeed, it required to pass a preallocated state in > drm_private_obj_init(), while all the others objects would have a reset > callback that would be called later on to create the state. > > However, reset really is meant to reset the hardware and software state. > That it creates an initial state is a side-effect that has been used in > all objects but drm_private_obj. This is made more complex since some > drm_private_obj, the DisplayPort ones in particular, need to be > persistent across and suspend/resume cycle, and such a cycle would call > drm_mode_config_reset(). > > [...]
Applied to misc/kernel.git (drm-misc-next). Thanks! Maxime
