When extracting the captured frame timestamp in an argus app using getSensorTimestamp() the returned value does not show nanoseconds information (nanoseconds always come as zeroes), values look like:
In contrast, timestamps of the system clock (monotonic raw), and timestamps of frames captured with v4l2 bring nanosecond information. For instance, the system clock timestamps captured in the same argus app as above look like:
My questions are:
Is the ISP using a different clock to timestamp the frames that go through the ISP path, in contrast to v4l2’s RTCPU (Memory controller path)?
Why does the timestamp extracted with getSensorTimestamp() does not have nanosecond information?
Where does this timestamp come from (ISP path)? It does not look to belong to the RTCPU nor the system clock.