From: Alexandre Courbot <acourbot@chromium.org>
To: Stanimir Varbanov <stanimir.varbanov@linaro.org>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@xs4all.nl>,
LKML <linux-kernel@vger.kernel.org>,
linux-arm-msm@vger.kernel.org,
Vikash Garodia <vgarodia@codeaurora.org>,
Tomasz Figa <tfiga@chromium.org>,
Malathi Gottam <mgottam@codeaurora.org>
Subject: Re: [PATCH 4/4] venus: helpers: drop setting of timestap invalid flag
Date: Wed, 23 Jan 2019 15:09:53 +0900 [thread overview]
Message-ID: <CAPBb6MWmeV2eUpk5HKOO1HVZ-eszehKfBW49+p4r-eSN1HuY0w@mail.gmail.com> (raw)
In-Reply-To: <20190109084616.17162-5-stanimir.varbanov@linaro.org>
On Wed, Jan 9, 2019 at 5:46 PM Stanimir Varbanov
<stanimir.varbanov@linaro.org> wrote:
>
> The zero timestap is really a valid so not sure why I discarded it. Fix
s/timestap/timestamp, also in patch title.
> that mistake by drop the code which checks for zero timestamp.
s/drop/dropping
>
> Signed-off-by: Stanimir Varbanov <stanimir.varbanov@linaro.org>
> ---
> drivers/media/platform/qcom/venus/helpers.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/drivers/media/platform/qcom/venus/helpers.c b/drivers/media/platform/qcom/venus/helpers.c
> index e436385bc5ab..5cad601d4c57 100644
> --- a/drivers/media/platform/qcom/venus/helpers.c
> +++ b/drivers/media/platform/qcom/venus/helpers.c
> @@ -439,9 +439,6 @@ session_process_buf(struct venus_inst *inst, struct vb2_v4l2_buffer *vbuf)
> fdata.flags = 0;
> fdata.clnt_data = vbuf->vb2_buf.index;
>
> - if (!fdata.timestamp)
> - fdata.flags |= HFI_BUFFERFLAG_TIMESTAMPINVALID;
> -
> if (type == V4L2_BUF_TYPE_VIDEO_OUTPUT_MPLANE) {
> fdata.buffer_type = HFI_BUFFER_INPUT;
> fdata.filled_len = vb2_get_plane_payload(vb, 0);
> --
> 2.17.1
>
prev parent reply other threads:[~2019-01-23 6:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 8:46 [PATCH 0/4] Venus various fixes Stanimir Varbanov
2019-01-09 8:46 ` [PATCH 1/4] venus: firmware: check fw size against DT memory region size Stanimir Varbanov
2019-01-18 16:20 ` Stanimir Varbanov
2019-01-23 6:10 ` Alexandre Courbot
2019-01-23 10:05 ` Stanimir Varbanov
2019-01-09 8:46 ` [PATCH 2/4] venus: core: corect maximum hardware load for sdm845 Stanimir Varbanov
2019-01-23 6:09 ` Alexandre Courbot
2019-01-09 8:46 ` [PATCH 3/4] venus: core: correct frequency table " Stanimir Varbanov
2019-01-09 8:46 ` [PATCH 4/4] venus: helpers: drop setting of timestap invalid flag Stanimir Varbanov
2019-01-23 6:09 ` Alexandre Courbot [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=CAPBb6MWmeV2eUpk5HKOO1HVZ-eszehKfBW49+p4r-eSN1HuY0w@mail.gmail.com \
--to=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=mgottam@codeaurora.org \
--cc=stanimir.varbanov@linaro.org \
--cc=tfiga@chromium.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;
as well as URLs for NNTP newsgroup(s).