dri-devel Archive mirror
 help / color / mirror / Atom feed
From: Leandro Ribeiro <leandro.ribeiro@collabora.com>
To: dri-devel@lists.freedesktop.org
Cc: airlied@linux.ie, pekka.paalanen@collabora.co.uk, kernel@collabora.com
Subject: [PATCH v4 0/2] Document drm_mode_get_plane
Date: Wed,  9 Jun 2021 20:00:37 -0300	[thread overview]
Message-ID: <20210609230039.73307-1-leandro.ribeiro@collabora.com> (raw)

v2: possible_crtcs field is a bitmask, not a pointer. Suggested by
Ville Syrjälä <ville.syrjala@linux.intel.com>

v3: document how userspace should find out CRTC index. Also,
document that field 'gamma_size' represents the number of
entries in the lookup table. Suggested by Pekka Paalanen
<ppaalanen@gmail.com> and Daniel Vetter <daniel@ffwll.ch>

v4: document IN and OUT fields and make the description more
concise. Suggested by Pekka Paalanen <ppaalanen@gmail.com>

Leandro Ribeiro (2):
  drm/doc: document how userspace should find out CRTC index
  drm/doc: document drm_mode_get_plane

 Documentation/gpu/drm-uapi.rst    | 13 +++++++++++
 drivers/gpu/drm/drm_debugfs_crc.c |  8 +++----
 include/uapi/drm/drm.h            |  4 ++--
 include/uapi/drm/drm_mode.h       | 36 +++++++++++++++++++++++++++++++
 4 files changed, 55 insertions(+), 6 deletions(-)

--
2.31.1


             reply	other threads:[~2021-06-09 23:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-09 23:00 Leandro Ribeiro [this message]
2021-06-09 23:00 ` [PATCH v4 1/2] drm/doc: document how userspace should find out CRTC index Leandro Ribeiro
2021-06-10  8:27   ` Pekka Paalanen
2021-06-10 17:17     ` Daniel Vetter
2021-06-09 23:00 ` [PATCH v4 2/2] drm/doc: document drm_mode_get_plane Leandro Ribeiro
2021-06-09 23:05   ` Leandro Ribeiro
2021-06-10  8:36     ` Pekka Paalanen
2021-06-10 12:53   ` Ville Syrjälä

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=20210609230039.73307-1-leandro.ribeiro@collabora.com \
    --to=leandro.ribeiro@collabora.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kernel@collabora.com \
    --cc=pekka.paalanen@collabora.co.uk \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).