lib: kconfig: Limit BINMAN_FDT for OF_SEPARATE or OF_EMBED

Generally speaking BINMAN_FDT makes sense for OF_SEPARATE or OF_EMBED.
For the other OF_CONTROL methods, it's quite possible binman node is
not available as binman is invoked during the build phase instead of
runtime. Let's only turn it on for OF_SEPARATE or OF_EMBED by default.

Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: Simon Glass <sjg@chromium.org>

diff --git a/lib/Kconfig b/lib/Kconfig
index b057b9d73bc208a86dad6eb68bb5096716dba79f..d675ab1d8267cbb01d43ee413edc09f5714d6a2e 100644 (file)
--- a/lib/Kconfig
+++ b/lib/Kconfig
@@ -25,7 +25,7 @@ config BCH
 config BINMAN_FDT
        bool "Allow access to binman information in the device tree"
        depends on BINMAN && DM && OF_CONTROL
-       default y
+       default y if OF_SEPARATE || OF_EMBED
        help
          This enables U-Boot to access information about binman entries,
          stored in the device tree in a binman node. Typical uses are to