Aguirre, Sergio wrote: > Hi, Hi Sergio, > I was wondering if there exists a current standard way to query a > Imaging sensor driver for knowing things like the signal vert/horz blanking time. > > In an old TI custom driver, we used to have a private IOCTL in the sensor > Driver we interfaced with the omap3 ISP, which was basically reporting: > > - Active resolution (Actual image size) > - Full resolution (Above size + dummy pixel columns/rows representing blanking times) > > However I resist to keep importing that custom interface, since I think its > Something that could be already part of an standard API. The N900 sensor drivers currently use private controls for this purpose. That is an issue which should be resolved. I agree there should be a uniform, standard way to access this information. What we currently have is this, not in upstream: --- /* SMIA-type sensor information */ #define V4L2_CID_MODE_CLASS_BASE (V4L2_CTRL_CLASS_MODE | 0x900) #define V4L2_CID_MODE_CLASS (V4L2_CTRL_CLASS_MODE | 1) #define V4L2_CID_MODE_FRAME_WIDTH (V4L2_CID_MODE_CLASS_BASE+1) #define V4L2_CID_MODE_FRAME_HEIGHT (V4L2_CID_MODE_CLASS_BASE+2) #define V4L2_CID_MODE_VISIBLE_WIDTH (V4L2_CID_MODE_CLASS_BASE+3) #define V4L2_CID_MODE_VISIBLE_HEIGHT (V4L2_CID_MODE_CLASS_BASE+4) #define V4L2_CID_MODE_PIXELCLOCK (V4L2_CID_MODE_CLASS_BASE+5) #define V4L2_CID_MODE_SENSITIVITY (V4L2_CID_MODE_CLASS_BASE+6) --- The pixel clock is read-only but some of the others should likely be changeable. Regards, -- Sakari Ailus sakari.ailus@xxxxxxxxxxxxxxxxxxxxxxxxxx -- 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
