V4L2 runs out of memory when OMAP3 ISP parallel pixel clock is high

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

 



I am running a DM3730 connected to an mt9p031 sensor, and the ISP is
running in 8-bit parallel mode.

I have the sensor endpoint configured as:

mt9p031_out: endpoint {
     input-clock-frequency = <24000000>;
     pixel-clock-frequency = <72000000>;
     remote-endpoint = <&ccdc_ep>;
};

I was looking through the datasheet, and it appears as if the pixel
clock frequency can go up to 96MHz, so I tried to increase the
pixel-clock-frequency to 96MHz, but v4l2 seems to get an out of memory
error.

libv4l2: error turning on stream: No space left on device
ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Failed
to allocate required memory.
Additional debug info:
gstv4l2src.c(658): gst_v4l2src_decide_allocation ():
/GstPipeline:pipeline0/GstV4l2Src:v4l2src0:
Buffer pool activation failed
Execution ended after 0:00:00.019073486

Through trial and error, I was able to get push the sensor's
pixel-clock-frequency to work at 90MHz, but no higher.  I have also
tried experimenting with the input clock frequency without success.

If I can get the clock to run at 96MHz, which the ISP and sensor
documentation appears to permit, I am hoping to be able to achieve a
little higher frame rate.

Is there something I need to do to allocate more memory to V4L2 or is
there some other limitation causing the out of memory at higher pixel
clock frequencies?


thank you,

adam



[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