From: Hans Verkuil <hverkuil-cisco@xs4all.nl>
To: Dikshita Agarwal <dikshita@codeaurora.org>,
linux-media@vger.kernel.org, stanimir.varbanov@linaro.org
Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
vgarodia@codeaurora.org
Subject: Re: [PATCH v4 0/2] Add base layer priority id control
Date: Wed, 13 Jan 2021 17:44:59 +0100 [thread overview]
Message-ID: <ef05e9fe-355d-43d5-7b14-9ea89cfef907@xs4all.nl> (raw)
In-Reply-To: <1609738914-22769-1-git-send-email-dikshita@codeaurora.org>
Hi Dikshita,
On 04/01/2021 06:41, Dikshita Agarwal wrote:
> This series adds base layer priority id control for encoder
> and support for the same in venus driver.
Posted a pull request for this series and the "Add new controls for QP and
layer bitrate" series.
Note that because the "Add encoder ctrls for long term reference" is not
merged, the control ID for V4L2_CID_MPEG_VIDEO_BASELAYER_PRIORITY_ID changed
and that you need to rebase the "Add encoder ctrls for long term reference"
series accordingly.
Regards,
Hans
>
> Changes since v3:
> - Rebased the changes on latest media tree.
> - Addressed the comments.
> - Added driver side implementation for new control.
>
> Dikshita Agarwal (2):
> media: v4l2-ctrl: Add base layer priority id control.
> venus: venc : Add support for priority ID control.
>
> Documentation/userspace-api/media/v4l/ext-ctrls-codec.rst | 9 +++++++++
> drivers/media/platform/qcom/venus/core.h | 2 ++
> drivers/media/platform/qcom/venus/venc_ctrls.c | 9 ++++++++-
> drivers/media/v4l2-core/v4l2-ctrls.c | 1 +
> include/uapi/linux/v4l2-controls.h | 1 +
> 5 files changed, 21 insertions(+), 1 deletion(-)
>
prev parent reply other threads:[~2021-01-13 16:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 5:41 Dikshita Agarwal
2021-01-04 5:41 ` [PATCH v4 1/2] media: v4l2-ctrl: " Dikshita Agarwal
2021-01-04 5:41 ` [PATCH v4 2/2] venus: venc : Add support for priority ID control Dikshita Agarwal
2021-01-12 9:44 ` Stanimir Varbanov
2021-01-13 16:44 ` Hans Verkuil [this message]
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=ef05e9fe-355d-43d5-7b14-9ea89cfef907@xs4all.nl \
--to=hverkuil-cisco@xs4all.nl \
--cc=dikshita@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=stanimir.varbanov@linaro.org \
--cc=vgarodia@codeaurora.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
all inboxes | Powered by JetHome®