2011/9/14 Cliff Cai <cliffcai.sh@xxxxxxxxx>: > Dear guys, > > I'm currently working on a camera/ISP Linux driver project.Of course,I > want it to be a V4L2 driver,but I got a problem about how to design > the driver framework. > let me introduce the background of this ISP(Image signal processor) a > little bit. > 1.The ISP has two output paths,first one called main path which is > used to transfer image data for taking picture and recording,the other > one called preview path which is used to transfer image data for > previewing. > 2.the two paths have the same image data input from sensor,but their > outputs are different,the output of main path is high quality and > larger image,while the output of preview path is smaller image. > 3.the two output paths have independent DMA engines used to move image > data to system memory. > > The problem is currently, the V4L2 framework seems only support one > buffer queue,and in my case,obviously,two buffer queues are required. > Any idea/advice for implementing such kind of V4L2 driver? or any > other better solutions? > > Thanks a lot! > Cliff > -- > 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 > Your chip seems like davinci isp, only difference is dma. So you can reference davinci drivers. If dma interrupt doesn't happen at the same time, I guess you must wait because source image is the same. Scott -- 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
