From: "Daniel W. S. Almeida" <dwlsalmeida@gmail.com>
To: mchehab@kernel.org, hverkuil@xs4all.nl
Cc: "Daniel W. S. Almeida" <dwlsalmeida@gmail.com>,
linux-media@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v4l-utils] test-media: add support for vidtv
Date: Tue, 5 Jan 2021 10:17:25 -0300 [thread overview]
Message-ID: <20210105131725.1191046-1-dwlsalmeida@gmail.com> (raw)
From: "Daniel W. S. Almeida" <dwlsalmeida@gmail.com>
Add support for vidtv at the test-media script so that automated testing
is possible. Proper compliance tests are still pending.
Signed-off-by: Daniel W. S. Almeida <dwlsalmeida@gmail.com>
---
contrib/test/test-media | 72 +++++++++++++++++++++++++++++++++++++++++
1 file changed, 72 insertions(+)
diff --git a/contrib/test/test-media b/contrib/test/test-media
index 1c1d2e37b..86a2e081a 100755
--- a/contrib/test/test-media
+++ b/contrib/test/test-media
@@ -4,6 +4,7 @@
#
# Copyright 2019 Cisco Systems, Inc. and/or its affiliates. All rights reserved.
+vidtv=0
vivid=0
vim2m=0
vimc=0
@@ -51,6 +52,7 @@ if [ -z "$1" ]; then
echo "-32: use v4l2-ctl-32 and v4l2-compliance-32 to test the 32 bit compat layer"
echo
echo Test Targets:
+ echo "vidtv: test the vidtv driver"
echo "vivid: test the vivid driver"
echo "vim2m: test the vim2m driver"
echo "vimc: test the vimc driver"
@@ -96,6 +98,7 @@ while [ ! -z "$1" ]; do
fi
;;
all)
+ vidtv=1
vivid=1
vim2m=1
vimc=1
@@ -109,6 +112,9 @@ while [ ! -z "$1" ]; do
vimc=1
vicodec=1
;;
+ vidtv)
+ vidtv=1
+ ;;
vivid)
vivid=1
;;
@@ -162,6 +168,72 @@ $v4l2_ctl -z platform:vivid-002 -d vivid-002-vid-out -o1 -x width=3840,height=21
echo
+if [ $vidtv -eq 1 ]; then
+ rmmod vidtv 2&>/dev/null
+ modprobe vidtv
+ sleep 2
+ dmesg -n notice
+ echo
+
+ if ! media-ctl -d platform:vidtv -p ; then
+ echo "FAIL: the vidtv module failed to load" | tee -a $tmp
+ echo "Grand Total for vidtv: Succeeded: 0, Failed: 1, Warnings: 0" | tee -a $tmp
+ echo "Final Summary: 1, Succeeded: 0, Failed: 1, Warnings: 0"
+ rmmod vidtv
+ exit 0
+ fi
+
+ echo
+ echo
+ echo
+ echo
+ echo
+ echo
+ echo
+ echo
+ echo
+ echo unbind vidtv
+ echo
+ echo -n vidtv.0 >/sys/bus/platform/drivers/vidtv/unbind
+ sleep $unbind_time
+ echo
+ echo rebind vidtv
+ echo
+ echo -n vidtv.0 >/sys/bus/platform/drivers/vidtv/bind
+ sleep 1
+ echo
+ echo second unbind vidtv
+ echo
+ sleep 1
+ echo
+ echo -n vidtv.0 >/sys/bus/platform/drivers/vidtv/unbind
+ sleep $reunbind_time
+ echo
+ echo rmmod vidtv
+ echo
+ rmmod vidtv
+ sleep $rmmod_time
+ if [ $kmemleak -eq 1 ]; then
+ echo
+ echo kmemleak results for vidtv:
+ echo
+ echo scan >/sys/kernel/debug/kmemleak
+ cat /sys/kernel/debug/kmemleak
+ echo
+ echo end of kmemleak results
+ echo clear >/sys/kernel/debug/kmemleak
+ fi
+ echo
+ echo
+ echo
+ echo
+ echo
+ echo
+ echo
+ echo
+
+fi
+
if [ $vivid -eq 1 ]; then
dmesg -n notice
echo
--
2.30.0
next reply other threads:[~2021-01-05 13:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 13:17 Daniel W. S. Almeida [this message]
2021-01-28 14:36 ` Hans Verkuil
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=20210105131725.1191046-1-dwlsalmeida@gmail.com \
--to=dwlsalmeida@gmail.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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
all inboxes | Powered by JetHome®