[lkml]   [2017]   [Aug]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 3/3] drm: Add CRTC_GET_SEQUENCE and CRTC_QUEUE_SEQUENCE ioctls [v2]
Michel Dänzer <> writes:

> [...]
>> +#define DRM_CRTC_SEQUENCE_NEXT_ON_MISS 0x00000002 /* Use next sequence if we've missed */
> Do you have userspace making use of DRM_CRTC_SEQUENCE_NEXT_ON_MISS? If
> not, drop it.

I added this so that the new ioctl would be compatible with the old
ioctl; do you think that's unnecessary?
>> +#define DRM_CRTC_SEQUENCE_FIRST_PIXEL_OUT 0x00000004 /* Signal when first pixel is displayed */
> I thought there was consensus that this flag is pointless.

I just wrote a note to Daniel about this; I think it is useful in that
applications could specify that they actually want the event delivered
at first pixel out in accordance with the Vulkan spec, even if we can't
do that (yet). I definitely agree that requiring the bit be set is
ridiculous and should be removed.

Two choices

1) Remove the code which checks whether the flag is set.
Make Vulkan set the flag signaling what it wants.
Plan on doing the actual driver work if we find that it's necessary.

2) Remove the flag entirely.

Any preference?

[unhandled content-type:application/pgp-signature]
 \ /
  Last update: 2017-08-06 07:42    [W:0.133 / U:2.924 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site