1. 28 Jan, 2017 3 commits
  2. 25 Jan, 2017 1 commit
  3. 24 Jan, 2017 1 commit
  4. 21 Jan, 2017 1 commit
  5. 11 Jan, 2017 1 commit
    • Masahiro Yamada's avatar
      mmc: move more driver config options to Kconfig · 1d2c0506
      Masahiro Yamada authored
      Move (and rename) the following CONFIG options to Kconfig:
        CONFIG_MXC_MMC      (renamed to CONFIG_MMC_MXC)
        CONFIG_MXS_MMC      (renamed to CONFIG_MMC_MXS)
        CONFIG_SUNXI_MMC    (renamed to CONFIG_MMC_SUNXI)
      They are the same option names as used in Linux.
      This commit was created as follows:
      [1] Rename the options with the following command:
      find . -name .git -prune -o ! -path ./scripts/config_whitelist.txt \
      -type f -print | xargs sed -i -e '
      [2] Commit the changes
      [3] Create entries in driver/mmc/Kconfig.
          (copied from Linux)
      [4] Move the options with the following command
      tools/moveconfig.py -y -r HEAD \
      [5] Sort and align drivers/mmc/Makefile for readability
      Signed-off-by: 's avatarMasahiro Yamada <yamada.masahiro@socionext.com>
      Reviewed-by: 's avatarMarek Vasut <marex@denx.de>
  6. 23 Oct, 2016 1 commit
  7. 27 Sep, 2016 1 commit
    • Tom Rini's avatar
      dfu: Migrate to Kconfig · 6828e602
      Tom Rini authored
      Introduce a hidden USB_FUNCTION_DFU Kconfig option and select it for
      CMD_DFU (as we must have the DFU command enabled to do anything DFU).
      Make all of the entries in drivers/dfu/Kconfig depend on CMD_DFU and add
      options for all of the back end choices that DFU can make use of.
      Cc: Lukasz Majewski <l.majewski@samsung.com>
      Signed-off-by: 's avatarTom Rini <trini@konsulko.com>
      Acked-by: 's avatarLukasz Majewski <l.majewski@samsung.com>
  8. 09 Sep, 2016 2 commits
  9. 28 Jun, 2016 1 commit
  10. 17 Jun, 2016 1 commit
  11. 09 Jun, 2016 1 commit
  12. 03 Jun, 2016 2 commits
  13. 27 May, 2016 3 commits
    • Madan Srinivas's avatar
      ti: AM43xx: Use CONFIG options from SOC Kconfig · 9aac7d0e
      Madan Srinivas authored
      Updates configs/am43xx_evm.h to use CONFIG options from
      SOC specific Kconfig file for various calculations.
      On AM43x devices, the address of SPL entry point  depends on
      the device type, i.e. whether it is secure or non-secure.
      Further, for non-secure devices, the SPL entry point is different
      between  USB HOST boot mode, other "memory" boot modes (MMC, NAND)
      and "peripheral" boot modes (UART, USB)
      To add to the complexity, on secure devices, in addition to the
      above differences, the SPL entry point can change because of the
      space occupied by other components (other than u-boot or spl)
      that go into a secure boot image.
      To prevent the user from having to modify source files every time
      any component of the secure image changes, the value of
      CONFIG_SPL_TEXT_BASE has been set using a Kconfig option that
      is supplied in the am43xx_*_defconfig files
      Using the CONFIG options also enables us to do away with some
      compile time flags that were used to specify CONFIG_SPL_TEXT_BASE
      for different boot modes.
      On QSPI devices, the same problem described above occurs w.r.t. the
      address of the u-boot entry point in flash, when booting secure
      devices. To handle this, CONFIG_SYS_TEXT_BASE is also setup via
      a Kconfig option and the defconfig files.
      Signed-off-by: 's avatarMadan Srinivas <madans@ti.com>
      Signed-off-by: 's avatarDaniel Allred <d-allred@ti.com>
      Reviewed-by: 's avatarLokesh Vutla <lokeshvutla@ti.com>
      Tested-by: 's avatarAndreas Dannenberg <dannenberg@ti.com>
      Reviewed-by: 's avatarTom Rini <trini@konsulko.com>
    • Madan Srinivas's avatar
      arm: Kconfig: Add support for AM43xx SoC specific Kconfig · 6384726d
      Madan Srinivas authored
      Adding support for AM43xx secure devices require the addition
      of some SOC specific config options like the amount of memory
      used by public ROM and the address of the entry point of u-boot
      or SPL, as seen by the ROM code, for the image to be built
      This mandates the addition of am AM43xx CONFIG option and the
      ARM Kconfig file has been modified to source this SOC Kconfig
      file. Moving the TARGET_AM43XX_EVM config option to the SOC
      KConfig and out of the arch/arm/Kconfig.
      Updating defconfigs to add the CONFIG_AM43XX=y statement and
      removing the #define CONFIG_AM43XX from the header file.
      Signed-off-by: 's avatarMadan Srinivas <madans@ti.com>
      Signed-off-by: 's avatarDaniel Allred <d-allred@ti.com>
      Tested-by: 's avatarAndreas Dannenberg <dannenberg@ti.com>
      Reviewed-by: 's avatarTom Rini <trini@konsulko.com>
    • Alexander Graf's avatar
      net: Move CONFIG_SPL_NET_VCI_STRING into Kconfig · 210be5c4
      Alexander Graf authored
      This patch also adds the SPL time VCI string into Kconfig.
      Signed-off-by: 's avatarAlexander Graf <agraf@suse.de>
      Reviewed-by: 's avatarTom Rini <trini@konsulko.com>
  14. 25 Apr, 2016 3 commits
  15. 20 Apr, 2016 6 commits
  16. 25 Mar, 2016 1 commit
  17. 14 Mar, 2016 1 commit
  18. 25 Nov, 2015 2 commits
  19. 22 Nov, 2015 1 commit
  20. 18 Nov, 2015 1 commit
  21. 26 Jun, 2015 2 commits
  22. 01 Jun, 2015 1 commit
  23. 12 May, 2015 1 commit
  24. 30 Jul, 2014 1 commit
    • Masahiro Yamada's avatar
      kconfig: add board Kconfig and defconfig files · dd84058d
      Masahiro Yamada authored
      This commit adds:
       - arch/${ARCH}/Kconfig
          provide a menu to select target boards
       - board/${VENDOR}/${BOARD}/Kconfig or board/${BOARD}/Kconfig
          set CONFIG macros to the appropriate values for each board
       - configs/${TARGET_BOARD}_defconfig
          default setting of each board
      (This commit was automatically generated by a conversion script
      based on boards.cfg)
      In Linux Kernel, defconfig files are located under
      arch/${ARCH}/configs/ directory.
      It works in Linux Kernel since ARCH is always given from the
      command line for cross compile.
      But in U-Boot, ARCH is not given from the command line.
      Which means we cannot know ARCH until the board configuration is done.
      That is why all the "*_defconfig" files should be gathered into a
      single directory ./configs/.
      Signed-off-by: 's avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      Acked-by: 's avatarSimon Glass <sjg@chromium.org>