Re: RFC: Request API and memory-to-memory devices

On 05/25/2018 05:26 PM, Hans Verkuil wrote: > On 25/05/18 16:16, Sakari Ailus wrote: >> Hi Hans, >> >> On Thu, May 24, 2018 at 10:44:13AM +0200, Hans Verkuil wrote: >>> Memory-to-memory devices have one video node, one internal control handler >>> but two vb2_queues (DMA engines). While often

Re: RFC: Request API and memory-to-memory devices

On 25/05/18 16:16, Sakari Ailus wrote: > Hi Hans, > > On Thu, May 24, 2018 at 10:44:13AM +0200, Hans Verkuil wrote: >> Memory-to-memory devices have one video node, one internal control handler >> but two vb2_queues (DMA engines). While often there is one buffer produced >> for every buffer

Re: RFC: Request API and memory-to-memory devices

On Fri, May 25, 2018 at 11:17 PM Sakari Ailus wrote: > Hi Hans, > On Thu, May 24, 2018 at 10:44:13AM +0200, Hans Verkuil wrote: > > Memory-to-memory devices have one video node, one internal control handler > > but two vb2_queues (DMA engines). While often there is

Re: RFC: Request API and memory-to-memory devices

Hi Hans, On Thu, May 24, 2018 at 10:44:13AM +0200, Hans Verkuil wrote: > Memory-to-memory devices have one video node, one internal control handler > but two vb2_queues (DMA engines). While often there is one buffer produced > for every buffer consumed, but this is by no means standard. E.g. >

Re: RFC: Request API and memory-to-memory devices

On Thu, May 24, 2018 at 5:44 PM Hans Verkuil wrote: > Memory-to-memory devices have one video node, one internal control handler > but two vb2_queues (DMA engines). While often there is one buffer produced > for every buffer consumed, but this is by no means standard. E.g.

RFC: Request API and memory-to-memory devices

Memory-to-memory devices have one video node, one internal control handler but two vb2_queues (DMA engines). While often there is one buffer produced for every buffer consumed, but this is by no means standard. E.g. deinterlacers will produce on buffer for every two buffers consumed. Codecs that