08 Sep, 2017

2 commits


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
     

16 May, 2017

1 commit


15 May, 2017

1 commit


01 May, 2017

1 commit


30 Apr, 2017

3 commits


31 Jan, 2017

1 commit

  • 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: Masahiro Yamada
    Reviewed-by: Tom Rini

    Masahiro Yamada
     

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
     

30 Dec, 2016

1 commit

  • Commit 7a777f6d6f35 ("mmc: Add generic Kconfig option") created
    a Kconfig entry for this option without any actual moves, then
    commit 44c798799f66 ("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: Masahiro Yamada
    Reviewed-by: Jaehoon Chung

    Masahiro Yamada
     

10 Sep, 2016

1 commit


26 Apr, 2016

2 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
     

19 Feb, 2016

1 commit


17 Feb, 2016

2 commits


26 Jan, 2016

1 commit

  • Enabling CONFIG_DISPLAY breaks building for some architectures
    (microblaze-generic), so we disable CONFIG_DISPLAY in Kconfig
    by default and enable this option in defconfigs. CONFIG_DISPLAY
    depends on CONFIG_I2C_EDID, so add and enable it in defconfigs, too.

    Signed-off-by: Anatolij Gustschin
    Reported-by: Bin Meng
    Cc: Simon Glass
    Reviewed-by: Tom Rini
    Reviewed-by: Simon Glass
    Tested-by: Bin Meng
    Signed-off-by: Anatolij Gustschin

    Anatolij Gustschin
     

25 Nov, 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
     

06 Aug, 2015

2 commits


26 Jun, 2015

1 commit

  • Some archs/boards specify their own default by pre-defining the config
    which causes the Kconfig system to mix up the order of the configs in
    the defconfigs... This will cause merge pain if allowed to proliferate.

    Remove the configs that behave this way from the archs.

    A few configs still remain, but that is because they only exist as
    defaults and do not have a proper Kconfig entry. Those appear to be:

    SPIFLASH
    DISPLAY_BOARDINFO

    Signed-off-by: Joe Hershberger
    [trini: rastaban, am43xx_evm_usbhost_boot, am43xx_evm_ethboot updates,
    drop DM_USB from MSI_Primo81 as USB_MUSB_SUNXI isn't converted yet to DM]
    Signed-off-by: Tom Rini

    Joe Hershberger
     

10 Jun, 2015

2 commits

  • We need to match the device tree in the FIT with the U-Boot model so we
    can automatically select the right device tree. Also adjust the load address
    so that the device tree is not in the way when a zImage kernel tries to
    extract itself.

    Signed-off-by: Simon Glass
    Signed-off-by: Tom Warren

    Simon Glass
     
  • Enable the EC and keyboard, using the SPI bus.

    The EC driver requires a particular format and a deactivation delay. Also
    U-Boot does not support interrupts.

    For now, adjust the device tree to comply. At some point we should tidy
    this up to support interrupts and make tegra and exynos use the same setup.

    Signed-off-by: Simon Glass
    Signed-off-by: Tom Warren

    Simon Glass
     

01 Jun, 2015

1 commit


14 May, 2015

1 commit


05 Mar, 2015

1 commit

  • All boards need CONFIG_BOARD_EARLY_INIT_F, and many actively need
    CONFIG_BOARD_LATE_INIT. Move both of these into tegra-common.h so that
    board config headers don't need to repeatedly define them.

    Later commits will add new code in board_late_init() which applies to
    all boards, so CONFIG_BOARD_LATE_INIT should be enabled for all Tegra
    boards.

    Signed-off-by: Stephen Warren
    Signed-off-by: Tom Warren

    Stephen Warren
     

12 Dec, 2014

2 commits

  • This converts all Tegra boards over to use driver model for I2C. The driver
    is adjusted to use driver model and the following obsolete CONFIGs are
    removed:

    - CONFIG_SYS_I2C_INIT_BOARD
    - CONFIG_I2C_MULTI_BUS
    - CONFIG_SYS_MAX_I2C_BUS
    - CONFIG_SYS_I2C_SPEED
    - CONFIG_SYS_I2C

    This has been tested on:
    - trimslice (no I2C)
    - beaver
    - Jetson-TK1

    It has not been tested on Tegra 114 as I don't have that board.

    Acked-by: Heiko Schocher
    Signed-off-by: Simon Glass

    Simon Glass
     
  • Nyan-big is a Tegra124 clamshell board that is very similar to venice2, but
    it has a different panel, the sdcard cd and wp sense are flipped, and it has
    a different revision of the AS3722 PMIC.

    This is the Acer Chromebook 13 CB5-311-T7NN (13.3-inch HD, NVIDIA
    Tegra K1, 2GB). The display is not currently supported, so it should
    boot on other nyan-based Chromebooks also, but only the device tree for
    nyan-big is provided here.

    The device tree file is from Linux but with features removed which are
    unlikely to be supported in U-Boot soon (regulators, pinmux). Also the
    addresses are updated to 32-bit.

    Signed-off-by: Allen Martin
    Signed-off-by: Simon Glass
    (rebase, change to 'nyan-big', fix pinmux that resets nyan-big)

    Allen Martin