From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from perceval.ideasonboard.com (perceval.ideasonboard.com [213.167.242.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B4FA61DA62E; Mon, 4 May 2026 16:34:44 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=213.167.242.64 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777912487; cv=none; b=n4uxiRlwgwFhHGn5SXIoiZyMxw+Pyk4tpG+7ohPfQQz5f7UiwpuPPe0O7F/4aOa5QA3z7v8iVs9DyyXogm0AvmnhVdhcSW3cDru1K+QH5nfErE5GbWNUtevs5d8gT6QYNcJ7p2LfIw/22XuGXQHYNuX7CXvc3aaqfjFIuvruVGM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777912487; c=relaxed/simple; bh=2OSAeT8an5e3Y+nfCRfDAXE6cwKmFiIVVKAcvn/IUNE=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=lyWmMlPQgijf3w3nMY4JXVFAQkA9JvXbCPKsoDgGF8f4Vzfvf1cUL2pTp8iKe1ZE4LSGIxdrXKItpIRlR9x4QhxqypEOn6QsRuC7EU5APLnIl/IKiFkSQR3VlaSBdLkdwDwFYIuR3OGqsqTAPCPkvj+I0ZY8UZoVJcg1S/M+AlQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=ideasonboard.com; spf=pass smtp.mailfrom=ideasonboard.com; dkim=pass (1024-bit key) header.d=ideasonboard.com header.i=@ideasonboard.com header.b=vxISDUCu; arc=none smtp.client-ip=213.167.242.64 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=ideasonboard.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=ideasonboard.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=ideasonboard.com header.i=@ideasonboard.com header.b="vxISDUCu" Received: from killaraus.ideasonboard.com (2001-14ba-703d-e500--2a1.rev.dnainternet.fi [IPv6:2001:14ba:703d:e500::2a1]) by perceval.ideasonboard.com (Postfix) with ESMTPSA id 3A5EF9C; Mon, 4 May 2026 18:34:41 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ideasonboard.com; s=mail; t=1777912481; bh=2OSAeT8an5e3Y+nfCRfDAXE6cwKmFiIVVKAcvn/IUNE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=vxISDUCuo6b67rdu9OyWQc4v82FFMWzd49PyIU+P5FA58n/pOr24USVXMSVJzhYd2 9LLY/MSJUZJRAKvQ69brP3BXwQwmcOYkm+rI9oCeir5Z2a+F7hIimQPN7mSOZBxz6H TnMUIUFuDNrQ9kdWmO/7opamqlJOvglSdCiRFVTA= Date: Mon, 4 May 2026 19:34:41 +0300 From: Laurent Pinchart To: Maxime Ripard Cc: Maarten Lankhorst , Thomas Zimmermann , David Airlie , Simona Vetter , Jonathan Corbet , Shuah Khan , Dmitry Baryshkov , Jyri Sarha , Tomi Valkeinen , Andrzej Hajda , Neil Armstrong , Robert Foss , Jonas Karlman , Jernej Skrabec , Simon Ser , Harry Wentland , Melissa Wen , Sebastian Wick , Alex Hung , Jani Nikula , Rodrigo Vivi , Joonas Lahtinen , Tvrtko Ursulin , Chen-Yu Tsai , Samuel Holland , Dave Stevenson , =?utf-8?B?TWHDrXJh?= Canal , Raspberry Pi Kernel Maintenance , dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, Daniel Stone , intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org, linux-arm-kernel@lists.infradead.org, linux-sunxi@lists.linux.dev Subject: Re: [PATCH v3 04/20] drm/atomic: Expand atomic_create_state expectations for drm_private_obj Message-ID: <20260504163441.GI1344263@killaraus.ideasonboard.com> References: <20260424-drm-mode-config-init-v3-0-8b68d9db0d8b@kernel.org> <20260424-drm-mode-config-init-v3-4-8b68d9db0d8b@kernel.org> Precedence: bulk X-Mailing-List: linux-doc@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20260424-drm-mode-config-init-v3-4-8b68d9db0d8b@kernel.org> Hi Maxime, Thank you for the patch. On Fri, Apr 24, 2026 at 12:18:44PM +0200, Maxime Ripard wrote: > The atomic_create_state callback documentation for planes, CRTCs, and > connectors explicitly states the expected behaviour: the returned > state must not be assigned to the object's state pointer, and hardware > must not be touched. > > The drm_private_state_funcs.atomic_create_state documentation is > missing this clarification. Add it for consistency. > > Signed-off-by: Maxime Ripard Reviewed-by: Laurent Pinchart > --- > include/drm/drm_atomic.h | 5 ++++- > 1 file changed, 4 insertions(+), 1 deletion(-) > > diff --git a/include/drm/drm_atomic.h b/include/drm/drm_atomic.h > index f03cd199aee7..f7f9c6c85f3a 100644 > --- a/include/drm/drm_atomic.h > +++ b/include/drm/drm_atomic.h > @@ -263,11 +263,14 @@ struct drm_private_state; > struct drm_private_state_funcs { > /** > * @atomic_create_state: > * > * Allocates a pristine, initialized, state for the private > - * object and returns it. > + * object and returns it. This callback must have no side > + * effects: in particular, the returned state must not be > + * assigned to the object's state pointer and it must not affect > + * the hardware state. > * > * RETURNS: > * > * A new, pristine, private state instance or an error pointer > * on failure. -- Regards, Laurent Pinchart