From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Viswanath Boma <quic_vboma@quicinc.com>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, quic_vgarodia@quicinc.com,
quic_dikshita@quicinc.com
Cc: stanimir.k.varbanov@gmail.com,
Vikash Garodia <vgarodia@qti.qualcomm.com>
Subject: Re: [PATCH v4] venus: Enable sufficient sequence change support for sc7180 and fix for Decoder STOP command issue.
Date: Wed, 29 Mar 2023 01:20:46 +0300 [thread overview]
Message-ID: <d3077a68-cdf4-6304-111e-1c262695a065@linaro.org> (raw)
In-Reply-To: <20230323130153.8229-1-quic_vboma@quicinc.com>
On 23/03/2023 15:01, Viswanath Boma wrote:
> For VP9 bitstreams, there could be a change in resolution at interframe,
> for driver to get notified of such resolution change,
> enable the property in video firmware.
> Also, EOS handling is now made same in video firmware across all V6 SOCs,
> hence above a certain firmware version, the driver handling is
> made generic for all V6s
>
> Signed-off-by: Vikash Garodia <vgarodia@qti.qualcomm.com>
> Signed-off-by: Viswanath Boma <quic_vboma@quicinc.com>
> Tested-by: Nathan Hebert <nhebert@chromium.org>
> ---
> Since v3 : Addressed comments to rectify email address.
This is not true. Your to and cc lists are still incorrect.
--
With best wishes
Dmitry
prev parent reply other threads:[~2023-03-28 22:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 13:01 Viswanath Boma
2023-03-28 22:19 ` Dmitry Baryshkov
2023-03-29 7:48 ` Vikash Garodia
2023-03-29 13:36 ` Dmitry Baryshkov
2023-03-29 17:15 ` Vikash Garodia
2023-03-29 17:33 ` Dmitry Baryshkov
2023-03-30 4:34 ` Vikash Garodia
2023-03-28 22:20 ` Dmitry Baryshkov [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=d3077a68-cdf4-6304-111e-1c262695a065@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@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_dikshita@quicinc.com \
--cc=quic_vboma@quicinc.com \
--cc=quic_vgarodia@quicinc.com \
--cc=stanimir.k.varbanov@gmail.com \
--cc=vgarodia@qti.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
all inboxes | Powered by JetHome®