23 Feb, 2018

1 commit


13 Dec, 2017

1 commit


11 Oct, 2017

1 commit

  • Having this as a 'default y' is rather annoying because it doesn't
    actually compile unless other options are defined in the board header:

    ../cmd/bootm.c: In function 'do_imls_nor':
    ../cmd/bootm.c:330:7: error: 'CONFIG_SYS_MAX_FLASH_BANKS' undeclared (first use in this function); did you mean 'CONFIG_SYS_MAX_FLASH_SECT'?
    i < CONFIG_SYS_MAX_FLASH_BANKS; ++i, ++info) {

    Make it 'default n' so people who develop new boards that start from a
    blank defconfig have one less compilation failure to debug.

    Signed-off-by: Tuomas Tynkkynen

    Tuomas Tynkkynen
     

08 Sep, 2017

2 commits


28 Aug, 2017

1 commit


15 Aug, 2017

1 commit


14 Aug, 2017

1 commit


11 Aug, 2017

1 commit


01 Aug, 2017

1 commit


26 Jul, 2017

1 commit

  • 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: Simon Glass
    Signed-off-by: Tom Rini

    Simon Glass
     

12 Jul, 2017

1 commit


04 Jun, 2017

1 commit

  • Now that these symbols are in Kconfig, migrate all users. Use imply on
    a number of platforms that default to having this enabled. As part of
    this we must migrate some straglers for CMD_FAT and DOS_PARTITION.

    Signed-off-by: Tom Rini

    Tom Rini
     

22 May, 2017

1 commit

  • This converts the following to Kconfig:
    CONFIG_CMD_EEPROM
    CONFIG_CMD_EEPROM_LAYOUT
    CONFIG_EEPROM_LAYOUT_HELP_STRING

    Signed-off-by: Simon Glass
    Reviewed-by: Tom Rini
    [trini: Rework Kconfig logic slightly, define EEPROM location on TI eval
    platforms]
    Signed-off-by: Tom Rini

    Simon Glass
     

16 May, 2017

1 commit


15 May, 2017

1 commit

  • While in theory this value could be used in places outside of "omap5"
    (such as OMAP4), we only make use of it today in OMAP5, so place the
    Kconfig entry there. Given that Kconfig lets us provide a default, we
    drop CONFIG_DEFAULT_OMAP_RESET_TIME_MAX_USEC entirely. The contents of
    doc/README.omap-reset-time make a good help entry, so adjust them
    slightly and delete the file. Move the comment about range to where we
    use the value now, and have Kconfig enforce the upper bound.

    Signed-off-by: Tom Rini

    Tom Rini
     

28 Apr, 2017

1 commit


14 Mar, 2017

1 commit


28 Jan, 2017

3 commits


11 Jan, 2017

1 commit

  • 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: Masahiro Yamada
    Reviewed-by: Marek Vasut

    Masahiro Yamada
     

19 Nov, 2016

1 commit


24 Oct, 2016

1 commit


20 Sep, 2016

1 commit


17 Sep, 2016

3 commits


10 Sep, 2016

2 commits


10 Jun, 2016

1 commit


26 Apr, 2016

3 commits


15 Mar, 2016

2 commits

  • 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: Simon Glass
    [trini: Add microblaze change, various configs/ re-applies]
    Signed-off-by: Tom Rini

    Simon Glass
     
  • Move this option to Kconfig and tidy up existing boards.

    Signed-off-by: Simon Glass

    Simon Glass
     

22 Nov, 2015

1 commit


19 Nov, 2015

1 commit


28 Sep, 2015

1 commit


13 Aug, 2015

1 commit

  • 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 _common.h and _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 _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
    _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
    Cc: Masahiro Yamada
    Cc: Stefano Babic
    Cc: Igor Grinberg
    Signed-off-by: Nikita Kiryanov
    [trini: Add spring, sniper, smartweb to conversion]
    Signed-off-by: Tom Rini

    Nikita Kiryanov