From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH 1/8] drm/omap: Simplify the rotation-on-crtc hack
Date: Mon, 31 Jul 2017 14:56:16 +0300 [thread overview]
Message-ID: <6b34707b-fed4-1c1d-e050-9eebee2a923d@ti.com> (raw)
In-Reply-To: <5875908.nkarGct6Ju@avalon>
[-- Attachment #1.1.1: Type: text/plain, Size: 1420 bytes --]
On 31/07/17 14:48, Laurent Pinchart wrote:
>>> The comment about read lock is only valid when the plane is bound to the
>>> crtc. In general this is not always the case. You can only peak at
>>> plane->state when crtc->state->plane_mask & BIT(drm_plane_index(plane))
>>> is true.
>>>
>>> I think we might need -EDEADLK handling for getprop then, even though it's
>>> not optimal. :(
>>
>> Well both the old an new way only worked because we grab all the locks
>> unconditionally. And I'd really want to avoid get_prop being anything
>> but a simple lookup. Unfortuantely that breaks omapdrm, so no idea
>> what exactly to do here.
>>
>> In a way adding properties without standardizing them across drivers
>> first was a really bad idea, because then we have disjoint sets of
>> uapi expectations, and there's just no way to make that work.
>>
>> I guess one radical approach might be to make this the "standard", and
>> just redirect rotation from the CRTC to the primary plane.
>>
>> Or omapdrm needs to duplicate the property properly, and update one if
>> the other is set. I think that's probably the most workable approach.
>
> Maybe the first question we should answer is whether this hack is still needed
> in the omapdrm driver. Tomi, do you know whether userspace still needs this ?
The omap X driver uses legacy modesetting and the rotation property for
the crtc.
Tomi
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-07-31 11:56 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 8:01 [PATCH 0/8] acquire ctx for everyone! Daniel Vetter
2017-07-25 8:01 ` [PATCH 1/8] drm/omap: Simplify the rotation-on-crtc hack Daniel Vetter
2017-07-25 8:47 ` Maarten Lankhorst
2017-07-25 9:24 ` [Intel-gfx] " Daniel Vetter
2017-07-31 11:48 ` Laurent Pinchart
2017-07-31 11:56 ` Tomi Valkeinen [this message]
2017-07-25 8:01 ` [PATCH 2/8] drm: Don't update property values for atomic drivers Daniel Vetter
2017-07-25 8:32 ` Maarten Lankhorst
2017-07-25 12:01 ` [PATCH] " Daniel Vetter
2017-08-11 22:20 ` [PATCH 2/8] " Laurent Pinchart
2017-08-14 7:25 ` Daniel Vetter
2017-08-14 10:32 ` Laurent Pinchart
2017-08-14 14:09 ` Daniel Vetter
2017-07-25 8:01 ` [PATCH 3/8] drm: Handle properties in the core " Daniel Vetter
2017-07-25 9:36 ` Archit Taneja
2017-07-25 12:02 ` [PATCH] " Daniel Vetter
2017-07-25 8:01 ` [PATCH 4/8] drm: Nuke drm_atomic_helper_crtc_set_property Daniel Vetter
2017-07-25 9:38 ` Archit Taneja
2017-07-25 10:05 ` Philippe CORNU
2017-08-03 13:34 ` Thomas Hellstrom
2017-07-25 8:01 ` [PATCH 5/8] drm: Nuke drm_atomic_helper_plane_set_property Daniel Vetter
2017-07-25 9:38 ` Archit Taneja
2017-07-25 10:06 ` Philippe CORNU
2017-07-28 16:45 ` Liviu Dudau
2017-08-08 10:03 ` Vincent ABRIOU
2017-08-08 12:31 ` Laurent Pinchart
[not found] ` <20170725080122.20548-1-daniel.vetter-/w4YWyX8dFk@public.gmane.org>
2017-07-25 8:01 ` [PATCH 6/8] drm: Nuke drm_atomic_helper_connector_set_property Daniel Vetter
[not found] ` <20170725080122.20548-7-daniel.vetter-/w4YWyX8dFk@public.gmane.org>
2017-07-25 9:23 ` [Intel-gfx] " Maarten Lankhorst
2017-07-25 9:26 ` Daniel Vetter
2017-08-08 10:04 ` Vincent ABRIOU
2017-07-25 8:01 ` [PATCH 7/8] drm: Nuke drm_atomic_helper_connector_dpms Daniel Vetter
2017-07-25 8:04 ` Neil Armstrong
2017-07-25 8:59 ` Philipp Zabel
2017-07-25 9:30 ` Archit Taneja
2017-07-25 10:07 ` Philippe CORNU
2017-07-25 14:01 ` Laurent Pinchart
2017-07-25 14:42 ` Shawn Guo
2017-07-26 19:00 ` Noralf Trønnes
2017-08-08 10:05 ` Vincent ABRIOU
2017-07-25 8:01 ` [PATCH 8/8] drm: Nuke drm_atomic_legacy_backoff Daniel Vetter
2017-07-25 9:36 ` [Intel-gfx] " Maarten Lankhorst
2017-07-25 8:44 ` ✓ Fi.CI.BAT: success for acquire ctx for everyone! Patchwork
2017-07-25 12:05 ` ✗ Fi.CI.BAT: failure for acquire ctx for everyone! (rev3) Patchwork
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=6b34707b-fed4-1c1d-e050-9eebee2a923d@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.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