Skip to content

Commit d85dfb4

Browse files
mripardairlied
authored andcommitted
Documentation: drm: Remove drm_atomic_state rename entry
We just did that item so we can remove it. Reviewed-by: Luca Ceresoli <luca.ceresoli@bootlin.com> Acked-by: Jani Nikula <jani.nikula@intel.com> Signed-off-by: Maxime Ripard <mripard@kernel.org> Signed-off-by: Dave Airlie <airlied@redhat.com> Link: https://patch.msgid.link/20260427-drm-drm-atomic-update-v4-2-c0e713bfdf25@kernel.org
1 parent 5164f7e commit d85dfb4

1 file changed

Lines changed: 0 additions & 23 deletions

File tree

Documentation/gpu/todo.rst

Lines changed: 0 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -152,29 +152,6 @@ Contact: Simona Vetter, respective driver maintainers
152152

153153
Level: Advanced
154154

155-
Rename drm_atomic_commit
156-
-----------------------
157-
158-
The KMS framework uses two slightly different definitions for the ``state``
159-
concept. For a given object (plane, CRTC, encoder, etc., so
160-
``drm_$OBJECT_state``), the state is the entire state of that object. However,
161-
at the device level, ``drm_atomic_commit`` refers to a state update for a
162-
limited number of objects.
163-
164-
The state isn't the entire device state, but only the full state of some
165-
objects in that device. This is confusing to newcomers, and
166-
``drm_atomic_commit`` should be renamed to something clearer like
167-
``drm_atomic_commit``.
168-
169-
In addition to renaming the structure itself, it would also imply renaming some
170-
related functions (``drm_atomic_commit_alloc``, ``drm_atomic_commit_get``,
171-
``drm_atomic_commit_put``, ``drm_atomic_commit_init``,
172-
``__drm_atomic_commit_free``, etc.).
173-
174-
Contact: Maxime Ripard <mripard@kernel.org>
175-
176-
Level: Advanced
177-
178155
Fallout from atomic KMS
179156
-----------------------
180157

0 commit comments

Comments
 (0)