Thanks for the hints. I tried the suggested branch adding omap3isp data to the Overo device tree and device tree bindings for the mt9v032 device. I needed to manually modprobe omap3-isp but the camera was registered and I was able to use media-ctl to manipulate the v4l2 pipeline. I wasn't able to stream as v4l2 was reporting "inappropriate ioctl"----old driver perhaps? I also tried changing the #define HIST_CONFIG_DMA 0 such that the histogram block uses PIO instead of using the deprecated omap_request_dma. I saw basically the same behaviour. What would be the correct/modern way to use DMA here? --Ash On Tue, Jan 6, 2015 at 2:11 PM, Sakari Ailus <sakari.ailus@xxxxxx> wrote: > (Fixed Laurent's e-mail.) > > Moikka, > > On Tue, Jan 06, 2015 at 01:42:18PM -0800, Tony Lindgren wrote: >> * Ash Charles <ashcharles@xxxxxxxxx> [150106 12:45]: >> > Hi, >> > >> > I'm playing with the Caspa camera (mt9v032) and Overo on the 3.17 >> > kernel. It looks like there has been some work on dt-bindings for the >> > omap3isp (notably [1] and [2]) but I didn't see anything heading for >> > mainline. >> > >> > What would be needed to support cameras using the omap3isp in a mainline kernel? >> >> No idea about the camera, but at least the legacy omap DMA calls need >> to be replaced or removed as the legacy DMA API will go away soon. > > OMAP DMA is only used by the histogram block which can cope with PIO as well > --- I think there at least was a #define for it. That's not a reason not to > convert it however, it's just not as urgent it otherwise might be. I wonder > if someone has patches for that already. > > Cc Laurent. > > -- > Terveisin, > > Sakari Ailus > e-mail: sakari.ailus@xxxxxx XMPP: sailus@xxxxxxxxxxxxxx -- 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
