On Tue, 18 May 2021 11:14:47 +0000
Simon Ser <[email protected]> wrote:

> Make it clear that the client is responsible for enabling ATOMIC
> prior to enabling WRITEBACK_CONNECTORS. Linkify the reference to
> ATOMIC.
> 
> Signed-off-by: Simon Ser <[email protected]>
> Cc: Daniel Vetter <[email protected]>
> Cc: Daniel Stone <[email protected]>
> Cc: Pekka Paalanen <[email protected]>
> ---
>  include/uapi/drm/drm.h | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/include/uapi/drm/drm.h b/include/uapi/drm/drm.h
> index 1c947227f72b..87878aea4526 100644
> --- a/include/uapi/drm/drm.h
> +++ b/include/uapi/drm/drm.h
> @@ -812,8 +812,8 @@ struct drm_get_cap {
>   * DRM_CLIENT_CAP_WRITEBACK_CONNECTORS
>   *
>   * 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. Depends on client
> - * also supporting DRM_CLIENT_CAP_ATOMIC
> + * writing back to memory the scene setup in the commit. The client must 
> enable
> + * &DRM_CLIENT_CAP_ATOMIC first.
>   */
>  #define DRM_CLIENT_CAP_WRITEBACK_CONNECTORS  5
>  

I'll take your word that this is how it must be done.

Acked-by: Pekka Paalanen <[email protected]>


Thanks,
pq

Attachment: pgp2kBhQjr6zK.pgp
Description: OpenPGP digital signature

Reply via email to