All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Maik Steuer" <Maik.Steuer@gmx.de>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: video4linux-list@redhat.com, kernel@pengutronix.de
Subject: Re: testing soc_camera with mt9m001 on pxa270
Date: Fri, 28 Nov 2008 17:26:09 +0100	[thread overview]
Message-ID: <20081128162609.107740@gmx.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0811281613160.4430@axis700.grange>


-------- Original-Nachricht --------
> Datum: Fri, 28 Nov 2008 16:16:48 +0100 (CET)
> Von: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
> An: Maik Steuer <Maik.Steuer@gmx.de>
> CC: video4linux-list@redhat.com, kernel@pengutronix.de
> Betreff: Re: testing soc_camera with mt9m001 on pxa270

> On Fri, 28 Nov 2008, Maik Steuer wrote:
> 
> > Hello,
> > 
> > I'm testing at the moment the capture interface with the soc-camera and 
> > mt9m001 driver.
> > 
> > I fixed all I2C routines to test without any connected camera like 
> > mt9m001, because we want to use another camera hardware as mt9m001.
> > 
> > To read out the capture buffer I use the example project capture.c from 
> > V4L2-API with mmap(). The ioctl (fd, VIDIOC_REQBUFS, &req) at the 
> > beginning of initialization fails.  I have debuged the most important 
> > parts of the driver (pxa_camera, soc_camera and mt9m001) but I can't 
> > find the mistake.
> > 
> > Any Idea?
> 
> Sorry, no. Without knowing what kernel version you're using, without 
> seeing your "fixes to all I2C routines" I don't think anyone would be able
> to tell you what the problem is. 

I'm using 2.6.27.7. The fixes are easy. The two functions reg_read() and reg_write() in mt9m001.c returns always with 0 and the included i2c_smbus_read_word_data() and i2c_smbus_write_word_data() were commented out. I set the MT9M001_CHIP_VERSION to 0x8431 and set the default data_width to 8. That's all. In the V4L2-API capture example I set the right color space (in this case V4L2_PIX_FMT_GREY).

> And anyway you wouldn't get too far 
> without a real camera - at best when the pxa will start capturing, it will
> timeout waiting for sync signals. Maybe you would be able to do this if 
> you switch to the slave mode, but beware, that this mode hasn't been 
> tested.
> 

The pxa doesn't start capturing. That's my target to test the capture interface. I don't know if there is an easier way to start capturing as with the capture example from V4L2-API.

> I would suggest you tell us what camera you are going to use, maybe 
> someone is already working on a driver for it. If not - you write a driver
> yourself and start working with a real hardware.
> 

At the moment the camera is only a FPGA which sends 8 Bit dummy data with hsync, vsync and pixclock. So I can change all necessary parameters for pxa requirements.

I throught that the ioctl (fd, VIDIOC_REQBUFS, &req) starts soc_camera_reqbufs() but it isn't so.

greets
Maik

> Thanks
> Guennadi
> 
> > 
> > 
> > Here is a short log, which functions were called:
> > 
> > [@Linux /opt]#./capture -m
> > soc_camera_open()
> > pxa_camera_add_device() !!!
> > camera 0-0: PXA Camera driver attached to camera 0
> > pxa_camera_activate() !!!
> > mt9m001_init() !
> > pxa_camera_add_device() ret !!!
> > pxa_camera_init_videobuf() !!!
> > soc_camera_querycap()
> > soc_camera_querycap() ret 0
> > soc_camera_cropcap()
> > soc_camera_s_crop()
> > mt9m001_set_fmt_cap() !
> > mt9m001_set_fmt_cap() ! ret 0
> > soc_camera_s_crop() ret 0
> > soc_camera_s_fmt_vid_cap()
> > soc_camera_try_fmt_vid_cap()
> > pxa_camera_try_bus_param() !!!
> > 	test_platform_param() !!!
> > buswidth 8 flags 3133
> > 	buswidth 8 flags 3197
> > mt9m001_query_bus_param() !
> > bus_switch_possible() !
> > width_flag 455
> > soc_camera_bus_param_compatible() ret 1109 !!!
> > mt9m001_try_fmt_cap() !
> > try_fmt__cap() ret 0
> > soc_camera_try_fmt_vid_cap() ret 0
> > mt9m001_set_fmt_cap() !
> > mt9m001_set_fmt_cap() ! ret 0
> > pxa_camera_set_bus_param()!!!
> > 	test_platform_param() !!!
> > buswidth 8 flags 3133
> > 	buswidth 8 flags 3197
> > mt9m001_query_bus_param()!
> > bus_switch_possible()!
> > width_flag 455
> > mt9m001_set_bus_param()!
> > flags 1109 datawidth 8 width_flags 64
> > pxa_camera_set_bus_param() ret 0 !!!
> > soc_camera_s_fmt_vid_cap() ret 0 
> > /dev/video does not support memory mapping
> > soc_camera_close()
> > camera 0-0: PXA Camera driver detached from camera 0
> > mt9m001_release() !
> > 
> > 
> > greets
> > 
> > Maik
> > -- 
> > Sensationsangebot nur bis 30.11: GMX FreeDSL - Telefonanschluss + DSL 
> > für nur 16,37 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a
> > 
> 
> ---
> Guennadi Liakhovetski, Ph.D.
> Freelance Open-Source Software Developer

-- 
Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

  reply	other threads:[~2008-11-28 16:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-28 14:58 testing soc_camera with mt9m001 on pxa270 Maik Steuer
2008-11-28 15:16 ` Guennadi Liakhovetski
2008-11-28 16:26   ` Maik Steuer [this message]
2008-11-28 17:00     ` Guennadi Liakhovetski
2008-12-01 10:35       ` Maik Steuer
2008-12-01 10:43         ` Guennadi Liakhovetski
2008-12-01 14:37           ` Mauro Carvalho Chehab

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=20081128162609.107740@gmx.net \
    --to=maik.steuer@gmx.de \
    --cc=g.liakhovetski@gmx.de \
    --cc=kernel@pengutronix.de \
    --cc=video4linux-list@redhat.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 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.