On Tue, Mar 29, 2011 at 8:32 AM, Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx> wrote: > I think that Sakari's patches correcty fix the problems he noticed. However, > they won't fix one basic issue, which is that the iommu2 module won't be > automatically pulled in when the omap3isp module is loaded. The omap3isp > driver will then fail to probe the device. That's better than crashing though. > > One possible solution for that is to turn the tristate option for iommu2 into > a bool option. I've also read a couple of times that the kernel provides a > standard iommu API. Maybe switching to it would help. I'm attempting to get support for the Gumstix Caspa image sensor (based on mt9v032) working with the 3.0 release. I'm running into the issue described above -- the omap3-isp module loads but fails to probe the device. I've tried the tristate->bool option change and find that it does allow me to proceed further, but the omap3-isp module is no longer loaded automatically when I call omap3_init_camera in the board file. I have to manually modprobe it. I then see the sensor module successfully probed and the video devices created (though not functioning yet). Are you aware of a better way to do this? I see lots of patches for iommu since this thread. Would I be better off waiting for 3.1 and trying that, or will final resolution of this issue come even later? Best regards, Steve -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
