From: Hans Verkuil <hverkuil@xs4all.nl>
To: Benoit Parrot <bparrot@ti.com>
Cc: linux-media@vger.kernel.org
Subject: Re: [Patch v2 1/2] media: v4l: ti-vpe: Add CAL v4l2 camera capture driver
Date: Tue, 20 Oct 2015 21:55:32 +0200 [thread overview]
Message-ID: <56269C34.3000306@xs4all.nl> (raw)
In-Reply-To: <562112B7.7090103@xs4all.nl>
On 10/16/2015 05:07 PM, Hans Verkuil wrote:
> On 09/21/2015 10:04 PM, Benoit Parrot wrote:
>> The Camera Adaptation Layer (CAL) is a block which consists of a dual
>> port CSI2/MIPI camera capture engine.
>> Port #0 can handle CSI2 camera connected to up to 4 data lanes.
>> Port #1 can handle CSI2 camera connected to up to 2 data lanes.
>> The driver implements the required API/ioctls to be V4L2 compliant.
>> Driver supports the following:
>> - V4L2 API using DMABUF/MMAP buffer access based on videobuf2 api
>> - Asynchronous sensor sub device registration
>> - DT support
>>
>> Signed-off-by: Benoit Parrot <bparrot@ti.com>
>> ---
>> drivers/media/platform/Kconfig | 12 +
>> drivers/media/platform/Makefile | 2 +
>> drivers/media/platform/ti-vpe/Makefile | 4 +
>> drivers/media/platform/ti-vpe/cal.c | 2161 ++++++++++++++++++++++++++++++
>> drivers/media/platform/ti-vpe/cal_regs.h | 779 +++++++++++
>> 5 files changed, 2958 insertions(+)
>> create mode 100644 drivers/media/platform/ti-vpe/cal.c
>> create mode 100644 drivers/media/platform/ti-vpe/cal_regs.h
>>
>> diff --git a/drivers/media/platform/Kconfig b/drivers/media/platform/Kconfig
>> index dc75694ac12d..c7f5704c56a2 100644
>> --- a/drivers/media/platform/Kconfig
>> +++ b/drivers/media/platform/Kconfig
>> @@ -120,6 +120,18 @@ source "drivers/media/platform/s5p-tv/Kconfig"
>> source "drivers/media/platform/am437x/Kconfig"
>> source "drivers/media/platform/xilinx/Kconfig"
>>
>> +config VIDEO_TI_CAL
>> + tristate "TI CAL (Camera Adaptation Layer) driver"
>> + depends on VIDEO_DEV && VIDEO_V4L2 && SOC_DRA7XX
>> + depends on VIDEO_V4L2_SUBDEV_API
>> + depends on VIDEOBUF2_DMA_CONTIG
>
> This should be:
>
> depends on VIDEO_DEV && VIDEO_V4L2 && VIDEO_V4L2_SUBDEV_API
> depends on SOC_DRA7XX || COMPILE_TEST
> select VIDEOBUF2_DMA_CONTIG
>
>> + default n
>> + ---help---
>> + Support for the TI CAL (Camera Adaptation Layer) block
>> + found on DRA72X SoC.
>> + In TI Technical Reference Manual this module is referred as
>> + Camera Interface Subsystem (CAMSS).
>> +
>> endif # V4L_PLATFORM_DRIVERS
>>
>> menuconfig V4L_MEM2MEM_DRIVERS
>
> By compiling with COMPILE_TEST I found a number of compile warnings and it also no
> longer compiled due to vb2 changes. Both are fixed in the patch below.
>
> SoB for the patch: Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
>
> That said, I'll postpone merging this until the remainder of the vb2 split patches
> have been merged. When that's done this driver will have to be changed some more.
OK, the vb2 split patches were just merged. Can you rebase and repost?
Thanks,
Hans
next prev parent reply other threads:[~2015-10-20 19:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 20:04 [Patch v2 0/2] media: v4l: ti-vpe: Add CAL v4l2 camera capture driver Benoit Parrot
2015-09-21 20:04 ` [Patch v2 1/2] " Benoit Parrot
2015-10-16 15:07 ` Hans Verkuil
2015-10-20 19:55 ` Hans Verkuil [this message]
2015-11-13 9:13 ` Hans Verkuil
2015-09-21 20:04 ` [Patch v2 2/2] media: v4l: ti-vpe: Document CAL driver Benoit Parrot
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=56269C34.3000306@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=bparrot@ti.com \
--cc=linux-media@vger.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).