Aurelien Jarno 992f29a1bc arch: make __ramfunc support transparent ... Instead of having to enable ramfunc support manually, just make it transparently available to users, keeping the MPU region disabled if not used to not waste a MPU region. This however wastes 24 bytes of code area when the MPU is disabled and 48 bytes when it is enabled, and probably a dozen of CPU cycles during boot. I believe it is something acceptable. Note that when XIP is used, code is already in RAM, so the __ramfunc keyword does nothing, but does not generate an error. Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>		2019-02-22 11:36:50 -08:00
..
include
atomic_c.c
CMakeLists.txt
compiler_stack_protect.c
device.c
errno.c
idle.c
init.c	arch: make __ramfunc support transparent	2019-02-22 11:36:50 -08:00
int_latency_bench.c
Kconfig	arch: make __ramfunc support transparent	2019-02-22 11:36:50 -08:00
Kconfig.power_mgmt
mailbox.c
mem_domain.c
mem_slab.c
mempool.c
msg_q.c
mutex.c
pipes.c
poll.c
queue.c
sched.c
sem.c
smp.c
stack.c
system_work_q.c
thread_abort.c
thread.c
timeout.c
timer.c
userspace_handler.c
userspace.c
version.c
work_q.c