arch: added support for the riscv32 architecture
RISC-V is an open-source instruction set architecture.
Added support for the 32bit version of RISC-V to Zephyr.
1) exceptions/interrupts/faults are handled at the architecture
level via the __irq_wrapper handler. Context saving/restoring
of registers can be handled at both architecture and SOC levels.
If SOC-specific registers need to be saved, SOC level needs to
provide __soc_save_context and __soc_restore_context functions
that shall be accounted by the architecture level, when
corresponding config variable RISCV_SOC_CONTEXT_SAVE is set.
2) As RISC-V architecture does not provide a clear ISA specification
about interrupt handling, each RISC-V SOC handles it in its own
way. Hence, at the architecture level, the __irq_wrapper handler
expects the following functions to be provided by the SOC level:
__soc_is_irq: to check if the exception is the result of an
interrupt or not.
__soc_handle_irq: handle pending IRQ at SOC level (ex: clear
pending IRQ in SOC-specific IRQ register)
3) Thread/task scheduling, as well as IRQ offloading are handled via
the RISC-V system call ("ecall"), which is also handled via the
__irq_wrapper handler. The _Swap asm function just calls "ecall"
to generate an exception.
4) As there is no conventional way of handling CPU power save in
RISC-V, the default nano_cpu_idle and nano_cpu_atomic_idle
functions just unlock interrupts and return to the caller, without
issuing any CPU power saving instruction. Nonetheless, to allow
SOC-level to implement proper CPU power save, nano_cpu_idle and
nano_cpu_atomic_idle functions are defined as __weak
at the architecture level.
Change-Id: I980a161d0009f3f404ad22b226a6229fbb492389
Signed-off-by: Jean-Paul Etienne <fractalclone@gmail.com>
2017-01-11 07:24:30 +08:00
|
|
|
/*
|
|
|
|
|
* Copyright (c) 2016 Jean-Paul Etienne <fractalclone@gmail.com>
|
|
|
|
|
*
|
2017-01-19 09:01:01 +08:00
|
|
|
* SPDX-License-Identifier: Apache-2.0
|
arch: added support for the riscv32 architecture
RISC-V is an open-source instruction set architecture.
Added support for the 32bit version of RISC-V to Zephyr.
1) exceptions/interrupts/faults are handled at the architecture
level via the __irq_wrapper handler. Context saving/restoring
of registers can be handled at both architecture and SOC levels.
If SOC-specific registers need to be saved, SOC level needs to
provide __soc_save_context and __soc_restore_context functions
that shall be accounted by the architecture level, when
corresponding config variable RISCV_SOC_CONTEXT_SAVE is set.
2) As RISC-V architecture does not provide a clear ISA specification
about interrupt handling, each RISC-V SOC handles it in its own
way. Hence, at the architecture level, the __irq_wrapper handler
expects the following functions to be provided by the SOC level:
__soc_is_irq: to check if the exception is the result of an
interrupt or not.
__soc_handle_irq: handle pending IRQ at SOC level (ex: clear
pending IRQ in SOC-specific IRQ register)
3) Thread/task scheduling, as well as IRQ offloading are handled via
the RISC-V system call ("ecall"), which is also handled via the
__irq_wrapper handler. The _Swap asm function just calls "ecall"
to generate an exception.
4) As there is no conventional way of handling CPU power save in
RISC-V, the default nano_cpu_idle and nano_cpu_atomic_idle
functions just unlock interrupts and return to the caller, without
issuing any CPU power saving instruction. Nonetheless, to allow
SOC-level to implement proper CPU power save, nano_cpu_idle and
nano_cpu_atomic_idle functions are defined as __weak
at the architecture level.
Change-Id: I980a161d0009f3f404ad22b226a6229fbb492389
Signed-off-by: Jean-Paul Etienne <fractalclone@gmail.com>
2017-01-11 07:24:30 +08:00
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#include <irq.h>
|
|
|
|
|
#include <irq_offload.h>
|
|
|
|
|
#include <misc/printk.h>
|
|
|
|
|
|
|
|
|
|
volatile irq_offload_routine_t _offload_routine;
|
|
|
|
|
static volatile void *offload_param;
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Called by _enter_irq
|
|
|
|
|
*
|
|
|
|
|
* Just in case the offload routine itself generates an unhandled
|
|
|
|
|
* exception, clear the offload_routine global before executing.
|
|
|
|
|
*/
|
|
|
|
|
void _irq_do_offload(void)
|
|
|
|
|
{
|
|
|
|
|
irq_offload_routine_t tmp;
|
|
|
|
|
|
|
|
|
|
if (!_offload_routine)
|
|
|
|
|
return;
|
|
|
|
|
|
|
|
|
|
tmp = _offload_routine;
|
|
|
|
|
_offload_routine = NULL;
|
|
|
|
|
|
|
|
|
|
tmp((void *)offload_param);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
void irq_offload(irq_offload_routine_t routine, void *parameter)
|
|
|
|
|
{
|
|
|
|
|
int key;
|
|
|
|
|
|
|
|
|
|
key = irq_lock();
|
|
|
|
|
_offload_routine = routine;
|
|
|
|
|
offload_param = parameter;
|
|
|
|
|
|
|
|
|
|
__asm__ volatile ("ecall");
|
|
|
|
|
|
|
|
|
|
irq_unlock(key);
|
|
|
|
|
}
|