From: Daniel Vetter <daniel@ffwll.ch>
To: Simon Ser <contact@emersion.fr>
Cc: dri-devel@lists.freedesktop.org, Daniel Stone <daniels@collabora.com>
Subject: Re: [PATCH 3/3] drm: document minimum kernel version for DRM_CLIENT_CAP_*
Date: Wed, 19 May 2021 12:18:08 +0200 [thread overview]
Message-ID: <YKTl4Ei5rB5WH87u@phenom.ffwll.local> (raw)
In-Reply-To: <8tBryxsjXiKtYZP4whnTumr2AsWx9X1xPmwFAdp5Nc@cp4-web-037.plabs.ch>
On Tue, May 18, 2021 at 11:14:52AM +0000, Simon Ser wrote:
> The kernel versions including the following commits are referenced:
>
> DRM_CLIENT_CAP_STEREO_3D
> 61d8e3282541 ("drm: Add a STEREO_3D capability to the SET_CLIENT_CAP ioctl")
>
> DRM_CLIENT_CAP_UNIVERSAL_PLANES
> 681e7ec73044 ("drm: Allow userspace to ask for universal plane list (v2)")
> c7dbc6c9ae5c ("drm: Remove command line guard for universal planes")
>
> DRM_CLIENT_CAP_ATOMIC
> 88a48e297b3a ("drm: add atomic properties")
> 8b72ce158cf0 ("drm: Always enable atomic API")
>
> DRM_CLIENT_CAP_ASPECT_RATIO
> 7595bda2fb43 ("drm: Add DRM client cap for aspect-ratio")
>
> DRM_CLIENT_CAP_WRITEBACK_CONNECTORS
> d67b6a206507 ("drm: writeback: Add client capability for exposing writeback connectors")
>
> Signed-off-by: Simon Ser <contact@emersion.fr>
> Cc: Daniel Vetter <daniel@ffwll.ch>
> Cc: Daniel Stone <daniels@collabora.com>
> Cc: Pekka Paalanen <ppaalanen@gmail.com>
On the series:
Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
btw your threading is busted.
-Daniel
> ---
> include/uapi/drm/drm.h | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
>
> diff --git a/include/uapi/drm/drm.h b/include/uapi/drm/drm.h
> index 87878aea4526..ec2b122cdcc5 100644
> --- a/include/uapi/drm/drm.h
> +++ b/include/uapi/drm/drm.h
> @@ -780,6 +780,8 @@ struct drm_get_cap {
> * If set to 1, the DRM core will expose the stereo 3D capabilities of the
> * monitor by advertising the supported 3D layouts in the flags of struct
> * drm_mode_modeinfo. See ``DRM_MODE_FLAG_3D_*``.
> + *
> + * This capability is always supported starting from kernel version 3.13.
> */
> #define DRM_CLIENT_CAP_STEREO_3D 1
>
> @@ -788,6 +790,9 @@ struct drm_get_cap {
> *
> * If set to 1, the DRM core will expose all planes (overlay, primary, and
> * cursor) to userspace.
> + *
> + * This capability has been introduced in kernel version 3.15. Starting from
> + * kernel version 3.17, this capability is always supported.
> */
> #define DRM_CLIENT_CAP_UNIVERSAL_PLANES 2
>
> @@ -797,6 +802,13 @@ struct drm_get_cap {
> * If set to 1, the DRM core will expose atomic properties to userspace. This
> * implicitly enables &DRM_CLIENT_CAP_UNIVERSAL_PLANES and
> * &DRM_CLIENT_CAP_ASPECT_RATIO.
> + *
> + * If the driver doesn't support atomic mode-setting, enabling this capability
> + * will fail with -EOPNOTSUPP.
> + *
> + * This capability has been introduced in kernel version 4.0. Starting from
> + * kernel version 4.2, this capability is always supported for atomic-capable
> + * drivers.
> */
> #define DRM_CLIENT_CAP_ATOMIC 3
>
> @@ -805,6 +817,8 @@ struct drm_get_cap {
> *
> * If set to 1, the DRM core will provide aspect ratio information in modes.
> * See ``DRM_MODE_FLAG_PIC_AR_*``.
> + *
> + * This capability is always supported starting from kernel version 4.18.
> */
> #define DRM_CLIENT_CAP_ASPECT_RATIO 4
>
> @@ -814,6 +828,9 @@ struct drm_get_cap {
> * If set to 1, the DRM core will expose special connectors to be used for
> * writing back to memory the scene setup in the commit. The client must enable
> * &DRM_CLIENT_CAP_ATOMIC first.
> + *
> + * This capability is always supported for atomic-capable drivers starting from
> + * kernel version 4.19.
> */
> #define DRM_CLIENT_CAP_WRITEBACK_CONNECTORS 5
>
> --
> 2.31.1
>
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2021-05-19 10:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 11:14 [PATCH 3/3] drm: document minimum kernel version for DRM_CLIENT_CAP_* Simon Ser
2021-05-19 10:18 ` Daniel Vetter [this message]
2021-05-19 10:26 ` Daniel Stone
2021-05-20 8:17 ` Pekka Paalanen
2021-05-31 16:59 ` Simon Ser
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=YKTl4Ei5rB5WH87u@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=contact@emersion.fr \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
/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