aro.org] On Behalf Of EXT
Ivan Khoronzhuk
Sent: Thursday, November 12, 2015 7:45 PM
To: lng-odp@lists.linaro.org
Subject: [lng-odp] [lng] [API-NEXT PATCH v2 7/7] api: time: make local
time to be wall time
It's more convenient the local time to be a wall time. It's allows
to measure time
should be able to handle both equally if it is defined to start from
0 and never wrap.
-Petri
-Original Message-
From: lng-odp [mailto:lng-odp-boun...@lists.linaro.org] On Behalf Of EXT
Ivan Khoronzhuk
Sent: Thursday, November 12, 2015 7:45 PM
To: lng-odp@lists.linaro.org
Subject: [lng-odp
015 7:45 PM
> To: lng-odp@lists.linaro.org
> Subject: [lng-odp] [lng] [API-NEXT PATCH v2 7/7] api: time: make local
> time to be wall time
>
> It's more convenient the local time to be a wall time. It's allows
> to measure time beginning from start of the thread. This al
ping.
On 13.11.15 11:28, Ivan Khoronzhuk wrote:
Petri,
Additional API calls like resolution and delay can be added after this patch.
The global API can be added after this patch and it will be absolutely similar
except global time source (in linux-generic it's the same source).
I've added this
Petri,
Additional API calls like resolution and delay can be added after this patch.
The global API can be added after this patch and it will be absolutely similar
except global time source (in linux-generic it's the same source).
I've added this patch separately (not considering that series bec
It's more convenient the local time to be a wall time. It's allows
to measure time beginning from start of the thread. This allows to use
local time in similar manner as it's supposed to be used with global
time and the 64-bit timer is enough to guarantee it.
Correct validation test to check new ti