From: Kieran Bingham <kbingham@kernel.org>
To: linux-renesas-soc@vger.kernel.org,
laurent.pinchart@ideasonboard.com,
kieran.bingham@ideasonboard.com
Cc: Kieran Bingham <kieran@ksquared.org.uk>
Subject: [RFC PATCH 0/3] [RFC] Video HDMI Loop-back Test
Date: Thu, 14 Dec 2017 00:25:06 +0000 [thread overview]
Message-ID: <cover.417c1b91fc9842fb290756d5ad23bdc16970b1e1.1513211056.git-series.kieran@bingham.xyz> (raw)
From: Kieran Bingham <kieran@bingham.xyz>
This short series works towards providing automated system validation by
introducing the ability to capture frames using the R-Car VIN device with an
HDMI cable connected to our HDMI output of the DU.
To support this test, relevant patches and support must be provided by kmsxx
which has been posted separately [0]:
[PATCH 0/4] kms++util: Provide validation helpers
This series provides an rcar_vin module to assist in detecting and identifying
the correct video device to use for the video capture device.
The rcar_vin module provides a lot of code which is not used specifically by
the following kms-test-vin-loopback test but is kept in the module as an RFC
and to stimulate discussion on implementing convenient helpers to wrap our
R-Car interfaces in python modules, especially as so much platform knowledge is
required to set up a capture.
Finally the VIN loopback test is added which uses two pre-filled display
buffers to simulate an active running display but with constant content.
The display output is then captured by setting up a VideoDevice interface and
registering a handler (handle_frame_capture) to process buffers when the are
presented by the VIN driver.
The captured frames are compared against the constant output buffer - and
written to file in the event that there are any differences to allow for visual
inspection and analysis.
This test currently highlights potential colour space conversion issues in YUYV
pipelines, and a non-determined error in ARGB configured pipelines which will
be investigated separately.
Further future possibilities here:
- Automatically configure the media device and links with a media-ctl abstraction
- Add meta-data into the output frames so that they can be correctly matched
against incoming captured frames. (I'm thinking adding a QR code to each frame)
--
Regards
Kieran
[0] https://www.mail-archive.com/linux-renesas-soc@vger.kernel.org/msg21303.html
Kieran Bingham (3):
kms-tests: Provide .gitignore
rcar_vin: Provide VIN configuration helpers
tests: Add a DU->VIN loopback test
.gitignore | 4 +-
tests/kms-test-vin-loopback.py | 198 ++++++++++++++++++++++++++++++++++-
tests/rcar_vin.py | 107 ++++++++++++++++++-
3 files changed, 309 insertions(+)
create mode 100644 .gitignore
create mode 100755 tests/kms-test-vin-loopback.py
create mode 100755 tests/rcar_vin.py
base-commit: 724e38e6c5f511030d7cbdcd40ccc3d0f8749981
--
git-series 0.9.1
next reply other threads:[~2017-12-14 0:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 0:25 Kieran Bingham [this message]
2017-12-14 0:25 ` [RFC PATCH 1/3] kms-tests: Provide .gitignore Kieran Bingham
2017-12-14 0:28 ` Kieran Bingham
2017-12-14 0:25 ` [RFC PATCH 2/3] rcar_vin: Provide VIN configuration helpers Kieran Bingham
2017-12-14 0:25 ` [RFC PATCH 3/3] tests: Add a DU->VIN loopback test 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=cover.417c1b91fc9842fb290756d5ad23bdc16970b1e1.1513211056.git-series.kieran@bingham.xyz \
--to=kbingham@kernel.org \
--cc=kieran.bingham@ideasonboard.com \
--cc=kieran@ksquared.org.uk \
--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 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.