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, 15 Dec 2014 23:49:20 +0000 [thread overview]
Message-ID: <3340292.c9zq3U75Jo@avalon> (raw)
In-Reply-To: <1410651385-13090-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
Hi Devendra,
On Monday 15 December 2014 03:42:59 Devendra Talegaonkar wrote:
> Laurent Pinchart writes:
> > On Tuesday 30 September 2014 13:47:32 Cao Minh Hiep wrote:
> > > Hi Laurent,
> > >
> > > We are testing the upstream linux version on Lager.
> > > I have tried to test VSP1 driver on r8a7790(Lager).
> > > But I don't know how to test it.
> > > Could you please tell the method to test it?
> >
> > Sure.
> >
> > I've attached the test script I use to configure the VSP1 pipeline to this
> > e- mail.
> >
> > Syntax: vsp1.sh dev cmd [...]
> >
> > Supported commands:
> > - m2d | m2d-bru | m2d-crop | m2d-scale | m2m | m2m-crop | m2m-scale infmt
> >
> > outfmt
> >
> > - input index infmt
> > - output index outfmt
> >
> > The input and output commands will invoke yavta to capture images from a
> > WPF (output) or stream images to an RPF (input). You can find a tarball
> > with the test frames I use at
> > http://www.ideasonboard.org/frame-reference.tar.bz2, but you can replace
> > them with any binary test image.
>
> Hello,
> I am testing VSP1 on lager board. You have mentioned that by invoking input
> command, file can be streamed to RPF. Does that mean, If we stream the file
> via input command we can seee it on LCD via VSPD0. If my understanding is
> correct can you explain how to test that by setting plane priority? Because
> VSPD0 can out put the data on predefined plane.
> As I am stuck here, awaiting for the earliest response.
The direct connection between the VSPD and the DU isn't supported in the
mainline kernel I'm afraid. I've implemented it in out-of-tree patches, but
they would require extensions to the DRM API that I'm not happy with in their
current form (so I don't expect the DRM developers to be happy either).
I've rebased the patches on a recent kernel, you can find them at
git://linuxtv.org/pinchartl/fbdev.git vsp1/devel
Please note that I haven't had time to test the rebased version yet.
You can find a patched version of the modetest utility at
git://git.ideasonboard.com/renesas/drm.git live
You might need to update the kernel headers, ioctl numbers might have changed
when I've rebased the kernel patches.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-12-15 23:49 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 [this message]
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
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=3340292.c9zq3U75Jo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.