From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Kieran Bingham <kieran.bingham@ideasonboard.com>
Cc: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [VSP-Tests PATCH 2/7] tests: Provide copy test to validate 1xN streams
Date: Sun, 17 Feb 2019 04:47:22 +0200 [thread overview]
Message-ID: <20190217024722.GC20463@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20181204155146.9726-3-kieran.bingham@ideasonboard.com>
Hi Kieran,
Thank you for the patch.
On Tue, Dec 04, 2018 at 03:51:41PM +0000, Kieran Bingham wrote:
> Validate that a 1xN stream can be read through the RPF and written
> through the WPF.
>
> The test framework does not currently support processing images where
> the stride does not match the output width - so the testing is currently
> limited to testing only the vertical direction in this aspect.
>
> Signed-off-by: Kieran Bingham <kieran.bingham@ideasonboard.com>
> ---
> tests/vsp-unit-test-0025.sh | 45 +++++++++++++++++++++++++++++++++++++
> 1 file changed, 45 insertions(+)
> create mode 100755 tests/vsp-unit-test-0025.sh
>
> diff --git a/tests/vsp-unit-test-0025.sh b/tests/vsp-unit-test-0025.sh
> new file mode 100755
> index 000000000000..57a1fac6e369
> --- /dev/null
> +++ b/tests/vsp-unit-test-0025.sh
> @@ -0,0 +1,45 @@
> +#!/bin/sh
> +
> +#
> +# Test pipelines which have a single pixel dimension. Use a RPF -> WPF
> +# pipeline with identical input and output formats to generate our output.
> +#
> +
> +. ./vsp-lib.sh
> +
> +features="rpf.0 uds wpf.0"
> +formats="RGB24 ARGB32"
> +
> +# Input is directly copied to the output. No change in format or size.
> +test_copy() {
> + local format=$1
> + local insize=$2
> +
> + test_start "copying $insize in $format"
> +
> + pipe_configure rpf-wpf 0 0
> + format_configure rpf-wpf 0 0 $format $insize $format
> +
> + vsp_runner rpf.0 &
> + vsp_runner wpf.0
> +
> + local result=$(compare_frames)
> +
> + test_complete $result
> +}
> +
> +test_main() {
> + local format
> +
> + for format in $formats ; do
> + test_copy $format 1024x768
> + test_copy $format 128x128
> + test_copy $format 128x1
If the purpose is to test Nx1 and 1xN, do we need the first two
resolutions ? Shouldn't the test_start message describe the exact
purpose ?
> +
> + # Skipped : Test framework does not yet support strides != width
> + #test_copy $format 1x128
> + done
> +}
> +
> +test_init $0 "$features"
> +test_run
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2019-02-17 2:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 15:51 [VSP-Tests PATCH 0/7] Reset controls and unloved patches Kieran Bingham
2018-12-04 15:51 ` [VSP-Tests PATCH 1/7] tests: add pseudo platform test Kieran Bingham
2019-02-17 2:41 ` Laurent Pinchart
2019-02-17 20:41 ` Kieran Bingham
2018-12-04 15:51 ` [VSP-Tests PATCH 2/7] tests: Provide copy test to validate 1xN streams Kieran Bingham
2019-02-17 2:47 ` Laurent Pinchart [this message]
2019-02-17 20:43 ` Kieran Bingham
2018-12-04 15:51 ` [VSP-Tests PATCH 3/7] vsp-lib: Provide command line argument parsing Kieran Bingham
2019-02-17 2:48 ` Laurent Pinchart
2019-02-17 20:47 ` Kieran Bingham
2018-12-04 15:51 ` [VSP-Tests PATCH 4/7] vsp-lib: trivial: Fix spelling of Reference Kieran Bingham
2019-02-17 2:42 ` Laurent Pinchart
2019-02-17 20:48 ` Kieran Bingham
2018-12-04 15:51 ` [VSP-Tests PATCH 5/7] vsp-lib: Allow forcing pixel perfect comparisons Kieran Bingham
2019-02-17 11:59 ` Laurent Pinchart
2019-02-17 20:51 ` Kieran Bingham
2019-02-19 16:35 ` Laurent Pinchart
2018-12-04 15:51 ` [VSP-Tests PATCH 6/7] vsp-lib: Support late queuing of buffers in yavta Kieran Bingham
2019-02-17 12:00 ` Laurent Pinchart
2019-02-17 20:57 ` Kieran Bingham
2019-02-19 16:37 ` Laurent Pinchart
2018-12-04 15:51 ` [VSP-Tests PATCH 7/7] vsp-lib: Reset controls to defaults on each test run Kieran Bingham
2019-02-17 12:01 ` Laurent Pinchart
2019-02-17 21:00 ` Kieran Bingham
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=20190217024722.GC20463@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-renesas-soc@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.