public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil@xs4all.nl>
To: Scott Jiang <scott.jiang.linux@gmail.com>,
	Lad Prabhakar <prabhakar.csengg@gmail.com>
Cc: adi-buildroot-devel@lists.sourceforge.net,
	Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
	LMML <linux-media@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 00/15] media: blackfin: bfin_capture enhancements
Date: Tue, 03 Mar 2015 09:49:49 +0100	[thread overview]
Message-ID: <54F575AD.5020307@xs4all.nl> (raw)
In-Reply-To: <CAHG8p1DFu8Y1qaDc9c0m0JggUHrF4grHBj9VZQ4224v2wPJRbQ@mail.gmail.com>

On 03/02/2015 08:57 AM, Scott Jiang wrote:
> Hi Lad and Hans,
> 
> 2015-02-22 2:39 GMT+08:00 Lad Prabhakar <prabhakar.csengg@gmail.com>:
>> From: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>
>>
>> This patch series, enhances blackfin capture driver with
>> vb2 helpers.
>>
>> Changes for v3:
>> 1: patches unchanged except for patch 8/15 fixing starting of ppi only
>>    after we have the resources.
>> 2: Rebased on media tree.
>>
>> v2: http://lkml.iu.edu/hypermail/linux/kernel/1501.2/04655.html
>>
>> v1: https://lkml.org/lkml/2014/12/20/27
>>
>> Lad, Prabhakar (15):
>>   media: blackfin: bfin_capture: drop buf_init() callback
>>   media: blackfin: bfin_capture: release buffers in case
>>     start_streaming() call back fails
>>   media: blackfin: bfin_capture: set min_buffers_needed
>>   media: blackfin: bfin_capture: improve buf_prepare() callback
>>   media: blackfin: bfin_capture: improve queue_setup() callback
>>   media: blackfin: bfin_capture: use vb2_fop_mmap/poll
>>   media: blackfin: bfin_capture: use v4l2_fh_open and vb2_fop_release
>>   media: blackfin: bfin_capture: use vb2_ioctl_* helpers
>>   media: blackfin: bfin_capture: make sure all buffers are returned on
>>     stop_streaming() callback
>>   media: blackfin: bfin_capture: return -ENODATA for *std calls
>>   media: blackfin: bfin_capture: return -ENODATA for *dv_timings calls
>>   media: blackfin: bfin_capture: add support for vidioc_create_bufs
>>   media: blackfin: bfin_capture: add support for VB2_DMABUF
>>   media: blackfin: bfin_capture: add support for VIDIOC_EXPBUF
>>   media: blackfin: bfin_capture: set v4l2 buffer sequence
>>
>>  drivers/media/platform/blackfin/bfin_capture.c | 306 ++++++++-----------------
>>  1 file changed, 94 insertions(+), 212 deletions(-)
>>
>> --
> 
> For all these patches,
> Acked-by: Scott Jiang <scott.jiang.linux@gmail.com>
> Tested-by: Scott Jiang <scott.jiang.linux@gmail.com>

Thanks!

Is it possible for you to run 'v4l2-compliance -s' with this driver and
report the results? I'd be interested in that.

Regards,

	Hans

  reply	other threads:[~2015-03-03  8:50 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-21 18:39 [PATCH v3 00/15] media: blackfin: bfin_capture enhancements Lad Prabhakar
2015-02-21 18:39 ` [PATCH v3 01/15] media: blackfin: bfin_capture: drop buf_init() callback Lad Prabhakar
2015-02-21 18:39 ` [PATCH v3 02/15] media: blackfin: bfin_capture: release buffers in case start_streaming() call back fails Lad Prabhakar
2015-02-21 18:39 ` [PATCH v3 03/15] media: blackfin: bfin_capture: set min_buffers_needed Lad Prabhakar
2015-02-21 18:39 ` [PATCH v3 04/15] media: blackfin: bfin_capture: improve buf_prepare() callback Lad Prabhakar
2015-03-03 15:21   ` Hans Verkuil
2015-02-21 18:39 ` [PATCH v3 05/15] media: blackfin: bfin_capture: improve queue_setup() callback Lad Prabhakar
2015-03-03 14:13   ` Mauro Carvalho Chehab
2015-02-21 18:39 ` [PATCH v3 06/15] media: blackfin: bfin_capture: use vb2_fop_mmap/poll Lad Prabhakar
2015-03-03 10:14   ` Hans Verkuil
2015-02-21 18:39 ` [PATCH v3 07/15] media: blackfin: bfin_capture: use v4l2_fh_open and vb2_fop_release Lad Prabhakar
2015-02-21 18:39 ` [PATCH v3 08/15] media: blackfin: bfin_capture: use vb2_ioctl_* helpers Lad Prabhakar
2015-02-21 18:39 ` [PATCH v3 09/15] media: blackfin: bfin_capture: make sure all buffers are returned on stop_streaming() callback Lad Prabhakar
2015-02-21 18:39 ` [PATCH v3 10/15] media: blackfin: bfin_capture: return -ENODATA for *std calls Lad Prabhakar
2015-02-21 18:39 ` [PATCH v3 11/15] media: blackfin: bfin_capture: return -ENODATA for *dv_timings calls Lad Prabhakar
2015-02-21 18:39 ` [PATCH v3 12/15] media: blackfin: bfin_capture: add support for vidioc_create_bufs Lad Prabhakar
2015-02-21 18:39 ` [PATCH v3 13/15] media: blackfin: bfin_capture: add support for VB2_DMABUF Lad Prabhakar
2015-02-21 18:40 ` [PATCH v3 14/15] media: blackfin: bfin_capture: add support for VIDIOC_EXPBUF Lad Prabhakar
2015-02-21 18:40 ` [PATCH v3 15/15] media: blackfin: bfin_capture: set v4l2 buffer sequence Lad Prabhakar
2015-03-02  7:57 ` [PATCH v3 00/15] media: blackfin: bfin_capture enhancements Scott Jiang
2015-03-03  8:49   ` Hans Verkuil [this message]
2015-03-03  9:30     ` Lad, Prabhakar
2015-03-03  9:39       ` Hans Verkuil
2015-03-03  9:43         ` Lad, Prabhakar
2015-03-05  9:44           ` Scott Jiang
2015-03-05 10:26             ` Hans Verkuil
2015-03-07 16:22               ` Lad, Prabhakar
2015-03-07 16:35                 ` 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=54F575AD.5020307@xs4all.nl \
    --to=hverkuil@xs4all.nl \
    --cc=adi-buildroot-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@osg.samsung.com \
    --cc=prabhakar.csengg@gmail.com \
    --cc=scott.jiang.linux@gmail.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