<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 2018年09月18日 16:32, Christian König
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:2bea4bc7-ce1f-e1ff-8308-d932d108f237@gmail.com">
<blockquote type="cite" style="color: #000000;">
<blockquote type="cite" style="color: #000000;">
<blockquote type="cite" style="color: #000000;">+ for (i =
0; i < args->count_handles; i++) {
<br>
+ if (syncobjs[i]->type ==
DRM_SYNCOBJ_TYPE_TIMELINE) {
<br>
+ DRM_ERROR("timeline syncobj cannot reset!\n");
<br>
</blockquote>
<br>
Why not? I mean that should still work or do I miss anything?
<br>
</blockquote>
timeline semaphore spec doesn't require reset interface, it says
the timeline value only can be changed by signal operations.
<br>
</blockquote>
<br>
Yeah, but we don't care about the timeline spec in the kernel.
<br>
<br>
Question is rather if that still makes sense to support that and
as far as I can see it should be trivial to reinitialize the
object.
</blockquote>
Hi Daniel Rakos,<br>
<br>
Could you give a comment on this question? Is it necessary to
support timeline reset interface? I only see the timeline value can
be changed by signal operations in Spec.<br>
<br>
<br>
Thanks,<br>
David Zhou<br>
</body>
</html>