From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Dikshita Agarwal <quic_dikshita@quicinc.com>,
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 3/3] venus: fix EOS handling in decoder stop command
Date: Wed, 5 Apr 2023 09:19:40 +0200 [thread overview]
Message-ID: <514ed648-2d5e-c18d-e5ff-828f6b9a8345@linaro.org> (raw)
In-Reply-To: <62cc41a2-ff48-40b9-eb89-69e352e6f6e9@quicinc.com>
On 5.04.2023 08:41, Dikshita Agarwal wrote:
>
> On 4/4/2023 11:54 PM, Konrad Dybcio wrote:
>>
>> On 4.04.2023 08:17, Dikshita Agarwal wrote:
>>> Use firmware version based check to assign correct
>>> device address for EOS buffer to fix the EOS handling
>>> with different firmware version.
>>>
>>> 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>
>>> ---
>> Does it only concern fw 1.0.xx?
>>
>> Konrad
>
> that's right.
>
> changes were made in later firmware (newer than 1.0.87) to
>
> make the behavior generic across all supported SOCs.
>
> Thanks,
OK
Reviewed-by: Konrad Dybcio <konrad.dybcio@linaro.org>
Konrad
>
> Dikshita
>
>>> drivers/media/platform/qcom/venus/vdec.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/media/platform/qcom/venus/vdec.c b/drivers/media/platform/qcom/venus/vdec.c
>>> index f0394b9..c59b34f 100644
>>> --- a/drivers/media/platform/qcom/venus/vdec.c
>>> +++ b/drivers/media/platform/qcom/venus/vdec.c
>>> @@ -545,7 +545,7 @@ vdec_decoder_cmd(struct file *file, void *fh, struct v4l2_decoder_cmd *cmd)
>>> fdata.buffer_type = HFI_BUFFER_INPUT;
>>> fdata.flags |= HFI_BUFFERFLAG_EOS;
>>> - if (IS_V6(inst->core))
>>> + if (IS_V6(inst->core) && is_fw_rev_or_older(inst->core, 1, 0, 87))
>>> fdata.device_addr = 0;
>>> else
>>> fdata.device_addr = 0xdeadb000;
prev parent reply other threads:[~2023-04-05 7:19 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
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 [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=514ed648-2d5e-c18d-e5ff-828f6b9a8345@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.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_dikshita@quicinc.com \
--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®