Hi Guennadi,
Guennadi Liakhovetski wrote:
On Thu, 30 Jul 2009, Valentin Longchamp wrote:
Hi Guennadi,
Guennadi Liakhovetski wrote:
Hi all
here goes a new iteration of the soc-camera scaling / cropping API
compliance fix. In fact, this is only the first _complete_ one, the previous
version only converted one platform - i.MX31 and one camera driver -
MT9T031. This patch converts all soc-camera drivers. The most difficult one
is the SuperH driver, since it is currently the only host driver
implementing own scaling and cropping on top of those of sensor drivers. The
first three patches in the series are purely cosmetic, unifying device
objects, used in dev_dbg, dev_info... functions. These patches extend the
patch series uploaded at
http://download.open-technology.de/soc-camera/20090701/ with the actual
scaling / cropping patch still in
http://download.open-technology.de/testing/. The series is still based on
the git://git.pengutronix.de/git/imx/linux-2.6.git (now gone) for-rmk
branch, but the i.MX31 patches, that my patch-series depends on, are now in
the mainline, so, I will be rebasing the stack soon. In the meantime, I'm
afraid, it might require some fiddling to test the stack.
I'd love to give your patches a try. But the fiddling looks very hard for me
... patch 0010 does not apply correctly for me, and a 130K patch to do by hand
is .. looooong.
Ok, a rebased patch set is under
http://download.open-technology.de/soc-camera/20090730/
now based on 2.6.31-rc4. Notice, all patches are now in the above
directory, .../testing is empty again.
I have some feedback with your patches. I have tried to add support for
my platform by doing the same as you did for pcm037. However it does not
work. I have applied your patches directly on 2.6.31-rc4.
The first problem is that in order to be able to probe the camera
correctly, I cannot have mt9t031 built as module and not loaded at this
time. This certainly is not critcal for the time being, but it should be
handled correctly later (the error comes from
v4l2_i2c_new_subdev_board -called from soc_camera_init_i2c - that does
not create the subdev with the module not loaded - kernel boot).
The second and bigger problem is that even if I can register everything
on the system (/dev/video0 gets created), when I try to access it, I get
a device or resourse busy error.
Kernel log (end):
Freescale High-Speed USB SOC Device Controller driver (Apr 20, 2007)
Platform driver 'fsl-usb2-udc' needs updating - please use dev_pm_ops
i2c /dev entries driver
Linux video capture interface: v2.00
camera 0-0: Probing 0-0
mx3-camera mx3-camera.0: MX3 Camera driver attached to camera 0
mt9t031 0-005d: Detected a MT9T031 chip ID 1621
mx3-camera mx3-camera.0: MX3 Camera driver detached from camera 0
i.MX SDHC driver
i.MX SDHC driver
TCP cubic registered
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 2
Waiting for root device /dev/mmcblk0p1...
mmc0: new SD card at address b368
mmcblk0: mmc0:b368 NCard 1.85 GiB
mmcblk0: p1
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem) on device 179:1.
Freeing init memory: 100K
root@mx31moboard:~# ./gst.sh
Setting pipeline to PAUSED ...
mx3-camera mx3-camera.0: MX3 Camera driver attached to camera 0
mx3-camera mx3-camera.0: MX3 Camera driver detached from camera 0
ERROR: Pipeline doesn't want to pause.
ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Could not open .
Additional debug info:
v4l2_calls.c(477): gst_v4l2_open (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0:
system error: Device or resource busy
Setting pipeline to NULL ...
Freeing pipeline ...
I have noticed that using the old way of doing the things (without
v4lsubdev support, using some code that works with 2.6.30), it does not
work either with 2.6.31-rc4 (same device or resource busy). So maybe am
I missing something here already. Here is the "log":
root@mx31moboard:~# insmod modules/mt9t031.ko
camera 0-0: MX3 Camera driver attached to camera 0
camera 0-0: Detected a MT9T031 chip ID 1621
camera 0-0: MX3 Camera driver detached from camera 0
root@mx31moboard:~# camera 0-0: MX3 Camera driver attached to camera 0
camera 0-0: MX3 Camera driver detached from camera 0
root@mx31moboard:~# ./gst.sh
Setting pipeline to PAUSED ...
camera 0-0: MX3 Camera driver attached to camera 0
camera 0-0: MX3 Camera driver detached from camera 0
ERROR: Pipeline doesn't want to pause.
ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Could not open .
Additional debug info:
v4l2_calls.c(477): gst_v4l2_open (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0:
system error: Device or resource busy
Setting pipeline to NULL ...
Freeing pipeline ...
Best Regards
Val
--
Valentin Longchamp, PhD Student, EPFL-STI-LSRO1
valentin.longchamp@xxxxxxx, Phone: +41216937827
http://people.epfl.ch/valentin.longchamp
MEA3485, Station 9, CH-1015 Lausanne
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
