From: Dikshita Agarwal <quic_dikshita@quicinc.com>
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
<linux-media@vger.kernel.org>, <stanimir.k.varbanov@gmail.com>,
<quic_vgarodia@quicinc.com>, <agross@kernel.org>,
<andersson@kernel.org>, <mchehab@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
"Viswanath Boma" <quic_vboma@quicinc.com>
Subject: Re: [PATCH 2/3] venus: enable sufficient sequence change support for vp9
Date: Wed, 5 Apr 2023 11:16:41 +0530 [thread overview]
Message-ID: <ac3faf07-7974-fb26-2d58-0ddc014fce66@quicinc.com> (raw)
In-Reply-To: <8f0404d0-659d-0855-15dd-8a45f6fd1871@linaro.org>
On 4/4/2023 11:52 PM, Konrad Dybcio wrote:
>
> On 4.04.2023 08:17, Dikshita Agarwal wrote:
>> VP9 supports resolution change at interframe.
>> Currenlty, if sequence change is detected at interframe and
>> resources are sufficient, sequence change event is not raised
>> by firmware to driver until the next keyframe.
>> This change add the HFI to notify the sequence change in this
>> case to driver.
>>
>> Signed-off-by: Dikshita Agarwal <quic_dikshita@quicinc.com>
>> Signed-off-by: Vikash Garodia <quic_vgarodia@quicinc.com>
>> Signed-off-by: Viswanath Boma <quic_vboma@quicinc.com>
>> Tested-by: Nathan Hebert <nhebert@chromium.org>
>> ---
>> drivers/media/platform/qcom/venus/hfi_cmds.c | 1 +
>> drivers/media/platform/qcom/venus/hfi_helper.h | 2 ++
>> drivers/media/platform/qcom/venus/vdec.c | 8 ++++++++
>> 3 files changed, 11 insertions(+)
>>
>> diff --git a/drivers/media/platform/qcom/venus/hfi_cmds.c b/drivers/media/platform/qcom/venus/hfi_cmds.c
>> index 930b743..e2539b5 100644
>> --- a/drivers/media/platform/qcom/venus/hfi_cmds.c
>> +++ b/drivers/media/platform/qcom/venus/hfi_cmds.c
>> @@ -521,6 +521,7 @@ static int pkt_session_set_property_1x(struct hfi_session_set_property_pkt *pkt,
>> pkt->shdr.hdr.size += sizeof(u32) + sizeof(*en);
>> break;
>> }
>> + case HFI_PROPERTY_PARAM_VDEC_ENABLE_SUFFICIENT_SEQCHANGE_EVENT:
>> case HFI_PROPERTY_CONFIG_VDEC_POST_LOOP_DEBLOCKER: {
>> struct hfi_enable *in = pdata;
>> struct hfi_enable *en = prop_data;
>> diff --git a/drivers/media/platform/qcom/venus/hfi_helper.h b/drivers/media/platform/qcom/venus/hfi_helper.h
>> index d2d6719..20516b4 100644
>> --- a/drivers/media/platform/qcom/venus/hfi_helper.h
>> +++ b/drivers/media/platform/qcom/venus/hfi_helper.h
>> @@ -469,6 +469,8 @@
>> #define HFI_PROPERTY_PARAM_VDEC_PIXEL_BITDEPTH 0x1003007
>> #define HFI_PROPERTY_PARAM_VDEC_PIC_STRUCT 0x1003009
>> #define HFI_PROPERTY_PARAM_VDEC_COLOUR_SPACE 0x100300a
>> +#define HFI_PROPERTY_PARAM_VDEC_ENABLE_SUFFICIENT_SEQCHANGE_EVENT \
>> + 0x0100300b
>>
>> /*
>> * HFI_PROPERTY_CONFIG_VDEC_COMMON_START
>> diff --git a/drivers/media/platform/qcom/venus/vdec.c b/drivers/media/platform/qcom/venus/vdec.c
>> index 4ceaba3..f0394b9 100644
>> --- a/drivers/media/platform/qcom/venus/vdec.c
>> +++ b/drivers/media/platform/qcom/venus/vdec.c
>> @@ -671,6 +671,14 @@ static int vdec_set_properties(struct venus_inst *inst)
>> return ret;
>> }
>>
>> + /* Enabling sufficient sequence change support for VP9 */
>> + if (is_fw_rev_or_newer(inst->core, 5, 4, 51)) {
>> + ptype = HFI_PROPERTY_PARAM_VDEC_ENABLE_SUFFICIENT_SEQCHANGE_EVENT;
>> + ret = hfi_session_set_property(inst, ptype, &en);
>> + if (ret)
>> + return ret;
>> + }
> Does it never have to be turned off? Or does it happen automatically
> at session closure?
>
> Konrad
Any property set to FW is applied for entire video session and it
doesn't need to change so
there is no need to turn it off or unset it.
Thanks,
Dikshita
>> +
>> ptype = HFI_PROPERTY_PARAM_VDEC_CONCEAL_COLOR;
>> conceal = ctr->conceal_color & 0xffff;
>> conceal |= ((ctr->conceal_color >> 16) & 0xffff) << 10;
next prev parent reply other threads:[~2023-04-05 5:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 6:17 [PATCH 0/3] fix decoder issues with firmware version check Dikshita Agarwal
2023-04-04 6:17 ` [PATCH 1/3] venus: add firmware version based check Dikshita Agarwal
2023-04-04 18:18 ` Konrad Dybcio
2023-04-05 8:20 ` Dikshita Agarwal
2023-04-04 6:17 ` [PATCH 2/3] venus: enable sufficient sequence change support for vp9 Dikshita Agarwal
2023-04-04 18:22 ` Konrad Dybcio
2023-04-05 5:46 ` Dikshita Agarwal [this message]
2023-04-04 19:05 ` Konrad Dybcio
2023-04-05 8:21 ` Dikshita Agarwal
2023-04-04 6:17 ` [PATCH 3/3] venus: fix EOS handling in decoder stop command Dikshita Agarwal
2023-04-04 18:24 ` Konrad Dybcio
2023-04-05 6:41 ` Dikshita Agarwal
2023-04-05 7:19 ` Konrad Dybcio
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=ac3faf07-7974-fb26-2d58-0ddc014fce66@quicinc.com \
--to=quic_dikshita@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=konrad.dybcio@linaro.org \
--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_vboma@quicinc.com \
--cc=quic_vgarodia@quicinc.com \
--cc=stanimir.k.varbanov@gmail.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
all inboxes | Powered by JetHome®