All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joonyoung Shim <jy0922.shim@samsung.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [RFC PATCH] drm: Add plane event
Date: Wed, 18 Apr 2012 19:11:45 +0900	[thread overview]
Message-ID: <4F8E9361.3080004@samsung.com> (raw)
In-Reply-To: <20120418084634.GC5315@phenom.ffwll.local>

On 04/18/2012 05:46 PM, Daniel Vetter wrote:
> On Wed, Apr 18, 2012 at 01:31:59PM +0900, Joonyoung Shim wrote:
>> DRM_MODE_PLANE_EVENT is similar to DRM_MODE_PAGE_FLIP_EVENT but it is
>> for a plane. The setplane ioctl (DRM_IOCTL_MODE_SETPLANE) needs to
>> provide the event such as DRM_MODE_PAGE_FLIP_EVENT. The setplane ioctl
>> can change the framebuffer of plane but user can't know completion of
>> changing the framebuffer of plane via event. If DRM_MODE_PLANE_EVENT is
>> added, we can also do pageflip of a plane.
>>
>> Signed-off-by: Joonyoung Shim<jy0922.shim@samsung.com>
>> Signed-off-by: Kyungmin Park<kyungmin.park@samsung.com>
> If I understand the current kms api correctly, set_plane is akin to
> set_base and should not generate an asynchronous flip completion event. To
> do that we need a new pageflip ioctl which changes a complete set of fb +
> planes + any crtc attributes that might be in an atomic fashion. At which
> point we can just reuse the existing page flip event mechanism.

It seems better way to add new pageflip ioctl for plane. I will try it.

Thanks for review.

  reply	other threads:[~2012-04-18 10:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-18  4:31 [RFC PATCH] drm: Add plane event Joonyoung Shim
2012-04-18  8:46 ` Daniel Vetter
2012-04-18 10:11   ` Joonyoung Shim [this message]
2012-04-18 12:25     ` Rob Clark
2012-04-18 14:04       ` Marcus Lorentzon
2012-04-18 14:26         ` Ville Syrjälä
2012-04-18 14:36           ` Daniel Vetter
2012-04-18 15:10             ` Marcus Lorentzon
2012-04-18 15:27               ` Daniel Vetter
2012-04-18 15:55                 ` Marcus Lorentzon
2012-04-18 16:04                   ` Jesse Barnes
2012-04-18 19:08                   ` Daniel Vetter
2012-04-18 16:06                 ` Ville Syrjälä
2012-04-18 16:26                   ` Marcus Lorentzon
2012-04-18 18:19                   ` Ville Syrjälä
2012-04-19  8:10                     ` Daniel Vetter
2012-04-18 15:43               ` Luc Verhaegen
2012-04-18 16:00                 ` Marcus Lorentzon
2012-04-19  1:24             ` Kristian Høgsberg
2012-04-19  8:05               ` Daniel Vetter
2012-04-18 14:58           ` Marcus Lorentzon
2012-04-18 15:57             ` Jesse Barnes
2012-04-18 16:47 ` Luc Verhaegen

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=4F8E9361.3080004@samsung.com \
    --to=jy0922.shim@samsung.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.