Skip to content
Snippets Groups Projects
  1. Apr 30, 2017
  2. Jan 31, 2017
    • Masahiro Yamada's avatar
      mmc: move CONFIG_GENERIC_MMC to Kconfig · 54925327
      Masahiro Yamada authored
      
      Now, CONFIG_GENERIC_MMC seems equivalent to CONFIG_MMC.
      
      Let's create an entry for "config GENERIC_MMC" with "default MMC",
      then convert all macro defines in headers to Kconfig.  Almost all
      of the defines will go away.
      
      I see only two exceptions:
        configs/blanche_defconfig
        configs/sandbox_noblk_defconfig
      
      They define CONFIG_GENERIC_MMC, but not CONFIG_MMC.  Something
      might be wrong with these two boards, so should be checked later.
      
      Anyway, this is the output of the moveconfig tool.
      
      This commit was created as follows:
      
      [1] create a config entry in drivers/mmc/Kconfig
      
      [2] tools/moveconfig.py -r HEAD GENERIC_MMC
      
      [3] manual clean-up of garbage comments in doc/README.* and
          include/configs/*.h
      
      Signed-off-by: default avatarMasahiro Yamada <yamada.masahiro@socionext.com>
      Reviewed-by: default avatarTom Rini <trini@konsulko.com>
      54925327
  3. Jan 11, 2017
    • 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_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: default avatarMasahiro Yamada <yamada.masahiro@socionext.com>
      Reviewed-by: default avatarMarek Vasut <marex@denx.de>
      1d2c0506
  4. Dec 29, 2016
    • Masahiro Yamada's avatar
      mmc: complete unfinished move of CONFIG_MMC · c2726995
      Masahiro Yamada authored
      
      Commit 7a777f6d ("mmc: Add generic Kconfig option") created
      a Kconfig entry for this option without any actual moves, then
      commit 44c79879 ("sunxi: Use Kconfig CONFIG_MMC") moved
      instances only for SUNXI.
      
      We generally do not like such partial moves.  This kind of work
      is automated by tools/moveconfig.py, so it is pretty easy to
      complete this move.
      
      I am adding "default ARM || PPC || SANDBOX" (suggested by Tom).
      This shortens the configs and will ease new board porting.
      
      This commit was created as follows:
      
      [1] Edit Kconfig (remove the "depends on", add the "default",
          copy the prompt and help message from Linux)
      
      [2] Run 'tools/moveconfig.py -y -s -r HEAD MMC'
      
      Signed-off-by: default avatarMasahiro Yamada <yamada.masahiro@socionext.com>
      Reviewed-by: default avatarJaehoon Chung <jh80.chung@samsung.com>
      c2726995
  5. Sep 09, 2016
  6. Apr 25, 2016
  7. Mar 14, 2016
    • Simon Glass's avatar
      Kconfig: Move CONFIG_FIT and related options to Kconfig · 73223f0e
      Simon Glass authored
      
      There are already two FIT options in Kconfig but the CONFIG options are
      still in the header files. We need to do a proper move to fix this.
      
      Move these options to Kconfig and tidy up board configuration:
      
         CONFIG_FIT
         CONFIG_OF_BOARD_SETUP
         CONFIG_OF_SYSTEM_SETUP
         CONFIG_FIT_SIGNATURE
         CONFIG_FIT_BEST_MATCH
         CONFIG_FIT_VERBOSE
         CONFIG_OF_STDOUT_VIA_ALIAS
         CONFIG_RSA
      
      Unfortunately the first one is a little complicated. We need to make sure
      this option is not enabled in SPL by this change. Also this option is
      enabled automatically in the host builds by defining CONFIG_FIT in the
      image.h file. To solve this, add a new IMAGE_USE_FIT #define which can
      be used in files that are built on the host but must also build for U-Boot
      and SPL.
      
      Note: Masahiro's moveconfig.py script is amazing.
      
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      [trini: Add microblaze change, various configs/ re-applies]
      Signed-off-by: default avatarTom Rini <trini@konsulko.com>
      73223f0e
  8. Feb 16, 2016
  9. Aug 13, 2015
    • Nikita Kiryanov's avatar
      kconfig: add config option for shell prompt · 181bd9dc
      Nikita Kiryanov authored
      
      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: default avatarNikita Kiryanov <nikita@compulab.co.il>
      [trini: Add spring, sniper, smartweb to conversion]
      Signed-off-by: default avatarTom Rini <trini@konsulko.com>
      181bd9dc
  10. Jun 01, 2015
  11. Mar 04, 2015
  12. Sep 25, 2014
  13. Jul 24, 2013
  14. Apr 15, 2013
  15. Mar 14, 2013
  16. Jan 16, 2013
  17. Nov 19, 2012
  18. Oct 15, 2012
  19. Sep 10, 2012
  20. Sep 07, 2012
  21. Sep 01, 2012
  22. Jul 09, 2012
  23. Jul 07, 2012
    • Tom Warren's avatar
      arm: Tegra: Use ODMDATA from BCT in IRAM · 76e350b7
      Tom Warren authored
      
      Walk the BIT and BCT to find the ODMDATA word in the
      CustomerData field and put it into Scratch20 reg for
      use by kernel, etc.
      
      Built all Tegra builds OK; Booted on Seaboard and saw
      ODMDATA in PMC scratch20 was the same as the value in my
      burn-u-boot.sh file (0x300D8011). NOTE: All flash utilities
      will have to specify the odmdata (nvflash --odmdata n) on
      the command line or via a cfg file, or built in to their
      BCT.
      
      Signed-off-by: default avatarTom Warren <twarren@nvidia.com>
      Acked-by: default avatarStephen Warren <swarren@wwwdotorg.org>
      76e350b7
    • Tom Warren's avatar
      mmc: tegra2: rename tegra2_mmc.* to tegra_mmc.* · 3f82d89d
      Tom Warren authored
      
      In anticipation of Tegra3 support, continue removing/renaming
      Tegra2-specific files. No functional changes (yet).
      Updated copyrights to 2012.
      
      Signed-off-by: default avatarTom Warren <twarren@nvidia.com>
      3f82d89d
    • Stephen Warren's avatar
      tegra: flesh out bootcmd · bea2674c
      Stephen Warren authored
      
      This implements a useful bootcmd for Tegra. The boot order is:
      
      * If USB enabled, USB storage
      * Internal MMC (SD card or eMMC)
      * If networking is enabled, BOOTP/TFTP
      
      When booting from USB or MMC, the boot script is assumed to be in
      partition 1 (although this may be overridden via the rootpart variable),
      both ext2 and FAT filesystems are supported, the boot script may exist
      in either / or /boot, and the boot script may be named boot.scr.uimg or
      boot.scr.
      
      When booting over the network, it is assumed that boot.scr.uimg exists
      on the TFTP server. There is less flexibility here since those setting
      up network booting are expected to need less hand-holding.
      
      In all cases, it is expected that the initial file loaded is a U-Boot
      image containing a script that will load the kernel, load any required
      initrd, load any required DTB, and finally bootm the kernel.
      
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      Signed-off-by: default avatarTom Warren <twarren@nvidia.com>
      bea2674c
    • Stephen Warren's avatar
      tegra: remove some cruft from CONFIG_EXTRA_ENV_SETTINGS · 07a84b7b
      Stephen Warren authored
      
      console isn't used by anything, and the kernel should be set appropriately
      by whatever script is booting the kernel, not imposed by the bootloader.
      
      mem might be useful, but the current value is pretty bogus, since it
      includes nvmem options that make no sense for an upstream kernel, and
      equally should not be required for any downstream kernel. Either way, this
      is also best left to the kernel boot script.
      
      smpflag isn't used by anything, and again was probably intended to be a
      kernel command-line option better set by the kernel boot script.
      
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      Signed-off-by: default avatarTom Warren <twarren@nvidia.com>
      07a84b7b
  24. Dec 24, 2011
  25. Dec 09, 2011
  26. Jul 16, 2011
  27. Apr 27, 2011
  28. Mar 27, 2011
  29. Feb 21, 2011
Loading