On Mon, 08 Jun 2026 16:35:48 +0200, Maxime Ripard <[email protected]> wrote: > Commit 47b5ac7daa46 ("drm/atomic: Add new atomic_create_state callback > to drm_private_obj") introduced a new pattern for allocating drm object > states: atomic_create_state, a dedicated hook that allocates and > initializes a pristine state without any side effect. > > The bridge atomic_reset callback is already fallible and in practice > only allocates and initializes state without touching hardware. > However, the reset name does not make this contract clear: callers > and implementers cannot tell from the name alone whether the hardware > will be affected or when the hook is safe to call. > > [...]
Reviewed-by: Luca Ceresoli <[email protected]> -- Luca Ceresoli, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
