Hello Laurent > Could you elaborate a bit on that last point ? What kind of timestamps would > you need, and what are the use cases ?
Right now we only have one timestamp field on the buffer structure, it might be a good idea to leave space for some more. My user case is a camera that is recording a conveyor belt at a very high frame rate. Instead of tracking the objects on the image with I use one or more encoders on the belt. The encoder count is read on vsync and kept it on a register(s). When an image is ready, the cpu starts the dma and read this "belt timestamps" registers. It would be nice to have an standard way to expose this alternative timestamps or at least find out if I am the only one with this issue and/or how you have solve it :) Best regards! -- Ricardo Ribalda -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
