From: Daniel Vetter <daniel@ffwll.ch>
To: Maxime Ripard <mripard@kernel.org>
Cc: Pekka Paalanen <pekka.paalanen@collabora.com>,
David Airlie <airlied@linux.ie>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
dri-devel@lists.freedesktop.org,
Thomas Zimmermann <tzimmermann@suse.de>
Subject: Re: [PATCH 3/5] drm/atomic: Rework the object doc a bit
Date: Thu, 7 Dec 2023 22:41:51 +0100 [thread overview]
Message-ID: <ZXI8HyiCxN8yvSyu@phenom.ffwll.local> (raw)
In-Reply-To: <20231204121707.3647961-3-mripard@kernel.org>
On Mon, Dec 04, 2023 at 01:17:05PM +0100, Maxime Ripard wrote:
> The doc for the planes, crtcs, connectors and private_objs fields
> mention that they are pointers to an array of structures with
> per-$OBJECT data.
>
> While these fields are indeed pointers to an array, each item of that
> array contain a pointer to the object structure affected by the update,
> and its old and new state. There's no per-object data there.
>
> Let's rephrase those fields a bit to better match the current situation.
Yeah that wasn't updated as part of 5d943aa6c0d4 ("drm: Consolidate crtc
arrays in drm_atomic_state") and b8b5342b699b ("drm: Consolidate plane
arrays in drm_atomic_state"). With that added to the commit message:
Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>
> Signed-off-by: Maxime Ripard <mripard@kernel.org>
> ---
> include/drm/drm_atomic.h | 20 ++++++++++++++++----
> 1 file changed, 16 insertions(+), 4 deletions(-)
>
> diff --git a/include/drm/drm_atomic.h b/include/drm/drm_atomic.h
> index 13cecdc1257d..914574b58ae7 100644
> --- a/include/drm/drm_atomic.h
> +++ b/include/drm/drm_atomic.h
> @@ -403,12 +403,18 @@ struct drm_atomic_state {
> bool duplicated : 1;
>
> /**
> - * @planes: pointer to array of structures with per-plane data
> + * @planes:
> + *
> + * Pointer to array of @drm_plane and @drm_plane_state part of this
> + * update.
> */
> struct __drm_planes_state *planes;
>
> /**
> - * @crtcs: pointer to array of CRTC pointers
> + * @crtcs:
> + *
> + * Pointer to array of @drm_crtc and @drm_crtc_state part of this
> + * update.
> */
> struct __drm_crtcs_state *crtcs;
>
> @@ -418,7 +424,10 @@ struct drm_atomic_state {
> int num_connector;
>
> /**
> - * @connectors: pointer to array of structures with per-connector data
> + * @connectors:
> + *
> + * Pointer to array of @drm_connector and @drm_connector_state part of
> + * this update.
> */
> struct __drm_connnectors_state *connectors;
>
> @@ -428,7 +437,10 @@ struct drm_atomic_state {
> int num_private_objs;
>
> /**
> - * @private_objs: pointer to array of private object pointers
> + * @private_objs:
> + *
> + * Pointer to array of @drm_private_obj and @drm_private_obj_state part
> + * of this update.
> */
> struct __drm_private_objs_state *private_objs;
>
> --
> 2.43.0
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2023-12-07 21:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 12:17 [PATCH 1/5] drm/atomic: Move the drm_atomic_state field doc inline Maxime Ripard
2023-12-04 12:17 ` [PATCH 2/5] drm/atomic: Remove inexistent reference Maxime Ripard
2023-12-05 13:32 ` [2/5] " Sui Jingfeng
2023-12-07 21:40 ` [PATCH 2/5] " Daniel Vetter
2023-12-04 12:17 ` [PATCH 3/5] drm/atomic: Rework the object doc a bit Maxime Ripard
2023-12-05 13:52 ` [3/5] " Sui Jingfeng
2023-12-07 21:41 ` Daniel Vetter [this message]
2023-12-04 12:17 ` [PATCH 4/5] drm/atomic: Make the drm_atomic_state documentation less ambiguous Maxime Ripard
2023-12-05 8:51 ` Pekka Paalanen
2023-12-05 9:15 ` Pekka Paalanen
2023-12-07 13:50 ` Maxime Ripard
2023-12-07 14:27 ` Maxime Ripard
2023-12-08 8:08 ` Pekka Paalanen
2023-12-08 12:25 ` Maxime Ripard
2023-12-08 13:59 ` Pekka Paalanen
2023-12-08 15:20 ` Maxime Ripard
2023-12-11 9:22 ` Pekka Paalanen
2023-12-07 21:48 ` Daniel Vetter
2023-12-04 12:17 ` [PATCH 5/5] drm/todo: Add entry to rename drm_atomic_state Maxime Ripard
2023-12-07 21:51 ` Daniel Vetter
2023-12-05 13:42 ` [1/5] drm/atomic: Move the drm_atomic_state field doc inline Sui Jingfeng
2023-12-07 21:34 ` [PATCH 1/5] " Daniel Vetter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZXI8HyiCxN8yvSyu@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@linux.ie \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=mripard@kernel.org \
--cc=pekka.paalanen@collabora.com \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox