From: Stanimir Varbanov <stanimir.varbanov@linaro.org>
To: Hans Verkuil <hverkuil@xs4all.nl>,
Malathi Gottam <mgottam@codeaurora.org>,
mchehab@kernel.org
Cc: 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 v3] media: venus: amend buffer size for bitstream plane
Date: Mon, 26 Nov 2018 16:57:37 +0200 [thread overview]
Message-ID: <f6106d20-abee-979c-8ac1-6c9115e8373c@linaro.org> (raw)
In-Reply-To: <d74281c8-a177-12a3-9e72-7a7db3014943@xs4all.nl>
Hi Hans,
On 11/26/18 3:37 PM, Hans Verkuil wrote:
> On 11/26/2018 11:12 AM, Malathi Gottam wrote:
>> Accept the buffer size requested by client and compare it
>> against driver calculated size and set the maximum to
>> bitstream plane.
>>
>> Signed-off-by: Malathi Gottam <mgottam@codeaurora.org>
>
> Sorry, this isn't allowed. It is the driver that sets the sizeimage value,
> never the other way around.
I think for decoders (OUTPUT queue) and encoders (CAPTURE queue) we
allowed userspace to set sizeimage for buffers. See [1] Initialization
paragraph point 2:
``sizeimage``
desired size of ``CAPTURE`` buffers; the encoder may adjust it to
match hardware requirements
Similar patch we be needed for decoder as well.
>
> If you need to allocate larger buffers, then use VIDIOC_CREATE_BUFS instead
> of VIDIOC_REQBUFS.
>
> What problem are you trying to solve with this patch?
>
> Regards,
>
> Hans
>
--
regards,
Stan
[1] https://www.spinics.net/lists/linux-media/msg142049.html
next prev parent reply other threads:[~2018-11-26 14:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 10:12 [PATCH v3] media: venus: amend buffer size for bitstream plane Malathi Gottam
2018-11-26 12:53 ` Stanimir Varbanov
2018-11-26 13:37 ` Hans Verkuil
2018-11-26 14:57 ` Stanimir Varbanov [this message]
2018-11-26 15:23 ` Hans Verkuil
2018-11-26 15:44 ` Tomasz Figa
2018-11-26 15:59 ` Hans Verkuil
2018-11-26 16:07 ` Tomasz Figa
2018-11-26 16:41 ` Hans Verkuil
2018-11-27 8:16 ` Alexandre Courbot
2018-11-28 8:41 ` Hans Verkuil
2018-11-27 8:23 ` Tomasz Figa
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=f6106d20-abee-979c-8ac1-6c9115e8373c@linaro.org \
--to=stanimir.varbanov@linaro.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=mgottam@codeaurora.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).