Linux Media Controller development
 help / color / mirror / Atom feed
From: Bryan O'Donoghue <bod@kernel.org>
To: Wangao Wang <wangao.wang@oss.qualcomm.com>,
	Vikash Garodia <vikash.garodia@oss.qualcomm.com>,
	Dikshita Agarwal <dikshita.agarwal@oss.qualcomm.com>,
	Abhinav Kumar <abhinav.kumar@linux.dev>,
	Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: quic_qiweil@quicinc.com,
	Renjiang Han <renjiang.han@oss.qualcomm.com>,
	linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] media: qcom: iris: Add request key frame support for encoder
Date: Tue, 30 Jun 2026 23:12:59 +0100	[thread overview]
Message-ID: <eaac41c0-94e6-4f7c-acaa-7270ce48e396@kernel.org> (raw)
In-Reply-To: <20260624-dynamic_encode-v3-2-f2a2db0ac2af@oss.qualcomm.com>

On 24/06/2026 09:51, Wangao Wang wrote:
> Add request key frame support for both gen1 and gen2 encoders by enabling
> 
> V4L2_CID_MPEG_VIDEO_FORCE_KEY_FRAME.
> 
> Signed-off-by: Wangao Wang<wangao.wang@oss.qualcomm.com>

Reviewed-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>

---
bod

  parent reply	other threads:[~2026-06-30 22:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Z3W2-J864HyF-sbnVW8bg7mP4rdQ-AGsEM_jIIXZEEzjrC0E2wQSfGS3CXZItedQtyxy_aMWtLQmg-iyFEcHpA==@protonmail.internalid>
2026-06-24  8:51 ` [PATCH v3 0/2] media: qcom: iris: add dynamic encoder properties Wangao Wang
2026-06-24  8:51   ` [PATCH v3 1/2] media: qcom: iris: improve gop size support for gen1 encoder Wangao Wang
2026-06-30 15:06     ` Vishnu Reddy
2026-06-30 22:10     ` Bryan O'Donoghue
2026-06-24  8:51   ` [PATCH v3 2/2] media: qcom: iris: Add request key frame support for encoder Wangao Wang
2026-06-30 15:10     ` Vishnu Reddy
2026-06-30 22:12     ` Bryan O'Donoghue [this message]
2026-06-30 22:07   ` [PATCH v3 0/2] media: qcom: iris: add dynamic encoder properties Bryan O'Donoghue

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=eaac41c0-94e6-4f7c-acaa-7270ce48e396@kernel.org \
    --to=bod@kernel.org \
    --cc=abhinav.kumar@linux.dev \
    --cc=dikshita.agarwal@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=quic_qiweil@quicinc.com \
    --cc=renjiang.han@oss.qualcomm.com \
    --cc=vikash.garodia@oss.qualcomm.com \
    --cc=wangao.wang@oss.qualcomm.com \
    /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