public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: bod@kernel.org
To: bod@kernel.org, linux-media@vger.kernel.org, hans@jjverkuil.nl
Cc: bryan.odonoghue@linaro.org
Subject: [GIT PULL FOR 6.20] Please pull platform-qcom-iris-6.20-fixes
Date: Tue, 20 Jan 2026 12:59:18 +0000	[thread overview]
Message-ID: <20260120125929.4795-1-bod@kernel.org> (raw)

From: Bryan O'Donoghue <bod@kernel.org>

The following changes since commit eb4ee870747c3a77a9c3c84d84efb64bd481013a:

  Documentation: admin-guide: media: mgb4: Add GMSL1 & GMSL3-coax modules info (2026-01-17 09:08:02 +0100)

are available in the Git repository at:

  https://gitlab.freedesktop.org/linux-media/users/bodonoghue.git tags/platform-qcom-iris-6.20-fixes

for you to fetch changes up to 4a2207a3736d0dc78ac2f16325189b307964a2cb:

  media: iris: Prevent output buffer queuing before stream-on completes (2026-01-19 09:50:34 +0000)

----------------------------------------------------------------
There are eleven fixes in this cycle including

- A revert for a commit which caused buffer leaks - Dikshita Agarwal
- A buffer flag fix host -> firmware - Vishnu Reddy
- FPS calculation bug found by cocci - Ricardo Ribalda
- Fallback frame size fix - Val Packett
- A fix to negate freeing a potentially in-use buffer - Dikshita Agarwal
- Add in missing platform data fields sm8750 - Dikshita Agarwal
- A Potential leak fix - Dikshita Agarwal
- Skip setting resolution doing reconfig - Dikshita Agarwal
- Iris/gen1 another buffer leak fixed - Dikshita Agarwal
- Fix a NULL pointer deference during stop_streaming - Dikshita Agarwal
- Stop firmware processing buffers too early - Dikshita Agarwal

----------------------------------------------------------------
Dikshita Agarwal (7):
      Revert "media: iris: Add sanity check for stop streaming"
      media: iris: remove v4l2_m2m_ioctl_{de,en}coder_cmd API usage during STOP handling
      media: iris: Add missing platform data entries for SM8750
      media: iris: Add buffer to list only after successful allocation
      media: iris: Skip resolution set on first IPSC
      media: iris: gen1: Destroy internal buffers after FW releases
      media: iris: gen2: Add sanity check for session stop

Ricardo Ribalda (1):
      media: iris: Fix fps calculation

Val Packett (1):
      media: iris: use fallback size when S_FMT is called without width/height

Vishnu Reddy (2):
      media: iris: Fix ffmpeg corrupted frame error
      media: iris: Prevent output buffer queuing before stream-on completes

 drivers/media/platform/qcom/iris/iris_buffer.c         |  7 +++++--
 .../media/platform/qcom/iris/iris_hfi_gen1_command.c   |  6 ++++--
 .../media/platform/qcom/iris/iris_hfi_gen2_command.c   |  3 +++
 drivers/media/platform/qcom/iris/iris_platform_gen2.c  |  2 ++
 drivers/media/platform/qcom/iris/iris_vb2.c            | 18 ++++++++++--------
 drivers/media/platform/qcom/iris/iris_vdec.c           |  8 ++++++++
 drivers/media/platform/qcom/iris/iris_venc.c           | 15 +++++----------
 drivers/media/platform/qcom/iris/iris_vidc.c           | 10 ++++++----
 8 files changed, 43 insertions(+), 26 deletions(-)

                 reply	other threads:[~2026-01-20 12:59 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=20260120125929.4795-1-bod@kernel.org \
    --to=bod@kernel.org \
    --cc=bryan.odonoghue@linaro.org \
    --cc=hans@jjverkuil.nl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox