From: Stanimir Varbanov <stanimir.varbanov@linaro.org>
To: Hans Verkuil <hverkuil@xs4all.nl>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Andy Gross <andy.gross@linaro.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Stephen Boyd <sboyd@codeaurora.org>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 0/8] Qualcomm video decoder/encoder driver
Date: Wed, 7 Sep 2016 11:57:19 +0300 [thread overview]
Message-ID: <8c79f249-ade9-59db-7bef-d46e8b1fc936@linaro.org> (raw)
In-Reply-To: <51878905-ca77-b972-f374-9bf2b4be9204@xs4all.nl>
Hi Hans,
On 09/05/2016 05:47 PM, Hans Verkuil wrote:
> On 08/22/2016 03:13 PM, Stanimir Varbanov wrote:
>> This patchset introduces a basic support for Qualcomm video
>> acceleration hardware used for video stream decoding/encoding.
>> The video IP can found on various qcom SoCs like apq8084, msm8916
>> and msm8996, hence it is widly distributed but the driver is
>> missing in the mainline.
>>
>> The v4l2 driver is something like a wrapper over Host Firmware
>> Interface. The HFI itself is a set of command and message packets
>> send/received through shared memory, and its purpose is to
>> comunicate with the firmware which is run on remote processor.
>> The Venus is the name of the video hardware IP that doing the
>> video acceleration.
>>
>> From the software point of view the HFI interface is implemented
>> in the files with prefix hfi_xxx. It acts as a translation layer
>> between HFI and v4l2 layer. There is one special file in the
>> driver called hfi_venus which doing most of the driver
>> orchestration work. Something more it setups Venus core, run it
>> and handle commands and messages from low-level point of view with
>> the help of provided functions by HFI interface.
>>
>> I think that the driver is in good shape for mainline kernel, and
>> I hope the review comments will help to improve it, so please
>> do review and make comments.
>
> I was hoping that I could finish reviewing this patch series today,
> but that didn't work out.
>
> I have more time next week, but I wonder if it isn't better if you make a
> v2 first, taking my comments into account. Then I can review v2 next week.
OK, I have more of your comments addressed plus few of Bjorn's too.
>
> Also test with the latest v4l2-compliance (i.e. as of today) since I improved
> a few tests relating to g/s_selection and g/s_parm.
Sure, I will retest and post the results in cover letter.
--
regards,
Stan
prev parent reply other threads:[~2016-09-07 8:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 13:13 [PATCH 0/8] Qualcomm video decoder/encoder driver Stanimir Varbanov
2016-08-22 13:13 ` [PATCH 1/8] doc: DT: vidc: binding document for Qualcomm video driver Stanimir Varbanov
2016-08-22 13:13 ` [PATCH 2/8] media: vidc: adding core part and helper functions Stanimir Varbanov
2016-08-22 13:41 ` Hans Verkuil
2016-08-22 16:03 ` Stanimir Varbanov
2016-08-23 2:50 ` Bjorn Andersson
2016-08-25 12:59 ` Stanimir Varbanov
2016-08-25 18:26 ` Bjorn Andersson
2016-08-22 13:13 ` [PATCH 3/8] media: vidc: decoder: add video decoder files Stanimir Varbanov
2016-08-22 14:38 ` Hans Verkuil
2016-08-23 12:45 ` Stanimir Varbanov
2016-08-23 13:12 ` Hans Verkuil
2016-08-29 14:22 ` Stanimir Varbanov
2016-08-22 13:13 ` [PATCH 4/8] media: vidc: encoder: add video encoder files Stanimir Varbanov
2016-08-22 13:13 ` [PATCH 5/8] media: vidc: add Host Firmware Interface (HFI) Stanimir Varbanov
2016-08-23 3:25 ` Bjorn Andersson
2016-08-26 14:21 ` Stanimir Varbanov
2016-08-22 13:13 ` [PATCH 6/8] media: vidc: add Venus HFI files Stanimir Varbanov
2016-08-23 3:35 ` Bjorn Andersson
2016-08-22 13:13 ` [PATCH 7/8] media: vidc: add Makefiles and Kconfig files Stanimir Varbanov
2016-08-22 13:13 ` [PATCH 8/8] media: vidc: enable building of the video codec driver Stanimir Varbanov
2016-09-05 14:47 ` [PATCH 0/8] Qualcomm video decoder/encoder driver Hans Verkuil
2016-09-07 8:57 ` 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=8c79f249-ade9-59db-7bef-d46e8b1fc936@linaro.org \
--to=stanimir.varbanov@linaro.org \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.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=sboyd@codeaurora.org \
--cc=srinivas.kandagatla@linaro.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).