Nicolas Boichat 6e8cbe40ee shared_mem: Assert that shared memory size is large enough ...

We add a configuration option to set the minimum shared memory
size (CONFIG_SHAREDMEM_MINIMUM_SIZE), so that the link will fail
if there is not enough IRAM left.

Also, we add 2 macros around shared_mem_acquire, that check, at
build time, that the shared memory size is sufficient for the
allocation:
 - SHARED_MEM_ACQUIRE_CHECK should be used instead of
   shared_mem_acquire, when size is known in advance.
 - SHARED_MEM_CHECK_SIZE should be used when only a maximum size
   is known.

This does not account for "jump tags" that boards often add on
jump from RO to RW. Luckily, RW usually does not do verification,
and does not need as much shared memory.

BRANCH=none
BUG=chromium:739771
TEST=make buildall -j, no error

Change-Id: Ic4c72938affe65fe8f8bc17ee5111c1798fc536f
Signed-off-by: Nicolas Boichat <drinkcat@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1002713
Reviewed-by: Gwendal Grignou <gwendal@chromium.org>
Reviewed-by: Randall Spangler <rspangler@chromium.org>
Reviewed-by: Vincent Palatin <vpalatin@chromium.org>

2018-05-07 20:45:54 -07:00

..

cortex-m

shared_mem: Assert that shared memory size is large enough

2018-05-07 20:45:54 -07:00

cortex-m0

shared_mem: Assert that shared memory size is large enough

2018-05-07 20:45:54 -07:00

host

cleanup: Remove jtag_pre_init()

2017-09-07 15:01:05 -07:00

minute-ia

stm32/usb: Add HOOK_USB_PM_CHANGE, called when USB is resumed/suspended

2018-02-02 10:17:30 -08:00

nds32

shared_mem: Assert that shared memory size is large enough

2018-05-07 20:45:54 -07:00