Re: Asking advice for Camera/ISP driver framework design

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

 



On Fri, Sep 16, 2011 at 1:14 AM, Sakari Ailus <sakari.ailus@xxxxxx> wrote:
> Cliff Cai wrote:
>> Dear guys,
>
> Hi Cliff,
>
>> 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.
>
> Is the ISP able to process images which already are in memory, or is
> this only from the sensor?

yes,it has another DMA to achieve  this.

Cliff

>> 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?
>
> Regards,
>
> --
> Sakari Ailus
> sakari.ailus@xxxxxx
>
--
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