Re: Minimum timing resolution in Ubuntu/Linaro on the PandaBoard ES

On Tue, 2012-02-07 at 21:21 -0800, Dmitry Antipov wrote:

BTW, I have no ideas why clock_getres(CLOCK_REALTIME,...) returns {0, 1} regardless of underlying clock source. I expect {0, 30517} for 32K timer and {0, 26} for MPU timer.

Yea. I had proposed to export the underlying clocksource's resolution via clock_getres, but it was argued against. The concern is that applications might not expect clock_getres to change while the application is running. Between any clock_getres() call and a time read, the clocksources could change.

But if someone has a different reading of the posix spec, it might be good to revisit this.

thanks -john