public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: m-karicheri2@ti.com
Cc: linux-media@vger.kernel.org,
	davinci-linux-open-source@linux.davincidsp.com,
	Muralidharan Karicheri <a0868495@dal.design.ti.com>
Subject: Re: [PATCH 0/11 - v3] ARM: DaVinci: Video: DM355/DM6446 VPFE Capture driver
Date: Fri, 19 Jun 2009 13:49:07 -0700	[thread overview]
Message-ID: <87ljnot0e4.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1245269484-8325-1-git-send-email-m-karicheri2@ti.com> (m-karicheri2@ti.com's message of "Wed\, 17 Jun 2009 16\:11\:13 -0400")

m-karicheri2@ti.com writes:

> From: Muralidharan Karicheri <a0868495@gt516km11.gt.design.ti.com>
>
> Big Thanks to all reviewers who have contributed to this driver
> by reviewing and offering valuable comments.
>
> VPFE Capture driver for DaVinci Media SOCs :- DM355 and DM6446
>
> This is the version v3 of the patch series. This is the reworked
> version of the driver based on comments received against the last
> version (v2) of the patch and is expected to be final version
> candidate for merge to upstream kernel

FYI...

I've updated the staging/vpfe branch of davinci git with this series
and the tvp514x v3 patch.

Also, I'll be pushing the arch/arm/* patches of this series to DaVinci
git master and queueing them for upstream merge.

Kevin

>
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> These patches add support for VPFE (Video Processing Front End) based
> video capture on DM355 and DM6446 EVMs. For more details on the hardware
> configuration and capabilities, please refer the vpfe_capture.c header.
> This patch set consists of following:- 
>
> Patch 1: VPFE Capture bridge driver
> Patch 2: CCDC hw device header file
> Patch 3: DM355 CCDC hw module
> Patch 4: DM644x CCDC hw module
> Patch 5: ccdc types used across CCDC modules
> Patch 6: Makefile and config files for the driver
> Patch 7: DM355 platform and board setup
> Patch 8: DM644x platform and board setup
> Patch 9: common vpss hw module for video drivers
> Patch 10: Remove outdated driver files from davinci git tree
> Patch 11: Makefile and config files for the davinci git tree (New
> from v2)
>
> NOTE:
>
> 1. Patches 10-11 are only for DaVinci GIT tree. Others applies to
> DaVinci GIT and v4l-dvb
>
> 2. Dependent on the TVP514x decoder driver patch for migrating the
> driver to sub device model from Vaibhav Hiremath. I am sending the
> reworked version of this patch instead of Vaibhav.

> Following tests are performed.
> 	1) Capture and display video (PAL & NTSC) from tvp5146 decoder.
> 	   Displayed using fbdev device driver available on davinci git tree
> 	2) Tested with driver built statically and dynamically
>
> Muralidhara Karicheri
>
> Reviewed by: Hans Verkuil <hverkuil@xs4all.nl>
> Reviewed by: Laurent Pinchart <laurent.pinchart@skynet.be>
> Reviewed by: Alexey Klimov <klimov.linux@gmail.com>
> Reviewed by: Kevin Hilman <khilman@deeprootsystems.com>
> Reviewed by: David Brownell <david-b@pacbell.net>
>
> Signed-off-by: Muralidharan Karicheri <m-karicheri2@ti.com>
> _______________________________________________
> Davinci-linux-open-source mailing list
> Davinci-linux-open-source@linux.davincidsp.com
> http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

  parent reply	other threads:[~2009-06-19 21:12 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-17 20:11 [PATCH 0/11 - v3] ARM: DaVinci: Video: DM355/DM6446 VPFE Capture driver m-karicheri2
2009-06-17 20:11 ` [PATCH 1/11 - v3] vpfe capture bridge driver for DM355 and DM6446 m-karicheri2
2009-06-17 20:11   ` [PATCH 2/11 - v3] ccdc hw device header file for vpfe capture m-karicheri2
2009-06-17 20:11     ` [PATCH 3/11 - v3] dm355 ccdc module for vpfe capture driver m-karicheri2
2009-06-17 20:11       ` [PATCH 4/11 - v3] dm644x " m-karicheri2
2009-06-17 20:11         ` [PATCH 5/11 - v3] ccdc types used across ccdc modules " m-karicheri2
2009-06-17 20:11           ` [PATCH 6/11 - v3] Makefile and config files " m-karicheri2
2009-06-17 20:11             ` [PATCH 7/11 - v3] DM355 platform changes " m-karicheri2
2009-06-17 20:11               ` [PATCH 8/11 - v3] DM6446 " m-karicheri2
2009-06-17 20:11                 ` [PATCH 9/11 - v3] common vpss module for video drivers m-karicheri2
2009-06-17 20:11                   ` [PATCH 10/11 - v3] remove outdated video driver files for dm6446 m-karicheri2
2009-06-17 20:11                     ` [PATCH 11/11 - v3] Makefile and config file changes for davinci git tree m-karicheri2
2009-06-19 21:24                     ` [PATCH 10/11 - v3] remove outdated video driver files for dm6446 Kevin Hilman
2009-06-17 21:59         ` [PATCH 4/11 - v3] dm644x ccdc module for vpfe capture driver Alexey Klimov
2009-06-17 21:51       ` [PATCH 3/11 - v3] dm355 " Alexey Klimov
2009-06-19 12:42         ` Hans Verkuil
2009-06-22 14:13           ` Karicheri, Muralidharan
2009-06-17 21:29   ` [PATCH 1/11 - v3] vpfe capture bridge driver for DM355 and DM6446 Alexey Klimov
2009-06-19 12:40     ` Hans Verkuil
2009-06-22 14:12       ` Karicheri, Muralidharan
2009-06-19 20:49 ` Kevin Hilman [this message]
2009-06-20  7:01   ` [PATCH 0/11 - v3] ARM: DaVinci: Video: DM355/DM6446 VPFE Capture driver 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=87ljnot0e4.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=a0868495@dal.design.ti.com \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=linux-media@vger.kernel.org \
    --cc=m-karicheri2@ti.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