Hi Laurent,
On 09/25/2012 02:35 AM, Laurent Pinchart wrote:
Does the clock type need to be selectable for mem-to-mem devices ? Do device-
specific timestamps make sense there ?
I'd like to clarify one thing here, i.e. if we select device-specific
timestamps how should the v4l2_buffer::timestamp field behave ?
Are these two things exclusive ? Or should v4l2_buffer::timestamp be
valid even if device-specific timestamps are enabled ?
With regards to your question, I think device-specific timestamps make
sense for mem-to-mem devices. Maybe not for the very simple ones, that
process buffers 1-to-1, but codecs may need it. I was told the Exynos/
S5P Multi Format Codec device has some register the timestamps could
be read from, but it's currently not used by the s5p-mfc driver. Kamil
might provide more details on that.
I guess if capture and output devices can have their timestamping clocks
selectable it should be also possible for mem-to-mem devices.
--
Regards,
Sylwester
--
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
