Zephyr has prefixed all of its includes with <zephyr/...>. While the old
mode can still be used (CONFIG_LEGACY_INCLUDE_PATH) and is still enabled
by default, it's better to be prepared for its removal in the future.
Signed-off-by: Gerard Marull-Paretas <gerard@teslabs.com>
The return value should be negative.
Added inclusion of errno.h to avoid an unresolved symbol
error when linking the test.
Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>
As Zephyr's IRQ infrastructure is not lined up with libmetal
IRQ infrastructure. And the drivers in Zephyr declare ISR
at compile time, we can have libmetal IRQ handling on top of
of Zephyr, but it will introduce unnecessary overhead.
Signed-off-by: Wendy Liang <wendy.liang@xilinx.com>
The IRQ registration API has been updated to support single
handler per IRQ. The IRQ test is updated for this change.
Signed-off-by: Wendy Liang <wendy.liang@xilinx.com>
Now that we have a a zephyr specific METAL_INIT_DEFAULTS we can just
use the default param passed to metal_init like all the other systems do
rather than specifying a unique metal_params to Zephyr. This gets the
Zephyr logger used for output.
Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
There are assumptions that one could directly assign a value to init a
mutex which shouldn't be made. Instead we should use the
metal_mutex_init call to setup the mutex. Also for static or global
defines of a mutex we need a way to set them up. So we introduce
METAL_MUTEX_DEFINE(m) for that case.
Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
Gerard Marull-Paretas
Luz Paz
Arnaud Pouliquen
Arnaud Pouliquen
Wendy Liang
Wendy Liang
Kumar Gala
Kristian Klomsten Skordal