linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: javier.martin@vista-silicon.com (javier Martin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] MT9P031: Add support for Aptina mt9p031 sensor.
Date: Wed, 25 May 2011 09:00:21 +0200	[thread overview]
Message-ID: <BANLkTi=7mssSFd=HYwVReoKw6VEC_Qvs0Q@mail.gmail.com> (raw)
In-Reply-To: <551158.38796.qm@web112009.mail.gq1.yahoo.com>

Please, do not remove anyone from the CC list.

On 25 May 2011 05:45, Chris Rodley <carlighting@yahoo.co.nz> wrote:
> Hi,
>
> Have upgraded the driver to Javier's latest RFC driver.
> Still having problems viewing output.
>
> Setting up with:
> # media-ctl -r -l '"mt9p031 2-0048":0->"OMAP3 ISP CCDC":0[1], "OMAP3 ISP CCDC":1->"OMAP3 ISP CCDC output":0[1]'
> Resetting all links to inactive
> Setting up link 16:0 -> 5:0 [1]
> Setting up link 5:1 -> 6:0 [1]
>
> # media-ctl -f '"mt9p031 2-0048":0[SGRBG12 320x240], "OMAP3 ISP CCDC":0[SGRBG8 320x240], "OMAP3 ISP CCDC":1[SGRBG8 320x240]'
> Setting up format SGRBG12 320x240 on pad mt9p031 2-0048/0
> Format set: SGRB
> Setting up format SGRBG12 320x240 on pad OMAP3 ISP CCDC/0
> Format set: SGRBG12 320x240
> Setting up format SGRBG8 320x240 on pad OMAP3 ISP CCDC/0
> Format set: SGRBG8 320x240
> Setting up format SGRBG8 320x240 on pad OMAP3 ISP CCDC/1
> Format set: SGRBG8 320x240
>
> Then:
> # yavta -f SGRBG8 -s 320x240 -n 4 --capture=100 -F /dev/video2
> Device /dev/video2 opened.
> Device `OMAP3 ISP CCDC output' on `media' is a video capture device.
> Video format set: width: 320 height: 240 buffer size: 76800
> Video format: GRBG (47425247) 320x240
> 4 buffers requested.
> length: 76800 offset: 0
> Buffer 0 mapped at address 0x4006c000.
> length: 76800 offset: 77824
> Buffer 1 mapped at address 0x40222000.
> length: 76800 offset: 155648
> Buffer 2 mapped at address 0x4025e000.
> length: 76800 offset: 233472
> Buffer 3 mapped at address 0x402f0000.
>
> After this it hangs and will exit on 'ctrl c':
> omap3isp omap3isp: CCDC stop timeout!
>
> Any ideas what is causing this problem?
>

No idea,
it works for me. Note you have to apply RFC + PATCH v2 2/2. Please,
double check.

Also, if you have problems with last RFC patch you should answer RFC
mail. Not this one.

Thank you.

-- 
Javier Martin
Vista Silicon S.L.
CDTUC - FASE C - Oficina S-345
Avda de los Castros s/n
39005- Santander. Cantabria. Spain
+34 942 25 32 60
www.vista-silicon.com

       reply	other threads:[~2011-05-25  7:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <551158.38796.qm@web112009.mail.gq1.yahoo.com>
2011-05-25  7:00 ` javier Martin [this message]
2011-05-20 13:47 [PATCH v2 1/2] MT9P031: Add support for Aptina mt9p031 sensor Javier Martin
2011-05-21 12:55 ` Mauro Carvalho Chehab
2011-05-22 20:41   ` Laurent Pinchart
2011-05-21 15:29 ` Guennadi Liakhovetski
2011-05-23  8:20   ` javier Martin
2011-05-23  8:48     ` Guennadi Liakhovetski
2011-05-23  9:08       ` Laurent Pinchart
2011-05-23  9:03   ` Laurent Pinchart
2011-05-23  9:26     ` Guennadi Liakhovetski
2011-05-24  8:31     ` javier Martin
2011-05-24  8:39       ` Laurent Pinchart
2011-05-24  8:56         ` javier Martin
2011-05-24  8:58           ` 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='BANLkTi=7mssSFd=HYwVReoKw6VEC_Qvs0Q@mail.gmail.com' \
    --to=javier.martin@vista-silicon.com \
    --cc=linux-arm-kernel@lists.infradead.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).