From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 2FC34388E6C for ; Thu, 26 Mar 2026 10:09:53 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774519794; cv=none; b=T1XkFxtPj3e5v6W9acKk0tyg6JTsFMMf9O7dphXgPYl77UAGhnsTGuJH1QAPID3/f4rD/4DkaDkwJRUBj8KZoicvYx1UDYMyU5wHOEJyyIgTfA/eEA1jNHx3SkOQE0o7Ir2RKqBkCXdfqCxX4AtV/Sp8OLosY6ufAjs9uM0zo4I= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774519794; c=relaxed/simple; bh=ehwJ0z/KHrCfGQljJUa7Xkhys1ou4TDKybZZvsmc+Mk=; h=From:Date:Subject:MIME-Version:Content-Type:Message-Id:References: In-Reply-To:To:Cc; b=C96bz7N1boYUYEHdOKYogNx703DhMTuL/JSCCcChM5sY5V9UeKk+HqxjPTbg9So08sHsCgOSJXgsKoZiFTocqB64ILEGJ42kTJw+HWBFYB1701ZIbMF2Y1TH4xuk3ih3AExfSHDgk6emVIdrNRtkkqtzUgep2h/YC6z6ylpDqlI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=Hv9rPz9e; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="Hv9rPz9e" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 7D26AC116C6; Thu, 26 Mar 2026 10:09:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1774519793; bh=ehwJ0z/KHrCfGQljJUa7Xkhys1ou4TDKybZZvsmc+Mk=; h=From:Date:Subject:References:In-Reply-To:To:Cc:From; b=Hv9rPz9e8txkHnqwpeTyHCyTrBSltAqpTSvpUUPeZSncnZwh/gRpH/Yj/Te4l7hqm rB7cTRCzGlSgcMJsmy5xCsPqfKT3/jL6cPp7Xfqo3uNPy/e13c3Wc2cUSf+rwJLjr8 PMi35ovkyaGdlH0JmoVUQ6XbioNC2C8Ue5+o2yrJ8DusJw3W3W6IFKtd1XxKcnhrx2 /n7A7RcdnbPp9Qz4a6ro6BY9CloAW6rYG6ulo1LgIBRFnG5pYkTW+IHt4FgtrKi/yz 4eivB1Jq2gwpSMwA4mWaZgTfre/nSf1JX2365rzCdW91x0THtXdxb3hjzNsYZDUm9N PnjjPoPExu2uQ== From: Maxime Ripard Date: Thu, 26 Mar 2026 11:09:39 +0100 Subject: [PATCH 2/2] Documentation: drm: Remove drm_atomic_state rename entry 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-Transfer-Encoding: 7bit Message-Id: <20260326-drm-drm-atomic-update-v1-2-2f7af5f4ad02@kernel.org> References: <20260326-drm-drm-atomic-update-v1-0-2f7af5f4ad02@kernel.org> In-Reply-To: <20260326-drm-drm-atomic-update-v1-0-2f7af5f4ad02@kernel.org> To: David Airlie , Simona Vetter , Maarten Lankhorst , Thomas Zimmermann , Jonathan Corbet Cc: dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org, Maxime Ripard X-Mailer: b4 0.14.2 X-Developer-Signature: v=1; a=openpgp-sha256; l=1726; i=mripard@kernel.org; h=from:subject:message-id; bh=ehwJ0z/KHrCfGQljJUa7Xkhys1ou4TDKybZZvsmc+Mk=; b=owGbwMvMwCmsHn9OcpHtvjLG02pJDJlHWZ+7GDmeuhD130FvRw9Ta6NE/Zb1ol9z/E90x053X /JftKSmYyoLgzAng6yYIssTmbDTy9sXVznYr/wBM4eVCWQIAxenAExEKJaxzjb8PZscz6f46f1n 3EJc97AsqipUn9HP+NTgxhJfIVux01YFzldm6d4IcFtytXrzt6kVjPWFTwrfJF6tEfPsTpxnfj/ 94vRPG9g31k8/4xYmscLW0s1kNve7UpfHsm5bG32S317N8wcA X-Developer-Key: i=mripard@kernel.org; a=openpgp; fpr=BE5675C37E818C8B5764241C254BCFC56BF6CE8D We just did that item so we can remove it. Signed-off-by: Maxime Ripard --- Documentation/gpu/todo.rst | 23 ----------------------- 1 file changed, 23 deletions(-) diff --git a/Documentation/gpu/todo.rst b/Documentation/gpu/todo.rst index 520da44a04a625e6ded3c6ef672c221523a993f8..407ceb14524e6971a13812fed4496d0feb91108a 100644 --- a/Documentation/gpu/todo.rst +++ b/Documentation/gpu/todo.rst @@ -118,33 +118,10 @@ still look at that flag. Contact: Simona Vetter, respective driver maintainers Level: Advanced -Rename drm_atomic_state ------------------------ - -The KMS framework uses two slightly different definitions for the ``state`` -concept. For a given object (plane, CRTC, encoder, etc., so -``drm_$OBJECT_state``), the state is the entire state of that object. However, -at the device level, ``drm_atomic_state`` refers to a state update for a -limited number of objects. - -The state isn't the entire device state, but only the full state of some -objects in that device. This is confusing to newcomers, and -``drm_atomic_state`` should be renamed to something clearer like -``drm_atomic_commit``. - -In addition to renaming the structure itself, it would also imply renaming some -related functions (``drm_atomic_state_alloc``, ``drm_atomic_state_get``, -``drm_atomic_state_put``, ``drm_atomic_state_init``, -``__drm_atomic_state_free``, etc.). - -Contact: Maxime Ripard - -Level: Advanced - Fallout from atomic KMS ----------------------- ``drm_atomic_helper.c`` provides a batch of functions which implement legacy IOCTLs on top of the new atomic driver interface. Which is really nice for -- 2.53.0