From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 5/5] drm: omapdrm: Add zpos property
Date: Mon, 24 Apr 2017 17:05:28 +0300 [thread overview]
Message-ID: <124441161.G11UIeOkjz@avalon> (raw)
In-Reply-To: <2141732.4ZUo233FVj@avalon>
Hi Tomi,
On Monday 24 Apr 2017 17:00:52 Laurent Pinchart wrote:
> On Monday 24 Apr 2017 12:37:24 Tomi Valkeinen wrote:
> > On 15/04/17 12:16, Laurent Pinchart wrote:
> >> Create a standard zpos property for every plane as an alias to the
> >> omapdrm-specific zorder property. Unlike the zorder property that has to
> >> be instantiated for both planes and CRTCs due to backward compatibility,
> >> the zpos property is only instantiated for planes. When userspace will
> >> have switched to the zpos property the zorder property will be removed.
> >>
> >> Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> >> ---
> >>
> >> drivers/gpu/drm/omapdrm/omap_plane.c | 1 +
> >> 1 file changed, 1 insertion(+)
> >>
> >> diff --git a/drivers/gpu/drm/omapdrm/omap_plane.c
> >> b/drivers/gpu/drm/omapdrm/omap_plane.c index 521dd2ea519a..871a89b87e72
> >> 100644
> >> --- a/drivers/gpu/drm/omapdrm/omap_plane.c
> >> +++ b/drivers/gpu/drm/omapdrm/omap_plane.c
> >> @@ -324,6 +324,7 @@ struct drm_plane *omap_plane_init(struct drm_device
> >> *dev,
> >>
> >> drm_plane_helper_add(plane, &omap_plane_helper_funcs);
> >>
> >> omap_plane_install_properties(plane, &plane->base);
> >>
> >> + drm_plane_create_zpos_property(plane, 0, 0, 3);
> >
> > I think this should use get_num_ovls() to get the max value.
>
> That's fine with me, but note that the code currently hardcodes the value to
> 3 for the zorder property. I can submit an addition patch on top of this to
> change both if you think it would be better.
And should it be get_num_ovls() - 1 ? The zorder register field is two bits
wide, and we have up to 4 overlays on OMAP4. This will change the maximum
value of the property from 3 to 2 on OMAP3. Do you think that could cause
issues ?
--
Regards,
Laurent Pinchart
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-04-24 14:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-15 9:16 [PATCH v2 0/5] omapdrm: fences and zpos Laurent Pinchart
2017-04-15 9:16 ` [PATCH v2 1/5] drm: omapdrm: Handle events when enabling/disabling CRTCs Laurent Pinchart
2017-04-24 9:59 ` Tomi Valkeinen
2017-04-15 9:16 ` [PATCH v2 2/5] drm: omapdrm: Use DRM core's atomic commit helper Laurent Pinchart
2017-04-27 10:45 ` Tomi Valkeinen
2017-04-15 9:16 ` [PATCH v2 3/5] drm: omapdrm: Remove legacy buffer synchronization support Laurent Pinchart
2017-04-18 6:20 ` Daniel Vetter
2017-04-18 8:59 ` Laurent Pinchart
2017-04-15 9:16 ` [PATCH v2 4/5] drm: omapdrm: Store the Z order in the plane state zpos field Laurent Pinchart
2017-04-24 9:40 ` Tomi Valkeinen
2017-04-24 14:00 ` Laurent Pinchart
2017-04-25 9:01 ` Tomi Valkeinen
2017-04-15 9:16 ` [PATCH v2 5/5] drm: omapdrm: Add zpos property Laurent Pinchart
2017-04-24 9:37 ` Tomi Valkeinen
2017-04-24 14:00 ` Laurent Pinchart
2017-04-24 14:05 ` Laurent Pinchart [this message]
2017-04-25 8:56 ` Tomi Valkeinen
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=124441161.G11UIeOkjz@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=tomi.valkeinen@ti.com \
/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