On Mon, Aug 08, 2011 at 05:50:06PM +0200, Laurent Pinchart wrote: > Hi everybody, Hi, all! > The V4L2 brainstorming meeting held in Cambourne from August the 1st to August > the 5th was a success. I would like to thank Linaro again, and particularly > Stephen Doel and Arwen Donaghey, for accommodating us during the whole week. > > Here is a summary of the discussions, with preliminary conclusions, ideas, and > action points. Thanks for the notes! ... > Pixel clock and blanking > ------------------------ > > Preliminary conclusions: > > - Pixel clock(s) and blanking will be exported through controls on subdev > nodes. > - The pixel array pixel clock is needed by userspace. > - Hosts/bridges/ISPs need pixel clock and blanking information to validate > pipelines. I have a small addition to this in my notes: Pixel array and bus configuration for sensors --------------------------------------------- The CSI-2 bus frequency will receive an integer menu control. Together with the binning, skipping, scaling and CSI-2 output bits-per-pixel information, this allows the sensor driver to calculate the value of the "best pixel rate" in the sensor, which will be a read-only int64 control. Based on pixel clock, image width, height and ranges on vertical and horizontal blanking, the user can define the frame rate. Vertical and horizontal blanking are implemented as integer controls. Integer menu controls are easy to add; this will be implemented by making the name field in v4l2_querymenu an anonymous union. (I actually have patches for this but haven't tested them yet. I'll send them once I have time for that.) Cheers, -- 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