linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanimir Varbanov <svarbanov@mm-sol.com>
To: Hans Verkuil <hverkuil@xs4all.nl>,
	Tiffany Lin <tiffany.lin@mediatek.com>,
	Hans Verkuil <hans.verkuil@cisco.com>,
	daniel.thompson@linaro.org, Rob Herring <robh+dt@kernel.org>,
	Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Daniel Kurtz <djkurtz@chromium.org>,
	Pawel Osciak <posciak@chromium.org>
Cc: Eddie Huang <eddie.huang@mediatek.com>,
	Yingjoe Chen <yingjoe.chen@mediatek.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-media@vger.kernel.org, linux-mediatek@lists.infradead.org,
	PoChun.Lin@mediatek.com
Subject: Re: [PATCH v5 0/8] Add MT8173 Video Encoder Driver and VPU Driver
Date: Fri, 26 Feb 2016 13:58:26 +0200	[thread overview]
Message-ID: <56D03DE2.1090400@mm-sol.com> (raw)
In-Reply-To: <56CC1CAB.1060409@xs4all.nl>

Hi Hans,

<snip>

> Nice!
> 
> Can you try 'v4l2-compliance -s'? Note that this may not work since I know
> that v4l2-compliance doesn't work all that well with codecs, but I am
> curious what the output is when you try streaming.

Sorry for the off topic question.

Does every new v4l2 encoder/decoder driver must use v4l2 mem2mem device
framework, with other words is that mandatory?

-- 
regards,
Stan

  parent reply	other threads:[~2016-02-26 11:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-23  8:11 [PATCH v5 0/8] Add MT8173 Video Encoder Driver and VPU Driver Tiffany Lin
2016-02-23  8:11 ` [PATCH v5 1/8] dt-bindings: Add a binding for Mediatek Video Processor Tiffany Lin
2016-02-23  8:11   ` [PATCH v5 2/8] [media] VPU: mediatek: support Mediatek VPU Tiffany Lin
2016-02-23  8:11     ` [PATCH v5 3/8] arm64: dts: mediatek: Add node for Mediatek Video Processor Unit Tiffany Lin
2016-02-23  8:11       ` [PATCH v5 4/8] dt-bindings: Add a binding for Mediatek Video Encoder Tiffany Lin
2016-02-23  8:11         ` [PATCH v5 5/8] [Media] vcodec: mediatek: Add Mediatek V4L2 Video Encoder Driver Tiffany Lin
2016-02-23  8:11           ` [PATCH v5 6/8] [media] vcodec: mediatek: Add Mediatek VP8 " Tiffany Lin
2016-02-23  8:11             ` [PATCH v5 7/8] [media] vcodec: mediatek: Add Mediatek H264 " Tiffany Lin
2016-02-23  8:11               ` [PATCH v5 8/8] arm64: dts: mediatek: Add Video Encoder for MT8173 Tiffany Lin
2016-02-23  8:47 ` [PATCH v5 0/8] Add MT8173 Video Encoder Driver and VPU Driver Hans Verkuil
2016-02-24  8:23   ` tiffany lin
2016-02-24  8:30     ` Hans Verkuil
2016-02-24 10:53       ` tiffany lin
2016-02-26 11:58   ` Stanimir Varbanov [this message]
2016-02-26 13:09     ` Hans Verkuil

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=56D03DE2.1090400@mm-sol.com \
    --to=svarbanov@mm-sol.com \
    --cc=PoChun.Lin@mediatek.com \
    --cc=daniel.thompson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=djkurtz@chromium.org \
    --cc=eddie.huang@mediatek.com \
    --cc=hans.verkuil@cisco.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=mchehab@osg.samsung.com \
    --cc=posciak@chromium.org \
    --cc=robh+dt@kernel.org \
    --cc=tiffany.lin@mediatek.com \
    --cc=yingjoe.chen@mediatek.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;
as well as URLs for NNTP newsgroup(s).