All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Enrico <ebutera@users.sourceforge.net>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	Enric Balletbo Serra <eballetbo@gmail.com>,
	stefan@herbrechtsmeier.net
Subject: Re: [PATCH 00/11] OMAP3 ISP BT.656 support
Date: Tue, 22 Jul 2014 18:04:03 +0200	[thread overview]
Message-ID: <5099401.EbLZaQU31t@avalon> (raw)
In-Reply-To: <CA+2YH7t0rzko=Ssg7Qe8oC_qXUTr=uFzDqBqmPtAAbQ2dAntNA@mail.gmail.com>

Hi Enrico,

On Tuesday 22 July 2014 17:52:27 Enrico wrote:
> On Tue, Jun 24, 2014 at 5:19 PM, Enrico <ebutera@users.berlios.de> wrote:
> > On Tue, May 27, 2014 at 10:38 AM, Enrico <ebutera@users.berlios.de> wrote:
> >> On Mon, May 26, 2014 at 9:50 PM, Laurent Pinchart wrote:
> >>> Hello,
> >>> 
> >>> This patch sets implements support for BT.656 and interlaced formats in
> >>> the OMAP3 ISP driver. Better late than never I suppose, although given
> >>> how long this has been on my to-do list there's probably no valid
> >>> excuse.
> >> 
> >> Thanks Laurent!
> >> 
> >> I hope to have time soon to test it :)
> > 
> > Hi Laurent,
> > 
> > i wanted to try your patches but i'm having a problem (probably not
> > caused by your patches).
> > 
> > I merged media_tree master and omap3isp branches, applied your patches
> > and added camera platform data in pdata-quirks, but when loading the
> > omap3-isp driver i have:
> > 
> > omap3isp: clk_set_rate for cam_mclk failed
> > 
> > The returned value from clk_set_rate is -22 (EINVAL), but i can't see
> > any other debug message to track it down. Any ides?
> > I'm testing it on an igep proton (omap3530 version).
> 
> I found out that my previous email was not working anymore, so i
> didn't read about Stefan patch (ti,set-rate-parent).
> 
> With that patch i can setup my pipeline (attached), but i can't make
> yavta capture:
> 
> root@igep00x0:~/field# ./yavta -f UYVY -n4 -s 720x624 -c100 /dev/video2
> Device /dev/video2 opened.
> Device `OMAP3 ISP CCDC output' on `media' is a video output (without
> mplanes) device.
> Video format set: UYVY (59565955) 720x624 (stride 1440) field none
> buffer size 898560
> Video format: UYVY (59565955) 720x624 (stride 1440) field none buffer
> size 898560
> 4 buffers requested.
> length: 898560 offset: 0 timestamp type/source: mono/EoF
> Buffer 0/0 mapped at address 0xb6ce4000.
> length: 898560 offset: 901120 timestamp type/source: mono/EoF
> Buffer 1/0 mapped at address 0xb6c08000.
> length: 898560 offset: 1802240 timestamp type/source: mono/EoF
> Buffer 2/0 mapped at address 0xb6b2c000.
> length: 898560 offset: 2703360 timestamp type/source: mono/EoF
> Buffer 3/0 mapped at address 0xb6a50000.
> Unable to start streaming: Invalid argument (22).
> 4 buffers released.
> 
> strace:
> 
> ioctl(3, VIDIOC_STREAMON, 0xbef9c75c)   = -1 EINVAL (Invalid argument)
> 
> any ideas?

You will need to upgrade media-ctl and yavta to versions that support 
interlaced formats. media-ctl has been moved to v4l-utils 
(http://git.linuxtv.org/cgit.cgi/v4l-utils.git/) and yavta is hosted at 
git://git.ideasonboard.org/yavta.git. You want to use the master branch for 
both trees.

-- 
Regards,

Laurent Pinchart


  reply	other threads:[~2014-07-22 16:03 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-26 19:50 [PATCH 00/11] OMAP3 ISP BT.656 support Laurent Pinchart
2014-05-26 19:50 ` [PATCH 01/11] v4l: subdev: Extend default link validation to cover field order Laurent Pinchart
2014-05-26 19:50 ` [PATCH 02/11] omap3isp: Don't ignore subdev streamoff failures Laurent Pinchart
2014-05-26 19:50 ` [PATCH 03/11] omap3isp: Remove boilerplate disclaimer and FSF address Laurent Pinchart
2014-05-26 19:50 ` [PATCH 04/11] omap3isp: Move non-critical code out of the mutex-protected section Laurent Pinchart
2014-05-26 19:50 ` [PATCH 05/11] omap3isp: Default to progressive field order when setting the format Laurent Pinchart
2014-05-26 19:50 ` [PATCH 06/11] omap3isp: video: Validate the video node field order Laurent Pinchart
2014-05-26 19:50 ` [PATCH 07/11] omap3isp: ccdc: Simplify the configuration function Laurent Pinchart
2014-05-26 19:50 ` [PATCH 08/11] omap3isp: ccdc: Simplify the ccdc_isr_buffer() function Laurent Pinchart
2014-05-26 19:50 ` [PATCH 09/11] omap3isp: ccdc: Add basic support for interlaced video Laurent Pinchart
2014-05-26 21:12   ` Sakari Ailus
2014-05-26 19:50 ` [PATCH 10/11] omap3isp: ccdc: Support the interlaced field orders at the CCDC output Laurent Pinchart
2014-05-26 19:50 ` [PATCH 11/11] omap3isp: ccdc: Add support for BT.656 YUV format at the CCDC input Laurent Pinchart
2014-05-26 21:18 ` [PATCH 00/11] OMAP3 ISP BT.656 support Sakari Ailus
2014-05-27  8:38 ` Enrico
2014-06-24 15:19   ` Enrico
2014-06-24 17:19     ` Stefan Herbrechtsmeier
2014-07-01 20:24       ` Laurent Pinchart
2014-07-04 11:21         ` Stefan Herbrechtsmeier
2014-06-26 16:18     ` Enrico
2014-07-01 20:17       ` Laurent Pinchart
2014-07-22 15:52     ` Enrico
2014-07-22 16:04       ` Laurent Pinchart [this message]
2014-07-22 16:26         ` Enrico
2014-07-22 16:32           ` Laurent Pinchart
2014-07-23 13:54             ` Enrico
2014-07-23 13:57               ` Enrico
2014-07-30 21:01                 ` Laurent Pinchart
2014-07-31 10:21                   ` Enrico
2014-08-01 13:46                     ` Laurent Pinchart
     [not found]         ` <1406046034.73192.YahooMailNeo@web162404.mail.bf1.yahoo.com>
2014-07-22 16:27           ` Laurent Pinchart

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=5099401.EbLZaQU31t@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=eballetbo@gmail.com \
    --cc=ebutera@users.sourceforge.net \
    --cc=linux-media@vger.kernel.org \
    --cc=stefan@herbrechtsmeier.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.