On Mon, Oct 21, 2019 at 3:48 AM Philipp Zabel <p.zabel@xxxxxxxxxxxxxx> wrote: > > Hi Adam, Fabio, > > On Fri, 2019-10-18 at 16:00 -0300, Fabio Estevam wrote: > > Hi Adam, > > > > Adding Steve and Philipp in case they can help. > > > > On Tue, Oct 15, 2019 at 1:52 AM Adam Ford <aford173@xxxxxxxxx> wrote: > > > I have an i.MX6Q with an ov5640 connected to the mipi-csi2 interface. > > > > > > I am routing ov5640 -> ipu1_csi0_mux -> ip1_csi0 -> ip1_csi0 capture. > > > > > > I am trying to go through the steps to attempt to get 60fps at > > > 640x480, but the best I can appear to acheive is 30fps. > > > > > > > > > v4l2-ctl --all > > > > > > Streaming Parameters Video Capture: > > > Capabilities : timeperframe > > > Frames per second: 30.000 (30/1) > > > Read buffers : 0 > > > > > > I have tried setting both the ov5640 and the ipu1_csi0 to 1/60 without success. > > > > > > Can someone tell me if it's even possible on this platform? When I > > > stream the video to the HDMI monitor, I am only using 3% of the ARM, > > > so I don't think it's processor limited. > > That should be possible. The sensor and dual-lane CSI-2 link can support > 1920x1080p30 or 1280x720p60, only the driver currently limits 60 fps > capture to 640x480. Is that an artificial limit? Looking through the driver, it appears to do more and more automatic calcuations to determine pixel and frame rate. I wonder how hard it would be > > The format has to be propagated through the media control graph from the > sensor to the capture device. Since the CSI-2 receiver and multiplexers > are not frame rate aware, the CSI has to be told the correct frame > interval at its input. > > What does your configuration look like? I'd expect something like: > > media-ctl --set-v4l2 "'ov5640 ?-00??':0[fmt:UYVY8_1X16/640x480@1/60]" > media-ctl --set-v4l2 "'imx6-mipi-csi2':1[fmt:UYVY8_1X16/640x480]" > media-ctl --set-v4l2 "'ipu1_csi0_mux':2[fmt:UYVY8_1X16/640x480]" > media-ctl --set-v4l2 "'ipu1_csi0':0[fmt:UYVY8_1X16/640x480@1/60]" > media-ctl --set-v4l2 "'ipu1_csi0':2[fmt:AYUV32/960x540@1/60]" Thanks for the suggestion. I was missing the entry for "'ipu1_csi0':0 I only listed the "'ipu1_csi0':2 It's working now. Sorry for the noise. adam > > What is the output of "media-ctl --print-topology"? > > regards > Philipp >
