dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Padovan <gustavo@padovan.org>
To: Inki Dae <inki.dae@samsung.com>
Cc: linux-samsung-soc@vger.kernel.org,
	dri-devel@lists.freedesktop.org, jy0922.shim@samsung.com,
	tjakobi@math.uni-bielefeld.de,
	Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Subject: Re: [PATCH 03/11] drm/exynos: add prepare and cleanup phases for planes
Date: Wed, 26 Aug 2015 12:45:13 -0300	[thread overview]
Message-ID: <20150826154513.GB1991@joana> (raw)
In-Reply-To: <55DB1473.40109@samsung.com>

Hi Inki,

2015-08-24 Inki Dae <inki.dae@samsung.com>:

> On 2015년 08월 16일 01:26, Gustavo Padovan wrote:
> > From: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
> >
> > .prepare_plane() and .cleanup_plane() allows to perform extra operations
> > before and after the update of planes. For FIMD for example this will
> > be used to enable disable the shadow protection bit.
> >
> > Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
> > ---
> >  drivers/gpu/drm/exynos/exynos_drm_crtc.c | 19 +++++++++++++++++++
> >  drivers/gpu/drm/exynos/exynos_drm_drv.h  |  6 ++++++
> >  2 files changed, 25 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/exynos/exynos_drm_crtc.c b/drivers/gpu/drm/exynos/exynos_drm_crtc.c
> > index 5a19e16..3a89fc9 100644
> > --- a/drivers/gpu/drm/exynos/exynos_drm_crtc.c
> > +++ b/drivers/gpu/drm/exynos/exynos_drm_crtc.c
> > @@ -72,15 +72,34 @@ exynos_drm_crtc_mode_set_nofb(struct drm_crtc *crtc)
> >  static void exynos_crtc_atomic_begin(struct drm_crtc *crtc)
> >  {
> >  	struct exynos_drm_crtc *exynos_crtc = to_exynos_crtc(crtc);
> > +	struct drm_plane *plane;
> >
> >  	if (crtc->state->event) {
> >  		WARN_ON(drm_crtc_vblank_get(crtc) != 0);
> >  		exynos_crtc->event = crtc->state->event;
> >  	}
> > +
> > +	drm_atomic_crtc_for_each_plane(plane, crtc) {
> > +		struct exynos_drm_plane *exynos_plane = to_exynos_plane(plane);
> > +
> > +		if (exynos_crtc->ops->prepare_plane)
> > +			exynos_crtc->ops->prepare_plane(exynos_crtc,
> > +							exynos_plane);
> 
> There is no any reason to use prepare_plane/cleanup_plane callback
> names. How about using atomic_begin/atomic_flush callback names instead
> for consistency between framework and device drivers?

Either names are fine for me. So let's go with atomic_begin/flush. I'll
send an updated patchset.

	Gustavo

  reply	other threads:[~2015-08-26 15:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-15 16:26 [PATCH 00/11] drm/exynos: improve atomic modesetting Gustavo Padovan
2015-08-15 16:26 ` [PATCH 01/11] drm/exynos: don't track enabled state at exynos_crtc Gustavo Padovan
2015-08-15 16:26 ` [PATCH 02/11] drm/exynos: fimd: unify call to exynos_drm_crtc_finish_pageflip() Gustavo Padovan
2015-08-15 16:26 ` [PATCH 03/11] drm/exynos: add prepare and cleanup phases for planes Gustavo Padovan
2015-08-24 12:56   ` Inki Dae
2015-08-26 15:45     ` Gustavo Padovan [this message]
2015-08-27  8:14       ` Inki Dae
2015-08-15 16:26 ` [PATCH 04/11] drm/exynos: fimd: move window protect code to prepare/cleanup_plane Gustavo Padovan
2015-08-15 16:26 ` [PATCH 05/11] drm/exynos: check for pending fb before finish update Gustavo Padovan
2015-08-15 16:26 ` [PATCH 06/11] drm/exynos: add macro to get the address of START_S reg Gustavo Padovan
2015-08-15 16:26 ` [PATCH 07/11] drm/exynos: fimd: only finish update if START == START_S Gustavo Padovan
2015-08-15 16:26 ` [PATCH 08/11] drm/exynos: add atomic asynchronous commit Gustavo Padovan
2015-08-15 16:26 ` [PATCH 09/11] drm/exynos: wait all planes updates to finish Gustavo Padovan
2015-08-15 16:26 ` [PATCH 10/11] drm/exynos: remove wait queue for pending page flip Gustavo Padovan
2015-08-15 16:26 ` [PATCH 11/11] drm/exynos: Enable atomic modesetting feature Gustavo Padovan

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=20150826154513.GB1991@joana \
    --to=gustavo@padovan.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gustavo.padovan@collabora.co.uk \
    --cc=inki.dae@samsung.com \
    --cc=jy0922.shim@samsung.com \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=tjakobi@math.uni-bielefeld.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