post: Migrate to Kconfig
We move the existing CONFIG_POST_* functionality over to CFG_POST and
then introduce CONFIG_POST to Kconfig.
Signed-off-by: Tom Rini <trini@konsulko.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
diff --git a/doc/README.POST b/doc/README.POST
index 1d1c25b..5d92f3f 100644
--- a/doc/README.POST
+++ b/doc/README.POST
@@ -242,11 +242,11 @@
All POST-related code will be #ifdef'ed with the CONFIG_POST macro.
This macro will be defined in the config_<board>.h file for those
-boards that need POST. The CONFIG_POST macro will contain the list of
+boards that need POST. The CFG_POST macro will contain the list of
POST tests for the board. The macro will have the format of array
composed of post_test structures:
-#define CONFIG_POST \
+#define CFG_POST \
{
"On-board peripherals test", "board", \
" This test performs full check-up of the " \
@@ -257,7 +257,7 @@
A new file, post.h, will be created in the include/ directory. This
file will contain common POST declarations and will define a set of
-macros that will be reused for defining CONFIG_POST. As an example,
+macros that will be reused for defining CFG_POST. As an example,
the following macro may be defined:
#define POST_CACHE \
diff --git a/doc/README.fsl-ddr b/doc/README.fsl-ddr
index cec5d94..10e63f3 100644
--- a/doc/README.fsl-ddr
+++ b/doc/README.fsl-ddr
@@ -137,7 +137,7 @@
2. Memory test can be done with Power-On-Self-Test function, activated at
compile time.
- In order to enable the POST memory test, CONFIG_POST needs to be
+ In order to enable the POST memory test, CFG_POST needs to be
defined in board configuraiton header file. By default, POST memory test
performs a fast test. A slow test can be enabled by changing the flag at
compiling time. To test memory bigger than 2GB, 36BIT support is needed.