On Fri, Oct 30, 2026 at 04:13:30PM +0100, Maxime Ripard wrote: > This is a follow-up to the plane and CRTC reset removal series, and > part of a larger effort to remove the reset hook from all KMS objects. > > The connector reset hook is overloaded: it is called both at probe > time to create the initial software state and during suspend/resume to > reset hardware and software state. These two roles have different > requirements, and the reset hook is not fallible, making error > handling difficult for the initial state allocation path. > > While reset has the semantics to reset both the software and hardware > state, the vast majority of implementations and all the helpers only > reset the software state, making them equivalent to > atomic_create_state in practice. The atomic_create_state hook makes > this explicit: it only allocates and initializes a pristine state > without any side effect, and returns the state pointer or an ERR_PTR > on failure. > > This series converts all connector drivers tree-wide from the reset hook > to atomic_create_state, then removes the reset hook from struct > drm_connector_funcs entirely. The conversions were done using a > combination of Coccinelle semantic patches, mechanical one-line > replacements and manual adjustments. > > Signed-off-by: Maxime Ripard Applied to drm-misc-next Maxime