All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil+cisco@kernel.org>
To: linux-media@vger.kernel.org
Cc: Maxime Ripard <mripard@kernel.org>,
	Dave Stevenson <dave.stevenson@raspberrypi.com>
Subject: [PATCHv2 0/2] media: tc358743: add support for more IF/Packet types
Date: Tue, 22 Jul 2025 09:34:34 +0200	[thread overview]
Message-ID: <cover.1753169676.git.hverkuil+cisco@kernel.org> (raw)

The tc358743 HDMI-to-CSI2 bridge is widely available, and it has quite
flexible InfoFrame/Packet Type support, so this makes it a very nice
device to capture such data.

This patch series adds support for SPD, AUDIO, DRM and HDMI InfoFrames.

Also add support for ISRC1 and ISRC2 Packet Types and a programmable
type for both Packet and InfoFrames, which by default is programmed
for DRM InfoFrames.

These changes make the tc358743 very useful when you want to see
what InfoFrames and Packet Types are being transmitted.

Regards,

	Hans

Changes since v1:

- Added Packet Type support (ISRC1, ISRC2) and DRM and MPEG
  InfoFrame support.
- Added programmable Packet Type (defaults to DRM).

Hans Verkuil (2):
  media: v4l2-core: v4l2-dv-timings: support DRM IFs
  media: i2c: tc358743: add support for more infoframe types

 drivers/media/i2c/tc358743.c              | 109 +++++++++++++++++++---
 drivers/media/i2c/tc358743_regs.h         |  57 +++++++----
 drivers/media/v4l2-core/v4l2-dv-timings.c |   4 +
 include/media/v4l2-dv-timings.h           |   1 +
 4 files changed, 140 insertions(+), 31 deletions(-)

-- 
2.47.2


             reply	other threads:[~2025-07-22  7:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-22  7:34 Hans Verkuil [this message]
2025-07-22  7:34 ` [PATCHv2 1/2] media: v4l2-core: v4l2-dv-timings: support DRM IFs Hans Verkuil
2025-07-22  7:34 ` [PATCHv2 2/2] media: i2c: tc358743: add support for more infoframe types 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=cover.1753169676.git.hverkuil+cisco@kernel.org \
    --to=hverkuil+cisco@kernel.org \
    --cc=dave.stevenson@raspberrypi.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mripard@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.