From: Hans Verkuil <hverkuil@xs4all.nl>
To: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>,
LMML <linux-media@vger.kernel.org>,
DLOS <davinci-linux-open-source@linux.davincidsp.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Hans Verkuil <hans.verkuil@cisco.com>,
Mauro Carvalho Chehab <m.chehab@samsung.com>
Subject: Re: [PATCH 1/2] media: davinci: vpif capture: upgrade the driver with v4l offerings
Date: Mon, 31 Mar 2014 17:04:45 +0200 [thread overview]
Message-ID: <5339840D.9000702@xs4all.nl> (raw)
In-Reply-To: <1396277573-9513-2-git-send-email-prabhakar.csengg@gmail.com>
Hi Prabhakar,
This looks really nice!
I'll do a full review on Friday, but in the meantime can you post the output
of 'v4l2-compliance -s' using the latest v4l2-compliance version? I've made
some commits today, so you need to do a git pull of v4l-utils.git.
I also have a small comment below:
On 03/31/2014 04:52 PM, Lad, Prabhakar wrote:
> From: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>
>
> This patch upgrades the vpif display driver with
> v4l helpers, this patch does the following,
>
> 1: initialize the vb2 queue and context at the time of probe
> and removes context at remove() callback.
> 2: uses vb2_ioctl_*() helpers.
> 3: uses vb2_fop_*() helpers.
> 4: uses SIMPLE_DEV_PM_OPS.
> 5: uses vb2_ioctl_*() helpers.
> 6: vidioc_g/s_priority is now handled by v4l core.
> 7: removed driver specific fh and now using one provided by v4l.
> 8: fixes checkpatch warnings.
>
> Signed-off-by: Lad, Prabhakar <prabhakar.csengg@gmail.com>
> ---
> drivers/media/platform/davinci/vpif_capture.c | 916 ++++++-------------------
> drivers/media/platform/davinci/vpif_capture.h | 32 +-
> 2 files changed, 229 insertions(+), 719 deletions(-)
>
> diff --git a/drivers/media/platform/davinci/vpif_capture.c b/drivers/media/platform/davinci/vpif_capture.c
> index 8dea0b8..76c15b3 100644
> --- a/drivers/media/platform/davinci/vpif_capture.c
> +++ b/drivers/media/platform/davinci/vpif_capture.c
...
> static int vpif_buffer_init(struct vb2_buffer *vb)
> {
> - struct vpif_cap_buffer *buf = container_of(vb,
> - struct vpif_cap_buffer, vb);
> + struct vpif_cap_buffer *buf = to_vpif_buffer(vb);
>
> INIT_LIST_HEAD(&buf->list);
>
> return 0;
> }
Is this really necessary? I think vpif_buffer_init can just be removed.
Ditto for vpif_display.c.
Regards,
Hans
next prev parent reply other threads:[~2014-03-31 15:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 14:52 [PATCH 0/2] DaVinci: VPIF: upgrade with v4l helpers Lad, Prabhakar
2014-03-31 14:52 ` [PATCH 1/2] media: davinci: vpif capture: upgrade the driver with v4l offerings Lad, Prabhakar
2014-03-31 15:04 ` Hans Verkuil [this message]
2014-03-31 17:24 ` Prabhakar Lad
2014-04-01 6:40 ` Hans Verkuil
2014-03-31 14:52 ` [PATCH 2/2] media: davinci: vpif display: " Lad, Prabhakar
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=5339840D.9000702@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=hans.verkuil@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=prabhakar.csengg@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