SUPERH platform development
 help / color / mirror / Atom feed
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: Tue, 30 Sep 2014 22:56:56 +0000	[thread overview]
Message-ID: <1734725.HHrFxhR7bF@avalon> (raw)
In-Reply-To: <1410651385-13090-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>

[-- Attachment #1: Type: text/plain, Size: 1996 bytes --]

Hi Cao Minh,

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

"dev" should be the media device name without the /dev/ prefix. For the first 
VSP1 that would thus be "media0".

"cmd" is one of the values listed above. m2d stands for memory to display 
(using out of tree patches for the DRM driver) and m2m stands for memory to 
memory. The *-bru command configures the BRU to blend two inputs, the *-crop 
commands will perform cropping on the input and the -scale commands will 
include the scaler (UDS) in the pipeline.

All the m2d and m2m commands perform pipeline configuration. They take two 
arguments, the input format and the output format. They should both be one of 
BGR24, BGR32, ABGR32, XBGR32, RGB24, RGB32, ARGB32, XRGB32, RGB332, RGB555, 
RGB565, NV12M, NV16M, NV21M, NV61M, UYVY, VYUY, YUV420M, YUYV or YVYU.

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.

The script requires the media-ctl and yavta utilities. The former is now part 
of the v4l-utils project, available at http://git.linuxtv.org/cgit.cgi/v4l-utils.git/. The latter can be found at http://git.ideasonboard.org/yavta.git.

I realize this probably lacks details, so please come back with any question 
you might have and I'll do my best to answer them.

-- 
Regards,

Laurent Pinchart

[-- Attachment #2: vsp1.sh --]
[-- Type: application/x-shellscript, Size: 7283 bytes --]

  parent reply	other threads:[~2014-09-30 22:56 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 [this message]
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
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=1734725.HHrFxhR7bF@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