Hello, fail or success in registering these subdevs depend on the sensor code probe() function (at least I think so). When the isp already mentions your driver name saa7113 check your saa7113 driver code and see what can fail in the probe function and add some debug output. Probably the i2c communication doesn't work, but I do not know the code. good luck, Bastian 2011/2/24 Loïc Akue <akue.loic@xxxxxxxxx>: > > Hello Bastian, > > As a newbie in kernel development, I'm facing the same issue about subdev > registration. > I'm trying to capture some raw video from a SAA7113 connected to the ISP of an > omap3530. May I please have your help with this problem? > > root@cm-t35:~# modprobe iommu > [ 8409.776123] omap-iommu omap-iommu.0: isp registered > > root@cm-t35:~# modprobe omap3_isp > [ 8451.821533] omap3isp omap3isp: Revision 2.0 found > [ 8451.827056] omap-iommu omap-iommu.0: isp: version 1.1 > [ 8453.291992] isp_register_subdev_group: Unable to register subdev saa7113 > > Regards > > Loïc Akue > > -- > 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 > -- 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