linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@gmail.com>
To: Kieran Bingham <kieran.bingham@ideasonboard.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 3/3] tests: unbind/bind: Only test non display VSPs
Date: Sat, 19 Sep 2020 11:38:24 +0300	[thread overview]
Message-ID: <f7c4fe78-359d-0a06-4850-1ccafdc31966@gmail.com> (raw)
In-Reply-To: <20200918202616.55977-4-kieran.bingham@ideasonboard.com>

Hello!

On 18.09.2020 23:26, Kieran Bingham wrote:

> Only perform bind/unbind testing on VSPs which expose a media-device.
> Unbinding a VSP which is connected to a DU causes the display pipeline
> to fail, and is not currently supported.
> 
> Signed-off-by: Kieran Bingham <kieran.bingham@ideasonboard.com>
> ---
>   tests/vsp-unit-test-0026.sh | 11 +++++++++--
>   1 file changed, 9 insertions(+), 2 deletions(-)
> 
> diff --git a/tests/vsp-unit-test-0026.sh b/tests/vsp-unit-test-0026.sh
> index 88038f3fdebf..4185bb23d05b 100755
> --- a/tests/vsp-unit-test-0026.sh
> +++ b/tests/vsp-unit-test-0026.sh
> @@ -10,7 +10,14 @@
>   features="rpf.0 wpf.0"
>   
>   vsp1_driver=/sys/bus/platform/drivers/vsp1
> -vsps=$(cd /sys/bus/platform/devices/; ls | grep vsp)
> +
> +# List all VSPs with a media device.
> +# This exludes VSP devices used by the DU.

    Excludes. :-)

[...]

MBR, Sergei

      reply	other threads:[~2020-09-19  8:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-18 20:26 [PATCH 0/3] VSP-Tests: unbind: Kieran Bingham
2020-09-18 20:26 ` [PATCH 1/3] scripts: vsp-lib.sh: Remove unused variable Kieran Bingham
2020-09-18 20:26 ` [PATCH 2/3] tests: Skip unbind/bind tests when not root Kieran Bingham
2020-09-18 20:45   ` Kieran Bingham
2020-09-18 20:52   ` [PATCH v2] " Kieran Bingham
2020-09-18 20:26 ` [PATCH 3/3] tests: unbind/bind: Only test non display VSPs Kieran Bingham
2020-09-19  8:38   ` Sergei Shtylyov [this message]

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=f7c4fe78-359d-0a06-4850-1ccafdc31966@gmail.com \
    --to=sergei.shtylyov@gmail.com \
    --cc=kieran.bingham@ideasonboard.com \
    --cc=laurent.pinchart@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).