Linux Media Controller development
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil+cisco@kernel.org>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: [GIT PULL FOR v7.3] media: CEC fixes/improvements + doc and vivid fix
Date: Wed, 15 Jul 2026 23:09:56 +0200	[thread overview]
Message-ID: <419c2b65-fd33-4113-8bab-1efddea6f410@kernel.org> (raw)

Hi Mauro,

This PR has one documentation improvement, one fix for vivid, and a bunch of
CEC related fixes and improvements.

Once this PR is merged, I'll also push a separate cec-compliance patch:

https://lore.kernel.org/linux-media/65a6bd5c-4e62-4370-b654-7dce0712aae5@kernel.org/

This uses the vivid CEC emulation and new error injection capability to add
new regression tests.

Regards,

	Hans

The following changes since commit bb03a00d68c147fe7b1fd1a8475c078613c30ec4:

  media: atomisp: Demote all broken kernel-doc comments (2026-07-15 17:12:55 +0200)

are available in the Git repository at:

  git://www.linuxtv.org/hverkuil/media.git tags/br-v7.3k

for you to fetch changes up to eb5fe5bde8cadade023adc03f3645c8da974ad14:

  media: cec/core: add error-inj-tx-timeouts debugfs entry (2026-07-15 23:00:02 +0200)

----------------------------------------------------------------
Tag branch

----------------------------------------------------------------
Hans Verkuil (12):
      Documentation: media: vidioc-g-ext-ctrls: clarify try/set behavior
      media: vivid: always allow meta output streaming
      media: cec: tegra_cec: don't break off msg on NACK
      media: cec: tegra_cec: keep track of number of Rx Low Drives
      media: cec/core: max_retries -> max_attempts
      media: cec/core: drop ABORTED/TIMEOUT check
      media: cec/core: handle core events like normal events
      media: cec/core: drop cec_post_state_event call
      media: cec/core: flush stale STATE_CHANGE events
      media: cec/core: add a new CEC_LOG_ADDRS_FL_CONFIG_FAILED flag
      media: cec/core: cec-pin: toggle rx_toggle when arb lost
      media: cec/core: add error-inj-tx-timeouts debugfs entry

 Documentation/userspace-api/media/cec/cec-ioc-adap-g-log-addrs.rst |  7 +++++
 Documentation/userspace-api/media/v4l/vidioc-g-ext-ctrls.rst       | 15 ++++++----
 drivers/media/cec/core/cec-adap.c                                  | 85 +++++++++++++++++++++++++++++++++-------------------
 drivers/media/cec/core/cec-api.c                                   |  5 ++--
 drivers/media/cec/core/cec-core.c                                  | 31 +++++++++++++++++++
 drivers/media/cec/core/cec-pin.c                                   | 10 ++++++-
 drivers/media/cec/platform/tegra/tegra_cec.c                       | 32 +++++++++++++++++++-
 drivers/media/test-drivers/vivid/vivid-meta-out.c                  | 23 ++++----------
 include/media/cec.h                                                |  6 ++--
 include/uapi/linux/cec.h                                           |  2 ++
 10 files changed, 155 insertions(+), 61 deletions(-)

                 reply	other threads:[~2026-07-15 21:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=419c2b65-fd33-4113-8bab-1efddea6f410@kernel.org \
    --to=hverkuil+cisco@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