From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/2] Add VSP1 devices to DT for r8a7790 and r8a7791
Date: Mon, 22 Dec 2014 09:27:35 +0000 [thread overview]
Message-ID: <1749192.EjGsnkTb20@avalon> (raw)
In-Reply-To: <1410651385-13090-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
Hi Sakari,
On Saturday 20 December 2014 23:46:00 Sakari Ailus wrote:
> On Sat, Dec 20, 2014 at 09:00:11PM +0200, Laurent Pinchart wrote:
> > On Friday 19 December 2014 05:05:22 Devendra Talegaonkar wrote:
> > > Hi,
> > > Thanks for the reply. I could successfully stream file data to display
> > > via media link. Now on Lager board, I am trying to stream live video
> > > data captured from camera ( VIN1 input via ADV7180 decoder, RGB565 ) to
> > > display. I am using yavta to capture data from camera and streaming it
> > > to rpf.0. But I am not able to see data on VGA. I am using following
> > > commands to establish media link ./vsp1.sh media1 m2d ARGB565 ARGB32
> > > Then yavta to capture and stream data with following command:
> > > "./yavta -c -n 4 -f RGB565 -s 400x200 /dev/video1 /dev/video10" (
> > > video10
> > > being associated dev for rpf.0) modetest command as follows:
> > > "./modetest -M rcar-du -s 17@11:1024x768@AR24 -d -P
> > > '11@32:1024x768@XR24"
> > >
> > > Am I missing something or doing something wrong?
> >
> > Yes. Or actually yavta is missing something :-) yavta is able to capture
> > from a video node to file, or output the contents of a file to a video
> > node, but doesn't have the ability to capture from one video node and
> > feed the frames to another video node.
> >
> > That would be an interesting addition to yavta though as it would allow
> > exercising the dmabuf code paths, but I wonder whether it would really fit
> > in yavta's original purpose as a low-level V4L2 test tool.
> >
> > Sakari, you're somehow familiar with the code base, what would you think ?
>
> I propose to implement reading from and writing to a given file handle (or
> just stdin/stdout). I don't think we currently have them at the moment, but
> it'd fit well for yavta IMHO. This way you could pipe the data from one
> yavta instance to another.
>
> This is how I tested m2m devices using yavta; it takes the device file
> handle as a parameter (--fd option) instead of opening it.
That won't help much here as the goal is to share buffers between two video
nodes using dmabuf.
Following our private discussion I think one solution would be to pass buffers
between two yavta instances using unix sockets. Defining a protocol would be
needed. Oh, and implementing it in yavta of course :-)
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-12-22 9:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-13 23:36 [PATCH 0/2] Add VSP1 devices to DT for r8a7790 and r8a7791 Laurent Pinchart
2014-09-30 4:47 ` Cao Minh Hiep
2014-09-30 22:56 ` Laurent Pinchart
2014-10-01 4:35 ` Cao Minh Hiep
2014-12-09 8:54 ` Devendra Talegaonkar
2014-12-15 3:42 ` Devendra Talegaonkar
2014-12-15 23:49 ` Laurent Pinchart
2014-12-16 23:34 ` Laurent Pinchart
2014-12-19 5:05 ` Devendra Talegaonkar
2014-12-20 19:00 ` Laurent Pinchart
2014-12-20 21:46 ` Sakari Ailus
2014-12-22 9:27 ` Laurent Pinchart [this message]
2015-02-04 14:50 ` Laurent Pinchart
2015-02-05 0:28 ` Devendra Talegaonkar
2015-02-09 8:59 ` Laurent Pinchart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1749192.EjGsnkTb20@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-sh@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox