Hi Philippe, On Tue, Mar 15, 2016 at 11:14:17AM +0100, Philippe De Muyter wrote: > Hi, > > Sorry if you read the following twice, but the subject of my previous post > was not precise enough :( > > I am in the process of converting a sensor driver compatible with the imx6 > freescale linux kernel, to a subdev driver compatible with a current kernel > and Steve Longerbeam's work. > > My sensor can work at any fps (even fractional) up to 60 fps with its default > frame size or even higher when using crop or "binning'. That fact is reflected > in my previous implemetation of VIDIOC_ENUM_FRAMEINTERVALS, which answered > with a V4L2_FRMIVAL_TYPE_CONTINUOUS-type reply. > > This seem not possible anymore because of the lack of the needed fields > in the 'struct v4l2_subdev_frame_interval_enum' used to delegate the question > to the subdev driver. V4L2_FRMIVAL_TYPE_STEPWISE does not seem possible > anymore either. Has that been replaced by something else or is that > functionality not considered relevant anymorea ? I think the issue was that the CONTINUOUS and STEPWISE were considered too clumsy for applications and practically no application was using them, or at least the need for these was not seen to be there. They were not added to the V4L2 sub-device implementation of the interface as a result. Cc Hans. The smiapp driver uses horizontal and vertical blanking controls for changing the frame rate. That's a bit lower level interface than most drivers use, but then you have to provide enough other information to the user space as well, including the pixel rate. -- Kind regards, Sakari Ailus e-mail: sakari.ailus@xxxxxx XMPP: sailus@xxxxxxxxxxxxxx -- 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
