From: mgottam@codeaurora.org
To: Stanimir Varbanov <stanimir.varbanov@linaro.org>
Cc: hverkuil@xs4all.nl, mchehab@kernel.org,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, acourbot@chromium.org,
vgarodia@codeaurora.org
Subject: Re: [PATCH] media: venus: dynamic handling of bitrate
Date: Thu, 01 Nov 2018 18:31:48 +0530 [thread overview]
Message-ID: <3364115421e89c7710725c06b820f8c6@codeaurora.org> (raw)
In-Reply-To: <3ff2c3dd-434d-960b-6806-f4bb8ec0d954@linaro.org>
On 2018-11-01 17:48, Stanimir Varbanov wrote:
> Hi Malathi,
>
> Thanks for the patch!
>
> On 10/31/18 9:42 AM, Malathi Gottam wrote:
>> Any request for a change in bitrate after both planes
>> are streamed on is handled by setting the target bitrate
>> property to hardware.
>>
>> Signed-off-by: Malathi Gottam <mgottam@codeaurora.org>
>> ---
>> drivers/media/platform/qcom/venus/venc_ctrls.c | 11 +++++++++++
>> 1 file changed, 11 insertions(+)
>>
>> diff --git a/drivers/media/platform/qcom/venus/venc_ctrls.c
>> b/drivers/media/platform/qcom/venus/venc_ctrls.c
>> index 45910172..54f310c 100644
>> --- a/drivers/media/platform/qcom/venus/venc_ctrls.c
>> +++ b/drivers/media/platform/qcom/venus/venc_ctrls.c
>> @@ -79,7 +79,9 @@ static int venc_op_s_ctrl(struct v4l2_ctrl *ctrl)
>> {
>> struct venus_inst *inst = ctrl_to_inst(ctrl);
>> struct venc_controls *ctr = &inst->controls.enc;
>> + struct hfi_bitrate brate;
>> u32 bframes;
>> + u32 ptype;
>> int ret;
>>
>> switch (ctrl->id) {
>> @@ -88,6 +90,15 @@ static int venc_op_s_ctrl(struct v4l2_ctrl *ctrl)
>> break;
>> case V4L2_CID_MPEG_VIDEO_BITRATE:
>> ctr->bitrate = ctrl->val;
>> + if (inst->streamon_out && inst->streamon_cap) {
>
> Hmm, hfi_session_set_property already checks the instance state so I
> don't think those checks are needed. Another thing is that we need to
> take the instance mutex to check the instance state.
Yes Stan, "hfi_session_set_property" this property check the instance
state,
but returns EINVAL if this is set at UNINIT instance state.
Controls initialization happens much earlier than session init and
instance init.
So the instance is still in UNINIT state which causes failure while
setting.
Through this patch we try to meet the client request of changing bitrate
only
when both planes are streamed on.
We have two ways to handle it
1. The way in this patch checks the planes state which will definitely
ensure
instance is in START state.
2. Have a check to ensure that instance is atleast Initialized.
I hope the first proposal is good enough for meeting requirement.
>
>> + ptype = HFI_PROPERTY_CONFIG_VENC_TARGET_BITRATE;
>> + brate.bitrate = ctr->bitrate;
>> + brate.layer_id = 0;
>> +
>> + ret = hfi_session_set_property(inst, ptype, &brate);
>> + if (ret)
>> + return ret;
>> + }
>> break;
>> case V4L2_CID_MPEG_VIDEO_BITRATE_PEAK:
>> ctr->bitrate_peak = ctrl->val;
>>
next prev parent reply other threads:[~2018-11-01 13:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 7:42 [PATCH] media: venus: dynamic handling of bitrate Malathi Gottam
2018-11-01 12:18 ` Stanimir Varbanov
2018-11-01 13:01 ` mgottam [this message]
2018-11-01 13:53 ` Tomasz Figa
2018-11-01 14:23 ` Vikash Garodia
2018-11-01 14:31 ` Tomasz Figa
2018-11-01 15:03 ` Stanimir Varbanov
2018-11-02 12:33 ` mgottam
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=3364115421e89c7710725c06b820f8c6@codeaurora.org \
--to=mgottam@codeaurora.org \
--cc=acourbot@chromium.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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 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.