From: Sam Ravnborg <sam@ravnborg.org>
To: Liviu Dudau <liviu.dudau@arm.com>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
David Airlie <airlied@linux.ie>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
dri-devel@lists.freedesktop.org,
Thomas Zimmermann <tzimmermann@suse.de>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH v2 2/3] drm: writeback: document callbacks
Date: Tue, 7 Apr 2020 17:51:25 +0200 [thread overview]
Message-ID: <20200407155125.GA24075@ravnborg.org> (raw)
In-Reply-To: <20200407120431.GI364558@e110455-lin.cambridge.arm.com>
On Tue, Apr 07, 2020 at 01:04:31PM +0100, Liviu Dudau wrote:
> On Mon, Apr 06, 2020 at 09:47:45PM +0200, Sam Ravnborg wrote:
> > Document the callbacks:
> > drm_connector_helper_funcs.prepare_writeback_job
> > drm_connector_helper_funcs.cleanup_writeback_job
> >
> > The documentation was pulled from the changelong introducing the
> > callbacks, originally written by Laurent.
> >
> > Adding the missing documentation fixes the following warnings:
> > drm_modeset_helper_vtables.h:1052: warning: Function parameter or member 'prepare_writeback_job' not described in 'drm_connector_helper_funcs'
> > drm_modeset_helper_vtables.h:1052: warning: Function parameter or member 'cleanup_writeback_job' not described in 'drm_connector_helper_funcs'
> >
> > v2:
> > - Fix formatting (Daniel)
> > - Drop changelog text and add reference (Daniel)
> > - Improve grammar. and use "operation" (Laurent)
> >
> > Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
> > Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> > Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
> > Cc: Liviu Dudau <liviu.dudau@arm.com>
>
> Reviewed-by: Liviu Dudau <liviu.dudau@arm.com>
Thanks, applied to drm-misc-next and pushed out.
Sam
>
> Thanks!
> Liviu
>
> > Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> > Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> > Cc: Maxime Ripard <mripard@kernel.org>
> > Cc: Thomas Zimmermann <tzimmermann@suse.de>
> > Cc: David Airlie <airlied@linux.ie>
> > ---
> > include/drm/drm_modeset_helper_vtables.h | 27 ++++++++++++++++++++++++
> > 1 file changed, 27 insertions(+)
> >
> > diff --git a/include/drm/drm_modeset_helper_vtables.h b/include/drm/drm_modeset_helper_vtables.h
> > index 7c20b1c8b6a7..421a30f08463 100644
> > --- a/include/drm/drm_modeset_helper_vtables.h
> > +++ b/include/drm/drm_modeset_helper_vtables.h
> > @@ -1075,8 +1075,35 @@ struct drm_connector_helper_funcs {
> > void (*atomic_commit)(struct drm_connector *connector,
> > struct drm_connector_state *state);
> >
> > + /**
> > + * @prepare_writeback_job:
> > + *
> > + * As writeback jobs contain a framebuffer, drivers may need to
> > + * prepare and clean them up the same way they can prepare and
> > + * clean up framebuffers for planes. This optional connector operation
> > + * is used to support the preparation of writeback jobs. The job
> > + * prepare operation is called from drm_atomic_helper_prepare_planes()
> > + * for struct &drm_writeback_connector connectors only.
> > + *
> > + * This operation is optional.
> > + *
> > + * This callback is used by the atomic modeset helpers.
> > + */
> > int (*prepare_writeback_job)(struct drm_writeback_connector *connector,
> > struct drm_writeback_job *job);
> > + /**
> > + * @cleanup_writeback_job:
> > + *
> > + * This optional connector operation is used to support the
> > + * cleanup of writeback jobs. The job cleanup operation is called
> > + * from the existing drm_writeback_cleanup_job() function, invoked
> > + * both when destroying the job as part of an aborted commit, or when
> > + * the job completes.
> > + *
> > + * This operation is optional.
> > + *
> > + * This callback is used by the atomic modeset helpers.
> > + */
> > void (*cleanup_writeback_job)(struct drm_writeback_connector *connector,
> > struct drm_writeback_job *job);
> > };
> > --
> > 2.20.1
> >
>
> --
> ====================
> | I would like to |
> | fix the world, |
> | but they're not |
> | giving me the |
> \ source code! /
> ---------------
> ¯\_(ツ)_/¯
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-04-07 15:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 19:47 [PATCH v2 0/3] drm: kernel-doc stuff Sam Ravnborg
2020-04-06 19:47 ` [PATCH v2 1/3] drm/vblank: Add intro to documentation Sam Ravnborg
2020-04-06 22:53 ` Lyude Paul
2020-04-07 6:24 ` Thomas Zimmermann
2020-04-07 12:03 ` Liviu Dudau
2020-04-07 14:42 ` Alex Deucher
2020-04-07 16:42 ` Sam Ravnborg
2020-04-06 19:47 ` [PATCH v2 2/3] drm: writeback: document callbacks Sam Ravnborg
2020-04-07 12:04 ` Liviu Dudau
2020-04-07 15:51 ` Sam Ravnborg [this message]
2020-04-06 19:47 ` [PATCH v2 3/3] drm/writeback: wire drm_writeback.h to kernel-doc Sam Ravnborg
2020-04-07 8:08 ` Daniel Vetter
2020-04-07 15:51 ` Sam Ravnborg
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=20200407155125.GA24075@ravnborg.org \
--to=sam@ravnborg.org \
--cc=airlied@linux.ie \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=liviu.dudau@arm.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