[Bug 726325] RFC: Add tunneling support.

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=726325
  GStreamer | gst-omx | git

--- Comment #26 from deathsimple at vodafone.de <deathsimple at vodafone.de> 2014-03-19 12:10:34 UTC ---
(In reply to comment #19)
> Review of attachment 271865 [details]:
> 
> ::: omx/gstomx.c
> @@ +2001,3 @@
> +    g_mutex_unlock (&tunneled->comp->lock);
> +  }
> +
> 
> When tunneling, does it mean gst_omx_port_set_enabled_unlocked will be called
> twice on each port when tunneled ?
> I mean in the case of tunneling element1 ! element2 then element1 will enable
> its output port and the peer. And the element2 will enable its input port and
> the peer. So total would be 4 call to gst_omx_port_set_enabled_unlocked, 2 for
> each omx port.

Yes that's correct, but the second calls are pretty much nops.

> 
> @@ +2194,3 @@
> +    g_mutex_unlock (&tunneled->comp->lock);
> +  }
> +
> 
> When tunneling, could it lead to a dead lock ? each port waiting for the other
> to be enabled ? (omxelem1 ! omxelem2)

Not as far as I can see.

The problem I'm trying to solve is that for reaching idle/loaded state of a
component you usually needs to enable/disable both ends of the tunnel.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.