config.h: clarify CONFIG_INTERNAL_STORAGE semantics

The semantics in the EC code base are that CONFIG_INTERNAL_STORAGE
implies eXecute-In-Place semantics (XIP). Add a comment to make that
abundantly clear.

BUG=none
BRANCH=none
TEST=none

Change-Id: I80152eeb41dd35716f4c09ffd1753ae128aa7d2d
Signed-off-by: Aaron Durbin <adurbin@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/995956
Reviewed-by: Vincent Palatin <vpalatin@chromium.org>
This commit is contained in:
Aaron Durbin
2018-04-04 09:18:39 -06:00
committed by chrome-bot
parent a26f7241f5
commit 5d8a4ba6f2

View File

@@ -1235,7 +1235,9 @@
/*
* EC code can reside on internal or external storage. Only one of these
* CONFIGs should be defined.
* CONFIGs should be defined. CONFIG_INTERNAL_STORAGE implies XIP
* (eXecute-In-Place) semantics. i.e. code is being fetched directly from
* storage media.
*/
#undef CONFIG_EXTERNAL_STORAGE
#undef CONFIG_INTERNAL_STORAGE