Linux Samsung SOC development
 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,
	Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Subject: Re: [PATCH -v4 5/8] drm/exynos: make zpos property immutable
Date: Fri, 3 Apr 2015 11:59:53 -0300	[thread overview]
Message-ID: <20150403145953.GA2208@joana> (raw)
In-Reply-To: <551E79C0.10105@samsung.com>

Hi Inki,

2015-04-03 Inki Dae <inki.dae@samsung.com>:

> On 2015년 04월 02일 01:02, Gustavo Padovan wrote:
> > From: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
> >
> > We already set each plane zpos at init, after that changes to zpos are
> > not expected. This patch turns zpos into a read-only property so now it is
> > impossible to set zpos.
> >
> > Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
> > ---
> >  drivers/gpu/drm/exynos/exynos_drm_plane.c | 21 ++-------------------
> >  1 file changed, 2 insertions(+), 19 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/exynos/exynos_drm_plane.c b/drivers/gpu/drm/exynos/exynos_drm_plane.c
> > index 504bd6e..2fbac9b 100644
> > --- a/drivers/gpu/drm/exynos/exynos_drm_plane.c
> > +++ b/drivers/gpu/drm/exynos/exynos_drm_plane.c
> > @@ -184,27 +184,10 @@ static void exynos_plane_destroy(struct drm_plane *plane)
> >  	drm_plane_cleanup(plane);
> >  }
> >
> > -static int exynos_plane_set_property(struct drm_plane *plane,
> > -				     struct drm_property *property,
> > -				     uint64_t val)
> > -{
> > -	struct drm_device *dev = plane->dev;
> > -	struct exynos_drm_plane *exynos_plane = to_exynos_plane(plane);
> > -	struct exynos_drm_private *dev_priv = dev->dev_private;
> > -
> > -	if (property == dev_priv->plane_zpos_property) {
> > -		exynos_plane->zpos = val;
> > -		return 0;
> > -	}
> > -
> > -	return -EINVAL;
> > -}
> > -
> >  static struct drm_plane_funcs exynos_plane_funcs = {
> >  	.update_plane	= exynos_update_plane,
> >  	.disable_plane	= exynos_disable_plane,
> >  	.destroy	= exynos_plane_destroy,
> > -	.set_property	= exynos_plane_set_property,
> 
> As I commented like below before, This patch would make the
> compatibility of the existing application which uses set_property ioctl
> to be broken. Didn't you check my comment?
> http://www.spinics.net/lists/dri-devel/msg78852.html

I checked that and it is currently not possible to output a error message
when an property is set to immutable. The drm core will return earlier
and never call the driver's set_property callback. We won't be able to add
the error message but I think we need this patch.

	Gustavo

  reply	other threads:[~2015-04-03 14:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-01 16:02 [PATCH -v4 0/8] drm/exynos: clean up patches (preparing for atomic) Gustavo Padovan
2015-04-01 16:02 ` [PATCH -v4 1/8] drm/exynos: fimd: fix alpha setting for XR24 pixel format Gustavo Padovan
2015-04-01 16:02 ` [PATCH -v4 2/8] drm/exynos: remove unused exynos_crtc->win_enable() callback Gustavo Padovan
2015-04-01 16:02 ` [PATCH -v4 3/8] drm/exynos: remove struct *_win_data abstraction on planes Gustavo Padovan
2015-04-01 16:02 ` [PATCH -v4 4/8] drm/exynos: preset zpos value for overlay planes Gustavo Padovan
2015-04-01 16:02 ` [PATCH -v4 5/8] drm/exynos: make zpos property immutable Gustavo Padovan
2015-04-03 11:30   ` Inki Dae
2015-04-03 14:59     ` Gustavo Padovan [this message]
2015-04-01 16:02 ` [PATCH -v4 6/8] drm/exynos: remove exynos_plane_destroy() Gustavo Padovan
2015-04-01 16:02 ` [PATCH -v4 7/8] drm/exynos: remove leftover functions declarations Gustavo Padovan
2015-04-01 16:02 ` [PATCH -v4 8/8] drm/exynos: track vblank events on a per crtc basis Gustavo Padovan
2015-04-06 10:38 ` [PATCH -v4 0/8] drm/exynos: clean up patches (preparing for atomic) Inki Dae

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=20150403145953.GA2208@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 \
    /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