how can deal with the stream in only on-the-fly-output available HW block??
-----Original Message-----
From: Kim, HeungJun [mailto:[email protected]]
Sent: Tuesday, September 14, 2010 2:02 PM
To: '[email protected]'; '[email protected]'
Subject: RE: how can deal with the stream in only on-the-fly-output available HW block??
Quoted 9 lines · HeungJun
Quoted 6 lines
Hi all,
What if some SoC's specific HW block supports only on-the-fly mode for stream output??
What do you mean with 'on-the-fly mode'? Does that mean that two HW
blocks
Quoted 1 line
are linked together so that the video stream goes directly from one to
the
Quoted 1 line
other without ever being DMA-ed to memory?
You're right. It's linked with internal SRAM FIFO. So, syncing streams with both blocks is kept with VSync Interrupt. It's not using DMA-ed to memory in this mode.
Quoted 5 lines
Quoted 3 lines
In this case, what is the suitable
buf_type??Suitable
buf_typefor doing what?
I wanna define this blocks topology with V4L2 APIs. But, I don't find suitable buf_type or any definitions in the V4L2 APIs with current SoC's block media topology.
Quoted 2 lines
You probably need the upcoming media API to be able to correctly deal
with
Quoted 4 lines
these issues. Check the mailing list for the patches done by Laurent Pinchart.
The current V4L2 API is really not able to handle changes in the
internal
Quoted 1 line
video stream topology.
Thanks to Hans. It's very helpful.
I'll check Laurent's media topology patches.
Hello, Laurent,
I'm googling and find your patches, so I'm checking with. But, where can I get your patches?? Probably, I would find in this page :
http://git.linuxtv.org/, so what's your repository?
Regards,
HeungJun, Kim
Quoted 6 lines
Regards,
Hans
Quoted 1 line
Quoted 12 lines
Quoted 5 lines
I'm faced with such problem.
As explanation for my situation briefly, the processor I deal with now
has 3
Quoted 1 line
Multimedia H/W blocks, and the problem-one in the 3 blocks do the work
for
Quoted 4 lines
sensor-interfacing and pre-processing.
It supports CCD or CMOS for input, and DMA or On-The-Fly for output. Exactly, it has two cases - DMA mode using memory bus & On-The-Fly
mode
Quoted 9 lines
Quoted 9 lines
connected with any other multimedia blocks.
Also, it use only one format "Bayer RGB" in case of mode the DMA and On-The-Fly mode both.
So, when the device operates in the On-The-Fly mode, is it alright the driver's current type is
V4L2_BUF_TYPE_VIDEO_CAPTURE? or something
else?
Quoted 2 lines
Quoted 2 lines
or if setting
buf_typeis wrong itself, what v4l2 API flow is right
for
Quoted 5 lines
Quoted 5 lines
driver or userspace??
the v4l2
buf_typeenumeratinos is defined here, but I have no idea
about
Quoted 1 line
Quoted 1 line
suitable enum value in this case, also except for any other under
enums
Quoted 39 lines
too.
Quoted 23 lines
V4L2_BUF_TYPE_VIDEO_CAPTURE= 1,
V4L2_BUF_TYPE_VIDEO_OUTPUT= 2,
V4L2_BUF_TYPE_VIDEO_OVERLAY= 3,
V4L2_BUF_TYPE_VBI_CAPTURE= 4,
V4L2_BUF_TYPE_VBI_OUTPUT= 5,
V4L2_BUF_TYPE_SLICED_VBI_CAPTURE= 6,
V4L2_BUF_TYPE_SLICED_VBI_OUTPUT= 7,
V4L2_BUF_TYPE_VIDEO_OUTPUT_OVERLAY= 8,
V4L2_BUF_TYPE_PRIVATE=0x80,Quoted 11 lines
I'll thanks for any idea or answer.
Regards,
HeungJun, Kim
--
Hans Verkuil - video4linux developer - sponsored by TANDBERG, part of Cisco
Hi Kim,
On Tuesday 14 September 2010 07:11:29 Kim, HeungJun wrote:
[snip]
Quoted 7 lines
Quoted 6 lines
You probably need the upcoming media API to be able to correctly deal with these issues. Check the mailing list for the patches done by Laurent Pinchart.
The current V4L2 API is really not able to handle changes in the internal video stream topology.
Quoted 8 lines
Thanks to Hans. It's very helpful.
I'll check Laurent's media topology patches.Hello, Laurent,
I'm googling and find your patches, so I'm checking with. But, where can I get your patches?? Probably, I would find in this page :
http://git.linuxtv.org/, so what's your repository?
Clone http://git.linuxtv.org/pinchartl/media.git and checkout the media-0003- subdev-pad branch.
Signature · 3 lines
Regards, Laurent Pinchart