1. 28 Jan, 2017 2 commits
  2. 29 Dec, 2016 2 commits
    • Masahiro Yamada's avatar
      mmc: move some SDHCI related options to Kconfig · 45a68fe2
      Masahiro Yamada authored
      While I moved the options, I also renamed them so that they are all
      prefixed with MMC_SDHCI_.
      This commit was created in the following steps.
      [1] Rename with the following command
      find . -name .git -prune -o ! -path ./scripts/config_whitelist.txt \
      -type f -print | xargs sed -i -e '
      [2] create the Kconfig entries in drivers/mmc/Kconfig
      [3] Move the options by the following command
      tools/moveconfig.py -y MMC_SDHCI_SDMA MMC_SDHCI_BCM2835 \
      [4] Sort drivers/mmc/Makefile for readability
      Signed-off-by: 's avatarMasahiro Yamada <yamada.masahiro@socionext.com>
      Reviewed-by: 's avatarTom Rini <trini@konsulko.com>
      Reviewed-by: 's avatarJaehoon Chung <jh80.chung@samsung.com>
    • Masahiro Yamada's avatar
      mmc: move CONFIG_SDHCI to Kconfig, renaming to CONFIG_MMC_SDHCI · e1ce61fb
      Masahiro Yamada authored
      Move CONFIG_SDHCI to Kconfig and rename it to CONFIG_MMC_SDHCI.
      My motivation for the rename is, ultimately, to make all the MMC
      options prefixed with MMC_ and SDHCI options with MMC_SDHCI_,
      like Linux.
      This commit was created as follows:
      [1] Rename the config option with the following command:
      find . -name .git -prune -o ! -path ./scripts/config_whitelist.txt \
      -type f -print | xargs sed -i -e 's/CONFIG_SDHCI/CONFIG_MMC_SDHCI/g'
      [2] create the entry for MMC_SDHCI in drivers/mmc/Kconfig
      [3] run "tools/moveconfig.py -y MMC_SDHCI"
      [4] add "depends on MMC_SDHCI" to existing SDHCI driver entries
      Signed-off-by: 's avatarMasahiro Yamada <yamada.masahiro@socionext.com>
      Reviewed-by: 's avatarTom Rini <trini@konsulko.com>
      Reviewed-by: 's avatarJaehoon Chung <jh80.chung@samsung.com>
  3. 12 Oct, 2016 2 commits
  4. 09 Sep, 2016 1 commit
  5. 20 Aug, 2016 1 commit
  6. 20 Jun, 2016 1 commit
    • Masahiro Yamada's avatar
      autoboot: add CONFIG_AUTOBOOT to allow to not compile autoboot.c · 41598c82
      Masahiro Yamada authored
      Since commit bb597c0e ("common: bootdelay: move CONFIG_BOOTDELAY
      into a Kconfig option"), CONFIG_BOOTDELAY is defined for all boards.
      Prior to that commit, it was allowed to unset CONFIG_BOOTDELAY to
      not compile common/autoboot.c, as described in common/Makefile:
        # This option is not just y/n - it can have a numeric value
        ifdef CONFIG_BOOTDELAY
        obj-y += autoboot.o
      It was a bit odd to enable/disable code with an integer type option,
      but it was how this option worked before that commit, and several
      boards actually unset it to opt out of the autoboot feature.
      This commit adds a new bool option, CONFIG_AUTOBOOT, and makes
      CONFIG_BOOTDELAY depend on it.
      I chose "default y" for this option because most boards use the
      autoboot.  I added "# CONFIG_AUTOBOOT is not set" for the boards that
      had not set CONFIG_BOOTDELAY prior to the bad commit.
      Signed-off-by: 's avatarMasahiro Yamada <yamada.masahiro@socionext.com>
  7. 13 Jun, 2016 1 commit
  8. 09 Jun, 2016 1 commit
  9. 06 Jun, 2016 1 commit
    • Andre Przywara's avatar
      arm/arm64: implement a boot header capability · cdaa633f
      Andre Przywara authored
      Some SPL loaders (like Allwinner's boot0, and Broadcom's boot0)
      require a header before the actual U-Boot binary to both check its
      validity and to find other data to load. Sometimes this header may
      only be a few bytes of information, and sometimes this might simply
      be space that needs to be reserved for a post-processing tool.
      Introduce a config option to allow assembler preprocessor commands
      to be inserted into the code at the appropriate location; typical
      assembler preprocessor commands might be:
        .space 1000
        .word 0x12345678
      Signed-off-by: 's avatarAndre Przywara <andre.przywara@arm.com>
      Signed-off-by: 's avatarSteve Rae <srae@broadcom.com>
      Commit Notes:
      Please note that the current code:
        start.S (arm64) and
        vectors.S (arm)
      already jumps over some portion of data already, so this option basically
      just increases the size of this region (and the resulting binary).
      For use with Allwinner's boot0 blob there is a tool called boot0img[1],
      which fills the header to allow booting A64 based boards.
      For the Pine64 we need a 1536 byte header (including the branch
      instruction) at the moment, so we add this to the defconfig.
      [1] https://github.com/apritzel/pine64/tree/master/tools
      Reviewed-by: 's avatarTom Rini <trini@konsulko.com>
  10. 25 Apr, 2016 3 commits
  11. 20 Apr, 2016 3 commits
  12. 18 Apr, 2016 1 commit
  13. 25 Mar, 2016 1 commit
  14. 22 Nov, 2015 1 commit
  15. 18 Nov, 2015 1 commit
  16. 26 Jun, 2015 1 commit
  17. 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>