From: Stanimir Varbanov <stanimir.varbanov@linaro.org>
To: Hans Verkuil <hverkuil-cisco@xs4all.nl>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-api@vger.kernel.org
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: [PATCH 3/3] venus: Add a handling of QC10C compressed format
Date: Wed, 2 Jun 2021 16:30:08 +0300 [thread overview]
Message-ID: <f5df5da4-6904-8e9f-0bf0-0c18cde1cc8a@linaro.org> (raw)
In-Reply-To: <37d5e58c-ce5b-07f8-396f-662258a9b229@xs4all.nl>
On 6/2/21 1:01 PM, Hans Verkuil wrote:
> On 29/04/2021 12:58, Stanimir Varbanov wrote:
>> This adds QC10C compressed pixel format in the Venus driver, and
>> make it enumeratable from v4l2 clients.
>
> enumeratable -> possible to discover
>
> (or possibly 'enumerable', but I prefer the phrase suggested above)
>
>>
>> Note: The QC10C format shouldn't be possible to enumerate by the
>> client if the decoded bitstream is not 10bits. This is not
>
> 10bits -> 10-bits
>
>> implemented in this patch yet.
>
> Obvious question: will this be done in a later patch that is being
> prepared? Would it be better to wait until such a patch is available?
>
Yes, It will be implemented in v2.
--
regards,
Stan
prev parent reply other threads:[~2021-06-02 13:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 10:58 [PATCH 0/3] Qualcomm custom compressed pixfmt Stanimir Varbanov
2021-04-29 10:58 ` [PATCH 1/3] v4l: Add Qualcomm custom compressed pixel formats Stanimir Varbanov
2021-04-29 19:10 ` Nicolas Dufresne
2021-05-17 15:13 ` Stanimir Varbanov
2021-06-02 9:56 ` Hans Verkuil
2021-06-02 13:29 ` Stanimir Varbanov
2021-04-29 10:58 ` [PATCH 2/3] venus: Add a handling of QC8C compressed format Stanimir Varbanov
2021-06-02 9:59 ` Hans Verkuil
2021-04-29 10:58 ` [PATCH 3/3] venus: Add a handling of QC10C " Stanimir Varbanov
2021-06-02 10:01 ` Hans Verkuil
2021-06-02 13:30 ` Stanimir Varbanov [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=f5df5da4-6904-8e9f-0bf0-0c18cde1cc8a@linaro.org \
--to=stanimir.varbanov@linaro.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-api@vger.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 \
/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).