All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil-cisco@xs4all.nl>
To: linux-media@vger.kernel.org
Cc: Johan Fjeldtvedt <johfjeld@cisco.com>
Subject: [PATCH 0/2] Introduce HDMI Video Guard Band test pattern
Date: Fri, 13 May 2022 14:53:05 +0200	[thread overview]
Message-ID: <20220513125307.3494442-1-hverkuil-cisco@xs4all.nl> (raw)

These patches add support for a specific test pattern to test HDMI
receivers.

Four pixels of the RGB color 0xab55ab are inserted at the left hand side of
the image. This is only done for 3 or 4 byte RGB pixel formats. The HDMI
TMDS encoding of this pixel value equals the Video Guard Band value as
defined by HDMI (see section 5.2.2.1 in the HDMI 1.3 Specification) that
preceeds the first actual pixel of a video line. If an HDMI receiver
doesn't handle this correctly, then it might keep skipping these Video
Guard Band patterns and end up with a shorter video line. So this is a
nice pattern to test with.

And yes, this does cause one receiver we tested with to lose sync :-)

Regards,

	Hans

Hans Verkuil (2):
  media: v4l2-tpg: add HDMI Video Guard Band test pattern
  media: vivid: add HDMI Video Guard Band control

 drivers/media/common/v4l2-tpg/v4l2-tpg-core.c | 38 +++++++++++++++++++
 .../media/test-drivers/vivid/vivid-ctrls.c    | 14 +++++++
 include/media/tpg/v4l2-tpg.h                  | 16 ++++++++
 3 files changed, 68 insertions(+)

-- 
2.34.1


             reply	other threads:[~2022-05-13 12:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-13 12:53 Hans Verkuil [this message]
2022-05-13 12:53 ` [PATCH 1/2] media: v4l2-tpg: add HDMI Video Guard Band test pattern Hans Verkuil
2022-05-13 12:53 ` [PATCH 2/2] media: vivid: add HDMI Video Guard Band control Hans Verkuil
2022-05-23  7:24   ` [PATCH 3/2] media: vivid.rst: document " 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=20220513125307.3494442-1-hverkuil-cisco@xs4all.nl \
    --to=hverkuil-cisco@xs4all.nl \
    --cc=johfjeld@cisco.com \
    --cc=linux-media@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.