devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Prabhakar Lad <prabhakar.csengg@gmail.com>
To: Felipe Balbi <balbi@ti.com>
Cc: Hans Verkuil <hans.verkuil@cisco.com>,
	Tony Lindgren <tony@atomide.com>,
	Benoit Cousson <bcousson@baylibre.com>,
	Rob Herring <robh+dt@kernel.org>,
	Russell King <linux@arm.linux.org.uk>,
	Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
	Linux ARM Kernel Mailing List
	<linux-arm-kernel@lists.infradead.org>,
	linux-media <linux-media@vger.kernel.org>,
	archit@ti.com, "Etheridge, Darren" <detheridge@ti.com>,
	Sakari Ailus <sakari.ailus@iki.fi>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [RFC/PATCH 0/5] Add Video Processing Front End Support
Date: Thu, 17 Jul 2014 13:43:32 +0100	[thread overview]
Message-ID: <CA+V-a8sZF-M1Me0ZpVAkCGChQYYNcCopdW50fLZwPQ1uCLgx4Q@mail.gmail.com> (raw)
In-Reply-To: <1405447012-5340-1-git-send-email-balbi@ti.com>

On Tue, Jul 15, 2014 at 6:56 PM, Felipe Balbi <balbi@ti.com> wrote:
> Hi all,
>
> the following patches add suport for AM43xx's Video Processing
> Front End (VPFE). Full documentation is available at [1] chapter 14.
>
> This driver has been tested with linux-next from yesterday, plus my
> (already queued) am437x starter kit patches, plus these patches, plus
> the sensor driver which, saddly enough, we're not allowed to release :-(
>
> This driver has almost full v4l2-compliance with only 2 failures (I'll
> take hints on how to properly fix them) as below:
>
>                 fail: v4l2-compliance.cpp(419): !doioctl(node2,
>                         VIDIOC_S_PRIORITY, &prio)
>         test VIDIOC_G/S_PRIORITY: FAIL
>
>                 fail: v4l2-test-formats.cpp(319): pixelformat !=
>                                 V4L2_PIX_FMT_JPEG && colorspace ==
>                                 V4L2_COLORSPACE_JPEG
>                 fail: v4l2-test-formats.cpp(418):
>                                 testColorspace(pix.pixelformat, pix.colorspace)
>         test VIDIOC_G_FMT: FAIL
>
> I have also tested with gst-launch using fbdevsink and I can see my
> ugly mug just fine.
>
> Please give this a thorough review and let me know of any problems
> which need to be sorted out and I'll try to help out as time allows.
>
> cheers
>
> [1] http://www.ti.com/lit/pdf/spruhl7
>
> Benoit Parrot (4):
>   Media: platform: Add ti-vpfe driver for AM437x device
>   arm: omap: hwmod: add hwmod entries for AM437x VPFE
>   arm: boot: dts: am4372: add vpfe DTS entries
>   arm: dts: am43x-epos: Add VPFE DTS entries
>
> Darren Etheridge (1):
>   ARM: dts: am437x-sk-evm: add vpfe support and ov2659 sensor
>
>  arch/arm/boot/dts/am4372.dtsi                     |   16 +
>  arch/arm/boot/dts/am437x-sk-evm.dts               |   63 +
>  arch/arm/boot/dts/am43x-epos-evm.dts              |   54 +
>  arch/arm/mach-omap2/omap_hwmod_43xx_data.c        |   56 +
>  arch/arm/mach-omap2/prcm43xx.h                    |    3 +-
>  drivers/media/platform/Kconfig                    |    1 +
>  drivers/media/platform/Makefile                   |    2 +
>  drivers/media/platform/ti-vpfe/Kconfig            |   12 +
>  drivers/media/platform/ti-vpfe/Makefile           |    2 +
>  drivers/media/platform/ti-vpfe/am437x_isif.c      | 1053 +++++++++
>  drivers/media/platform/ti-vpfe/am437x_isif.h      |  355 +++
>  drivers/media/platform/ti-vpfe/am437x_isif_regs.h |  144 ++
>  drivers/media/platform/ti-vpfe/vpfe_capture.c     | 2478 +++++++++++++++++++++
>  drivers/media/platform/ti-vpfe/vpfe_capture.h     |  263 +++
>  14 files changed, 4501 insertions(+), 1 deletion(-)

Missing documentation for DT ?

Thanks,
--Prabhakar Lad

>  create mode 100644 drivers/media/platform/ti-vpfe/Kconfig
>  create mode 100644 drivers/media/platform/ti-vpfe/Makefile
>  create mode 100644 drivers/media/platform/ti-vpfe/am437x_isif.c
>  create mode 100644 drivers/media/platform/ti-vpfe/am437x_isif.h
>  create mode 100644 drivers/media/platform/ti-vpfe/am437x_isif_regs.h
>  create mode 100644 drivers/media/platform/ti-vpfe/vpfe_capture.c
>  create mode 100644 drivers/media/platform/ti-vpfe/vpfe_capture.h
>
> --
> 2.0.0.390.gcb682f8
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2014-07-17 12:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-15 17:56 [RFC/PATCH 0/5] Add Video Processing Front End Support Felipe Balbi
2014-07-15 17:56 ` [RFC/PATCH 1/5] Media: platform: Add ti-vpfe driver for AM437x device Felipe Balbi
2014-07-15 20:37   ` Hans Verkuil
     [not found]   ` <1405447012-5340-2-git-send-email-balbi-l0cyMroinI0@public.gmane.org>
2014-07-16  8:39     ` Prabhakar Lad
2014-07-15 17:56 ` [RFC/PATCH 2/5] arm: omap: hwmod: add hwmod entries for AM437x VPFE Felipe Balbi
2014-07-15 17:56 ` [RFC/PATCH 3/5] arm: boot: dts: am4372: add vpfe DTS entries Felipe Balbi
2014-07-15 17:56 ` [RFC/PATCH 4/5] arm: dts: am43x-epos: Add VPFE " Felipe Balbi
2014-07-15 17:56 ` [RFC/PATCH 5/5] ARM: dts: am437x-sk-evm: add vpfe support and ov2659 sensor Felipe Balbi
2014-07-15 18:02   ` Felipe Balbi
2014-07-17 12:43 ` Prabhakar Lad [this message]

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=CA+V-a8sZF-M1Me0ZpVAkCGChQYYNcCopdW50fLZwPQ1uCLgx4Q@mail.gmail.com \
    --to=prabhakar.csengg@gmail.com \
    --cc=archit@ti.com \
    --cc=balbi@ti.com \
    --cc=bcousson@baylibre.com \
    --cc=detheridge@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hans.verkuil@cisco.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=robh+dt@kernel.org \
    --cc=sakari.ailus@iki.fi \
    --cc=tony@atomide.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).