Re: omap3-isp: can't register subdev for new sensor driver mt9t001

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Loic,

in my last post, make sure you return a v4l2_mbus_framefmt structure
that contain yuv 720x480. Else the framework thinks your driver cannot
supply this format. I do not know the exact enums myself, try to grep
it in the linux kernel includes.
In my test driver I added a printk(KERN_ALERT "blabla"); to all subdev
calls to see when the framework calls which functions.

good luck,

Bastian



2011/3/2 Loïc Akue <akue.loic@xxxxxxxxx>:
> Hi Bastien,
>
> Me again =)
> Thank you for your previous reply. I added some code, so my saa7113 drivers
> could be compatible with the new media framework.
> But I still can get some video data, from my sub-device. I saw in a mailing
> list that you had a similar issue, could you please help me on this?
>
> root@cm-t35:~# ./media-ctl -r -l '"saa7115 3-0024":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]
>
> My first problem appears when I try to configure my pads before trying to
> capture
>
> ************************************************************************************************
> root@cm-t35:~# ./media-ctl -f '"saa7115 3-0024":0[UYVY 720x480], "OMAP3 ISP
> CCDC":2[UYVY 720x480]'
>
> Setting up format UYVY 720x480 on pad saa7115 3-0024/0
> Format set: UYVY 720x480
> Setting up format UYVY 720x480 on pad OMAP3 ISP CCDC/0
> Format set: SGRBG10 720x480
> Setting up format UYVY 720x480 on pad OMAP3 ISP CCDC/2
> Format set: SGRBG10 720x479
>
> Setting up format SGRBG10 720x479 on pad OMAP3 ISP AEWB/0
> Unable to set format: Invalid argument (-22)
> Setting up format SGRBG10 720x479 on pad OMAP3 ISP AF/0
> Unable to set format: Invalid argument (-22)
> Setting up format SGRBG10 720x479 on pad OMAP3 ISP histogram/0
> Unable to set format: Invalid argument (-22)
> ************************************************************************************************
> Then, when I run this yavta command :
> ************************************************************************************************
> root@cm-t35:~# ./yavta -f UYVY -s 720x480 -n 4 --capture=4 --skip 3 -F
> $(./media
> -ctl -e "OMAP3 ISP CCDC output")
>
> Device /dev/video2 opened: OMAP3 ISP CCDC output (media).
> Video format set: width: 720 height: 480 buffer size: 691200
> Video format: UYVY (59565955) 720x480
> 4 buffers requested.
> length: 691200 offset: 0
> Buffer 0 mapped at address 0x40306000.
> length: 691200 offset: 692224
> Buffer 1 mapped at address 0x40417000.
> length: 691200 offset: 1384448
> Buffer 2 mapped at address 0x404d1000.
> length: 691200 offset: 2076672
> Buffer 3 mapped at address 0x405ed000.
> Unable to start streaming: 22.
> ************************************************************************************************
> And the system hangs.
> Do you have any idea where to look?
>
> Regards
>
> Loïc
>
--
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


[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux