i.MX timers can't handle timeouts in the past or too far into the future

[philipderrin]

The i.MX timer's set_timeout function converts absolute times to relative without checking that the time is in the future. This leads to an attempt to set a very large relative timeout instead of returning ETIME.

util_libs/libplatsupport/src/mach/imx/ltimer.c

Line 122 in 8d89181

if (type == TIMEOUT_ABSOLUTE) {

Also, non-periodic relative timeouts that are too far into the future for a 32-bit timer should saturate to 0xffffffff so that the timeout is received early, rather than returning EINVAL.

The omap version of set_timeout handles both of these cases; I think the code can simply be copied from there.

util_libs/libplatsupport/src/mach/omap/ltimer.c

Line 94 in 8d89181

static int set_timeout(void *data, uint64_t ns, timeout_type_t type)