From: Louis Chauvet <louis.chauvet@bootlin.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>,
Daniel Vetter <daniel@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
seanpaul@google.com, marcheu@google.com,
nicolejadeyee@google.com, pekka.paalanen@collabora.com,
thomas.petazzoni@bootlin.com,
Louis Chauvet <louis.chauvet@bootlin.com>
Subject: [PATCH 0/3] drm: Multiple documentation update
Date: Tue, 09 Apr 2024 12:04:04 +0200 [thread overview]
Message-ID: <20240409-google-drm-doc-v1-0-033d55cc8250@bootlin.com> (raw)
PATCH 1 and PATCH 2 focus on the rotation property. The rotation property
can be challenging to understand, especially when it is combined with
reflections. These patches aim to provide clearer explanations and
examples to aid in comprehension.
Patch 3 relates to the fourcc property. It includes additional details
about block and char_per_block to provide a more comprehensive
understanding of this feature.
Regarding PATCH 1, I would appreciate some feedback on the expected
behavior. During a recent VKMS refactor, I used drm_rect_rotate as a
reference for the rotation. However, during my testing phase, I noticed
that the original VKMS implementation interpreted the rotation
differently. Therefore, I kindly request that someone validate or
invalidate my interpretation before proceeding with the merge.
Signed-off-by: Louis Chauvet <louis.chauvet@bootlin.com>
---
Louis Chauvet (3):
drm: drm_blend.c: Add precision in drm_rotation_simplify kernel doc
drm: drm_blend.c: Improve drm_plane_create_rotation_property kernel doc
drm/fourcc: Add documentation around drm_format_info
drivers/gpu/drm/drm_blend.c | 57 ++++++++++++++++++++++++++++++++++-----------
include/drm/drm_fourcc.h | 45 +++++++++++++++++++++++++++++------
2 files changed, 81 insertions(+), 21 deletions(-)
---
base-commit: e495e523b888a6155f82c767d34c8d712a41ee54
change-id: 20240327-google-drm-doc-cd275291792f
Best regards,
--
Louis Chauvet <louis.chauvet@bootlin.com>
next reply other threads:[~2024-04-09 10:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 10:04 Louis Chauvet [this message]
2024-04-09 10:04 ` [PATCH 1/3] drm: drm_blend.c: Add precision in drm_rotation_simplify kernel doc Louis Chauvet
2024-04-15 14:30 ` Bagas Sanjaya
2024-04-09 10:04 ` [PATCH 2/3] drm: drm_blend.c: Improve drm_plane_create_rotation_property " Louis Chauvet
2024-04-15 11:36 ` Pekka Paalanen
2024-04-16 22:30 ` Louis Chauvet
2024-04-17 11:34 ` Pekka Paalanen
2024-04-15 14:28 ` Bagas Sanjaya
2024-04-16 22:30 ` Louis Chauvet
2024-04-09 10:04 ` [PATCH 3/3] drm/fourcc: Add documentation around drm_format_info Louis Chauvet
2024-04-15 12:00 ` Pekka Paalanen
2024-04-16 22:30 ` Louis Chauvet
2024-04-17 11:44 ` Pekka Paalanen
2024-04-15 14:16 ` Bagas Sanjaya
2024-04-09 10:18 ` [PATCH 0/3] drm: Multiple documentation update Jani Nikula
2024-04-09 12:38 ` Louis Chauvet
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=20240409-google-drm-doc-v1-0-033d55cc8250@bootlin.com \
--to=louis.chauvet@bootlin.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marcheu@google.com \
--cc=mripard@kernel.org \
--cc=nicolejadeyee@google.com \
--cc=pekka.paalanen@collabora.com \
--cc=seanpaul@google.com \
--cc=thomas.petazzoni@bootlin.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
Powered by JetHome