zephyr/soc/xtensa
Andy Ross f4a0ea7b43 soc/intel_adsp: Correct errant ATOMCTL
This got broken during the cpu_init unification pass.  I appear to
have copied that zero out of code that initialized Zephyr on a
uniprocessor config somewhere.  But what it means is that any use of
the S32C1I instruction to store to any memory type will trap an
exception!  And even when CONFIG_MP_NUM_CPUS==1, we will emit code to
do that in the atomics layer when SMP=y.

That configuration ("SMP" with 1 cpu) is actually exercised by some
tests, including important ones like timer_api.  These got broken.
Fix.

Really it's never correct to have anything but 1:1:1 ("external RCW
transaction") on these CPUs.  All Intel cAVS processors have hardware
atomics support.  We owe it to all the code we'll run to make sure it
works as documented and doesn't explode.

Signed-off-by: Andy Ross <andrew.j.ross@intel.com>
2022-01-05 15:01:45 -05:00
..
esp32 soc: esp32: add support to mcuboot build 2021-12-18 07:20:38 -05:00
esp32s2 soc: esp32s2: fix: data cache setup 2021-12-03 16:45:16 -06:00
intel_adsp soc/intel_adsp: Correct errant ATOMCTL 2022-01-05 15:01:45 -05:00
intel_s1000 soc: xtensa: cavs-link.ld: add *(.trace_ctx) sections 2021-12-22 17:47:21 -06:00
nxp_adsp soc: xtensa: cavs-link.ld: add *(.trace_ctx) sections 2021-12-22 17:47:21 -06:00
sample_controller debug: coredump: add xtensa coredump 2021-12-14 07:40:55 -05:00
CMakeLists.txt