23 Feb, 2018

1 commit


11 Feb, 2018

1 commit


28 Jan, 2018

1 commit


23 Jan, 2018

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
     

04 Oct, 2017

1 commit

  • The g_dnl USB settings for the vendor ID, product ID and manufacturer are
    actually common settings that can and should be shared by all the gadgets.

    Make them common by renaming them, and convert all the users.

    Reviewed-by: Simon Glass
    Reviewed-by: Lukasz Majewski
    Signed-off-by: Maxime Ripard

    Maxime Ripard
     

28 Aug, 2017

1 commit


15 Aug, 2017

1 commit


08 Aug, 2017

1 commit


26 Jul, 2017

1 commit


19 Jun, 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
     

28 Apr, 2017

1 commit


19 Mar, 2017

1 commit

  • Today, we have cases where we wish to build all of U-Boot in Thumb2 mode for
    various reasons. We also have cases where we only build SPL in Thumb2 mode due
    to size constraints and wish to build the rest of the system in ARM mode. So
    in this migration we introduce a new symbol as well, SPL_SYS_THUMB_BUILD to
    control if we build everything or just SPL (or in theory, just U-Boot) in
    Thumb2 mode.

    Signed-off-by: Tom Rini
    Acked-by: Siarhei Siamashka

    Tom Rini
     

28 Jan, 2017

3 commits


26 Jan, 2017

1 commit


24 Jan, 2017

1 commit


22 Jan, 2017

1 commit


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
     

24 Oct, 2016

1 commit


27 Sep, 2016

1 commit

  • Introduce a hidden USB_FUNCTION_DFU Kconfig option and select it for
    CMD_DFU (as we must have the DFU command enabled to do anything DFU).
    Make all of the entries in drivers/dfu/Kconfig depend on CMD_DFU and add
    options for all of the back end choices that DFU can make use of.

    Cc: Lukasz Majewski
    Signed-off-by: Tom Rini
    Acked-by: Lukasz Majewski

    Tom Rini
     

10 Sep, 2016

2 commits


29 Jun, 2016

1 commit


17 Jun, 2016

1 commit


10 Jun, 2016

1 commit


04 Jun, 2016

2 commits

  • Create an entry for "config USB_XHCI_DWC3" in Kconfig and
    switch over to it for all boards.

    Signed-off-by: Masahiro Yamada

    Masahiro Yamada
     
  • Move CONFIG_USB_XHCI to defconfig files for all boards, renaming it
    into CONFIG_USB_XHCI_HCD.

    As commented in the help of "config USB_XHCI" entry, this has been
    a TODO for a long time; now CONFIG_USB_XHCI_HCD and CONFIG_USB_XHCI
    have been unified in favor of the former.

    Note:
    Some boards define CONFIG_USB_XHCI in their headers without
    CONFIG_USB, which does not meet the "depends on" in Kconfig.
    I added CONFIG_USB=y for those boards when converting.
    Otherwise, they would fail to build.

    Signed-off-by: Masahiro Yamada

    Masahiro Yamada
     

28 May, 2016

3 commits

  • Updates configs/am43xx_evm.h to use CONFIG options from
    SOC specific Kconfig file for various calculations.

    On AM43x devices, the address of SPL entry point depends on
    the device type, i.e. whether it is secure or non-secure.

    Further, for non-secure devices, the SPL entry point is different
    between USB HOST boot mode, other "memory" boot modes (MMC, NAND)
    and "peripheral" boot modes (UART, USB)

    To add to the complexity, on secure devices, in addition to the
    above differences, the SPL entry point can change because of the
    space occupied by other components (other than u-boot or spl)
    that go into a secure boot image.

    To prevent the user from having to modify source files every time
    any component of the secure image changes, the value of
    CONFIG_SPL_TEXT_BASE has been set using a Kconfig option that
    is supplied in the am43xx_*_defconfig files

    Using the CONFIG options also enables us to do away with some
    compile time flags that were used to specify CONFIG_SPL_TEXT_BASE
    for different boot modes.

    On QSPI devices, the same problem described above occurs w.r.t. the
    address of the u-boot entry point in flash, when booting secure
    devices. To handle this, CONFIG_SYS_TEXT_BASE is also setup via
    a Kconfig option and the defconfig files.

    Signed-off-by: Madan Srinivas
    Signed-off-by: Daniel Allred

    Reviewed-by: Lokesh Vutla
    Tested-by: Andreas Dannenberg
    Reviewed-by: Tom Rini

    Madan Srinivas
     
  • Adding support for AM43xx secure devices require the addition
    of some SOC specific config options like the amount of memory
    used by public ROM and the address of the entry point of u-boot
    or SPL, as seen by the ROM code, for the image to be built
    correctly.

    This mandates the addition of am AM43xx CONFIG option and the
    ARM Kconfig file has been modified to source this SOC Kconfig
    file. Moving the TARGET_AM43XX_EVM config option to the SOC
    KConfig and out of the arch/arm/Kconfig.

    Updating defconfigs to add the CONFIG_AM43XX=y statement and
    removing the #define CONFIG_AM43XX from the header file.

    Signed-off-by: Madan Srinivas
    Signed-off-by: Daniel Allred

    Tested-by: Andreas Dannenberg
    Reviewed-by: Tom Rini

    Madan Srinivas
     
  • This patch also adds the SPL time VCI string into Kconfig.

    Signed-off-by: Alexander Graf
    Reviewed-by: Tom Rini

    Alexander Graf
     

26 Apr, 2016

3 commits


20 Apr, 2016

3 commits