1. 05 8月, 2017 1 次提交
  2. 26 7月, 2017 1 次提交
    • S
      Convert CONFIG_ENV_IS_IN_MMC/NAND/UBI and NOWHERE to Kconfig · 2be29653
      Simon Glass 提交于
      This converts the following to Kconfig:
         CONFIG_ENV_IS_IN_MMC
         CONFIG_ENV_IS_IN_NAND
         CONFIG_ENV_IS_IN_UBI
         CONFIG_ENV_IS_NOWHERE
      
      In fact this already exists for sunxi as a 'choice' config. However not
      all the choices are available in Kconfig yet so we cannot use that. It
      would lead to more than one option being set.
      
      In addition, one purpose of this series is to allow the environment to be
      stored in more than one place. So the existing choice is converted to a
      normal config allowing each option to be set independently.
      
      There are not many opportunities for Kconfig updates to reduce the size of
      this patch. This was tested with
      
         ./tools/moveconfig.py -i CONFIG_ENV_IS_IN_MMC
      
      And then manual updates.  This is because for CHAIN_OF_TRUST boards they
      can only have ENV_IS_NOWHERE set, so we enforce that via Kconfig logic
      now.
      Signed-off-by: NSimon Glass <sjg@chromium.org>
      Signed-off-by: NTom Rini <trini@konsulko.com>
      2be29653
  3. 19 6月, 2017 1 次提交
  4. 28 4月, 2017 1 次提交
  5. 19 3月, 2017 1 次提交
  6. 14 3月, 2017 1 次提交
  7. 18 2月, 2017 1 次提交
  8. 28 1月, 2017 3 次提交
  9. 11 1月, 2017 1 次提交
    • M
      mmc: move more driver config options to Kconfig · 1d2c0506
      Masahiro Yamada 提交于
      Move (and rename) the following CONFIG options to Kconfig:
      
        CONFIG_DAVINCI_MMC  (renamed to CONFIG_MMC_DAVINCI)
        CONFIG_OMAP_HSMMC   (renamed to CONFIG_MMC_OMAP_HS)
        CONFIG_MXC_MMC      (renamed to CONFIG_MMC_MXC)
        CONFIG_MXS_MMC      (renamed to CONFIG_MMC_MXS)
        CONFIG_TEGRA_MMC    (renamed to CONFIG_MMC_SDHCI_TEGRA)
        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 '
      s/CONFIG_DAVINCI_MMC/CONFIG_MMC_DAVINCI/g
      s/CONFIG_OMAP_HSMMC/CONFIG_MMC_OMAP_HS/g
      s/CONFIG_MXC_MMC/CONFIG_MMC_MXC/g
      s/CONFIG_MXS_MMC/CONFIG_MMC_MXS/g
      s/CONFIG_TEGRA_MMC/CONFIG_MMC_SDHCI_TEGRA/g
      s/CONFIG_SUNXI_MMC/CONFIG_MMC_SUNXI/g
      '
      
      [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 \
      MMC_DAVINCI MMC_OMAP_HS MMC_MXC MMC_MXS MMC_SDHCI_TEGRA MMC_SUNXI
      
      [5] Sort and align drivers/mmc/Makefile for readability
      Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
      Reviewed-by: NMarek Vasut <marex@denx.de>
      1d2c0506
  10. 30 12月, 2016 1 次提交
  11. 19 11月, 2016 1 次提交
  12. 24 10月, 2016 1 次提交
  13. 20 9月, 2016 1 次提交
  14. 17 9月, 2016 2 次提交
  15. 26 4月, 2016 3 次提交
  16. 20 4月, 2016 2 次提交
  17. 26 3月, 2016 1 次提交
  18. 15 3月, 2016 1 次提交
  19. 01 3月, 2016 1 次提交
  20. 22 11月, 2015 1 次提交
  21. 28 9月, 2015 1 次提交
  22. 13 8月, 2015 3 次提交
    • N
      kconfig: add config option for shell prompt · 181bd9dc
      Nikita Kiryanov 提交于
      Add option to set shell prompt string from menuconfig and migrate
      boards globally.
      
      The migration is done as follows:
      - Boards that explicitly and unconditionally set CONFIG_SYS_PROMPT had the
        entry moved to their defconfig files.
      - Boards that defined some kind of #ifdef logic which selects the
        CONFIG_SYS_PROMPT (for example qemu-mips) got an #undef CONFIG_SYS_PROMPT
        right before the #ifdef logic and were left alone.
      - This change forces CONFIG_SYS_PROMPT to be a per board decision, and thus
        CONFIG_SYS_PROMPT was removed from all <soc>_common.h and <arch>_common.h
        files. This results in a streamlined default value across platforms, and
        includes the following files: spear-common, sunxi-common, mv-common,
        ti_armv7_common, tegra-common, at91-sama5_common, and zynq-common.
      - Boards that relied on <arch/soc>_common.h values of CONFIG_SYS_PROMPT were
        not updated in their respective defconfig files under the assumption that
        since they did not explicitly define a value, they're fine with whatever
        the default is.
      - On the other hand, boards that relied on a value defined in some
        <boards>_common.h file such as woodburn_common, rpi-common,
        bur_am335x_common, ls2085a_common, siemens_am33x_common, and
        omap3_evm_common, had their values moved to the respective defconfig files.
      - The define V_PROMPT was removed, since it is not used anywhere except for
        assigning a value for CONFIG_SYS_PROMPT.
      
      Cc: Tom Rini <trini@konsulko.com>
      Cc: Masahiro Yamada <yamada.m@jp.panasonic.com>
      Cc: Stefano Babic <sbabic@denx.de>
      Cc: Igor Grinberg <grinberg@compulab.co.il>
      Signed-off-by: NNikita Kiryanov <nikita@compulab.co.il>
      [trini: Add spring, sniper, smartweb to conversion]
      Signed-off-by: NTom Rini <trini@konsulko.com>
      181bd9dc
    • P
      sniper: Fastboot support · fbdd3299
      Paul Kocialkowski 提交于
      This adds support for the fastboot USB gadget, including flashing to the
      internal MMC and reboot to bootloader or not.
      Signed-off-by: NPaul Kocialkowski <contact@paulk.fr>
      Reviewed-by: NTom Rini <trini@konsulko.com>
      [trini: Update to use Kconfig for MUSB]
      Signed-off-by: NTom Rini <trini@konsulko.com>
      fbdd3299
    • P
      LG Optimus Black (P970) codename sniper support · 0257930b
      Paul Kocialkowski 提交于
      The LG Optimus Black (P970) codename sniper is a smartphone that was designed
      and manufactured by LG Electronics (LGE) and released back in 2011.
      
      It is using an OMAP3630 SoC GP version, which allows running U-Boot and the
      U-Boot SPL from the ground up. This port is aimed at running an Android version
      such as Replicant, the fully free Android distribution. However, support for
      upstream Linux with device-tree and common GNU/Linux distros boot commands
      could be added in the future.
      
      For more information about the journey to freeing this device, please read the
      series of blog posts at:
      http://code.paulk.fr/article20/a-hacker-s-journey-freeing-a-phone-from-the-ground-up-first-partSigned-off-by: NPaul Kocialkowski <contact@paulk.fr>
      Reviewed-by: NTom Rini <trini@konsulko.com>
      [trini: Add CONFIG_OF_SUPPORT]
      Signed-off-by: NTom Rini <trini@konsulko.com>
      0257930b
  23. 26 6月, 2015 1 次提交
  24. 01 6月, 2015 1 次提交
  25. 13 5月, 2015 1 次提交
  26. 19 4月, 2015 1 次提交
    • M
      dm: select CONFIG_DM* options · 58d423b8
      Masahiro Yamada 提交于
      As mentioned in the previous commit, adding default values in each
      Kconfig causes problems because it does not co-exist with the
      "depends on" syntax.  (Please note this is not a bug of Kconfig.)
      We should not do so unless we have a special reason.  Actually,
      for CONFIG_DM*, we have no good reason to do so.
      
      Generally, CONFIG_DM is not a user-configurable option.  Once we
      convert a driver into Driver Model, the board only works with Driver
      Model, i.e. CONFIG_DM must be always enabled for that board.
      So, using "select DM" is more suitable rather than allowing users to
      modify it.  Another good thing is, Kconfig warns unmet dependencies
      for "select" syntax, so we easily notice bugs.
      
      Actually, CONFIG_DM and other related options have been added
      without consistency: some into arch/*/Kconfig, some into
      board/*/Kconfig, and some into configs/*_defconfig.
      
      This commit prefers "select" and cleans up the following issues.
      
      [1] Never use "CONFIG_DM=n" in defconfig files
      
      It is really rare to add "CONFIG_FOO=n" to disable CONFIG options.
      It is more common to use "# CONFIG_FOO is not set".  But here, we
      do not even have to do it.
      Less than half of OMAP3 boards have been converted to Driver Model.
      Adding the default values to arch/arm/cpu/armv7/omap3/Kconfig is
      weird.  Instead, add "select DM" only to appropriate boards, which
      eventually eliminates "CONFIG_DM=n", etc.
      
      [2] Delete redundant CONFIGs
      
      Sandbox sets CONFIG_DM in arch/sandbox/Kconfig and defines it again
      in configs/sandbox_defconfig.
      Likewise, OMAP3 sets CONFIG_DM arch/arm/cpu/armv7/omap3/Kconfig and
      defines it also in omap3_beagle_defconfig and devkit8000_defconfig.
      Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
      58d423b8
  27. 16 3月, 2015 1 次提交
  28. 13 2月, 2015 1 次提交
  29. 31 8月, 2014 1 次提交
  30. 30 7月, 2014 1 次提交
    • M
      kconfig: add board Kconfig and defconfig files · dd84058d
      Masahiro Yamada 提交于
      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: NMasahiro Yamada <yamada.m@jp.panasonic.com>
      Acked-by: NSimon Glass <sjg@chromium.org>
      dd84058d