ARM: dts: armada-385-turris-omnia: rename node in -u-boot.dtsi file

[platform/kernel/u-boot.git] / dts / Kconfig

diff --git a/dts/Kconfig b/dts/Kconfig
index 64c98dd..71f5055 100644 (file)
--- a/dts/Kconfig
+++ b/dts/Kconfig
@@ -25,6 +25,7 @@ menu "Device Tree Control"
 config OF_CONTROL
        bool "Run-time configuration via Device Tree"
        select DTC
+       select OF_LIBFDT if !OF_PLATDATA
        help
          This feature provides for run-time configuration of U-Boot
          via a flattened device tree.
@@ -42,6 +43,7 @@ config OF_BOARD_FIXUP
 config SPL_OF_CONTROL
        bool "Enable run-time configuration via Device Tree in SPL"
        depends on SPL && OF_CONTROL
+       select SPL_OF_LIBFDT if !SPL_OF_PLATDATA
        help
          Some boards use device tree in U-Boot but only have 4KB of SRAM
          which is not enough to support device tree. Disable this option to
@@ -50,6 +52,7 @@ config SPL_OF_CONTROL
 config TPL_OF_CONTROL
        bool "Enable run-time configuration via Device Tree in TPL"
        depends on TPL && OF_CONTROL
+       select TPL_OF_LIBFDT if !TPL_OF_PLATDATA
        help
          Some boards use device tree in U-Boot but only have 4KB of SRAM
          which is not enough to support device tree. Enable this option to
@@ -311,6 +314,26 @@ config OF_SPL_REMOVE_PROPS
          can be discarded. This option defines the list of properties to
          discard.
 
+config OF_DTB_PROPS_REMOVE
+       bool "Enable removal of device tree properties"
+       depends on OF_CONTROL
+       help
+         Some boards have restricted amount of storage for U-Boot image.
+         If the generated binary doesn't fit into available image storage,
+         the built-in device tree could probably be cut down by removing
+         some not required device tree properties to reduce the image size.
+         Enable this option and define the properties to be removed in the
+         CONFIG_OF_REMOVE_PROPS list. Do not enable this option if you must
+         pass the built-in DTB directly to the kernel!
+
+config OF_REMOVE_PROPS
+       string "List of device tree properties to drop"
+       depends on OF_DTB_PROPS_REMOVE
+       default "interrupt-parent interrupts" if PINCTRL
+       help
+         Some properties are not used by U-Boot and can be discarded.
+         This option defines the list of properties to discard.
+
 config SPL_OF_PLATDATA
        bool "Generate platform data for use in SPL"
        depends on SPL_OF_CONTROL
@@ -323,15 +346,24 @@ config SPL_OF_PLATDATA
          former can add 3KB or more to a Thumb 2 Image.
 
          This option enables generation of platform data from the device
-         tree as C code. This code creates devices using U_BOOT_DEVICE()
+         tree as C code. This code creates devices using U_BOOT_DRVINFO()
          declarations. The benefit is that it allows driver code to access
          the platform data directly in C structures, avoidin the libfdt
          overhead.
 
          This option works by generating C structure declarations for each
-         compatible string, then adding platform data and U_BOOT_DEVICE
+         compatible string, then adding platform data and U_BOOT_DRVINFO
          declarations for each node. See of-plat.txt for more information.
 
+config SPL_OF_PLATDATA_PARENT
+       bool "Support parent information in devices"
+       depends on SPL_OF_PLATDATA
+       default y
+       help
+         Generally it is useful to be able to access the parent of a device
+         with of-platdata. To save space this can be disabled, but in that
+         case dev_get_parent() will always return NULL;
+
 config TPL_OF_PLATDATA
        bool "Generate platform data for use in TPL"
        depends on TPL_OF_CONTROL
@@ -344,22 +376,22 @@ config TPL_OF_PLATDATA
          former can add 3KB or more to a Thumb 2 Image.
 
          This option enables generation of platform data from the device
-         tree as C code. This code creates devices using U_BOOT_DEVICE()
+         tree as C code. This code creates devices using U_BOOT_DRVINFO()
          declarations. The benefit is that it allows driver code to access
          the platform data directly in C structures, avoidin the libfdt
          overhead.
 
          This option works by generating C structure declarations for each
-         compatible string, then adding platform data and U_BOOT_DEVICE
+         compatible string, then adding platform data and U_BOOT_DRVINFO
          declarations for each node. See of-plat.txt for more information.
 
-endmenu
-
-config MKIMAGE_DTC_PATH
-       string "Path to dtc binary for use within mkimage"
-       default "dtc"
+config TPL_OF_PLATDATA_PARENT
+       bool "Support parent information in devices"
+       depends on TPL_OF_PLATDATA
+       default y
        help
-         The mkimage host tool will, in order to generate FIT images make
-         calls to the dtc application in order to create the output.  In
-         some cases the system dtc may not support all required features
-         and the path to a different version should be given here.
+         Generally it is useful to be able to access the parent of a device
+         with of-platdata. To save space this can be disabled, but in that
+         case dev_get_parent() will always return NULL;
+
+endmenu