09 Feb, 2020

1 commit

  • Both CMD_MX_CYCLIC and MX_CYCLIC are in use and defined in Kconfig,
    but only the non-CMD version currently does anything. This changes all
    usages to prefer the CMD_MX_CYCLIC option (since it's only affecting
    addition of the commands), and switches defconfigs using the non-CMD
    version to use the CMD version.

    Signed-off-by: Joel Johnson
    Reviewed-by: Tom Rini

    Joel Johnson
     

05 Dec, 2019

1 commit


21 Nov, 2019

2 commits

  • - In ARMv8 NXP Layerscape platforms we also need to make use of
    CONFIG_SYS_RELOC_GD_ENV_ADDR now, do so.
    - On ENV_IS_IN_REMOTE, CONFIG_ENV_OFFSET is never used, drop the define
    to 0.
    - Add Kconfig entry for ENV_ADDR.
    - Make ENV_ADDR / ENV_OFFSET depend on the env locations that use it.
    - Add ENV_xxx_REDUND options that depend on their primary option and
    SYS_REDUNDAND_ENVIRONMENT
    - On a number of PowerPC platforms, use SPL_ENV_ADDR not CONFIG_ENV_ADDR
    for the pre-main-U-Boot environment location.
    - On ENV_IS_IN_SPI_FLASH, check not for CONFIG_ENV_ADDR being set but
    rather it being non-zero, as it will now be zero by default.
    - Rework the env_offset absolute in env/embedded.o to not use
    CONFIG_ENV_OFFSET as it was the only use of ENV_OFFSET within
    ENV_IS_IN_FLASH.
    - Migrate all platforms.

    Cc: Wolfgang Denk
    Cc: Joe Hershberger
    Cc: Patrick Delaunay
    Cc: uboot-stm32@st-md-mailman.stormreply.com
    Signed-off-by: Tom Rini
    Acked-by: Joe Hershberger
    Reviewed-by: Simon Goldschmidt

    Tom Rini
     
  • Today in initr_reloc_global_data() we use some non-obvious tests to
    determine if we need to relocate the env_addr within gd or not. In
    order to facilitate migration of other symbols to Kconfig we need to
    introduce a new symbol for this particular use case.

    Cc: Wolfgang Denk
    Cc: Joe Hershberger
    Signed-off-by: Tom Rini

    Tom Rini
     

24 Aug, 2019

1 commit


18 Aug, 2018

1 commit


17 Aug, 2018

1 commit

  • We have the following cases:
    - CONFIG_NR_DRAM_BANKS was defined, migrate normally
    - CONFIG_NR_DRAM_BANKS_MAX was defined and then used for
    CONFIG_NR_DRAM_BANKS after a check, just migrate it over now.
    - CONFIG_NR_DRAM_BANKS was very oddly defined on p2771-0000-* (to 1024 +
    2), set this to 8.

    Signed-off-by: Tom Rini

    Tom Rini
     

11 Feb, 2018

1 commit

  • On the NIOS2 and Xtensa architectures, we do not have
    CONFIG_SYS_TEXT_BASE set. This is a strict migration of the current
    values into the defconfig and removing them from the headers.

    I did not attempt to add more default values in and for now will leave
    that to maintainers.

    Signed-off-by: Tom Rini

    Tom Rini
     

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


11 Aug, 2017

1 commit


08 Aug, 2017

1 commit

  • move to Kconfig:
    CONFIG_BCM_SF2_ETH
    CONFIG_BCM_SF2_ETH_DEFAULT_PORT
    CONFIG_BCM_SF2_ETH_GMAC

    Also modified defconfigs of all platforms that use these configs.

    Signed-off-by: Suji Velupillai
    Tested-by: Suji Velupillai
    Reviewed-by: JD Zheng
    Reviewed-by: Scott Branden
    Signed-off-by: Steve Rae
    Reviewed-by: Tom Rini
    Acked-by: Joe Hershberger

    Suji Velupillai
     

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
     

28 Jan, 2017

2 commits


30 Dec, 2016

2 commits

  • 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 '
    s/CONFIG_MMC_SDMA/CONFIG_MMC_SDHCI_SDMA/g
    s/CONFIG_BCM2835_SDHCI/CONFIG_MMC_SDHCI_BCM2835/g
    s/CONFIG_KONA_SDHCI/CONFIG_MMC_SDHCI_KONA/g
    s/CONFIG_MV_SDHCI/CONFIG_MMC_SDHCI_MV/g
    s/CONFIG_S5P_SDHCI/CONFIG_MMC_SDHCI_S5P/g
    s/CONFIG_SPEAR_SDHCI/CONFIG_MMC_SDHCI_SPEAR/g
    '

    [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 \
    MMC_SDHCI_KONA MMC_SDHCI_MV MMC_SDHCI_S5P MMC_SDHCI_SPEAR

    [4] Sort drivers/mmc/Makefile for readability

    Signed-off-by: Masahiro Yamada
    Reviewed-by: Tom Rini
    Reviewed-by: Jaehoon Chung

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

    Masahiro Yamada
     

12 Oct, 2016

2 commits


10 Sep, 2016

1 commit


20 Jun, 2016

1 commit

  • Since commit bb597c0eeb7e ("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
    endif

    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: Masahiro Yamada

    Masahiro Yamada
     

13 Jun, 2016

1 commit


10 Jun, 2016

1 commit


07 Jun, 2016

1 commit

  • 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: Andre Przywara
    Signed-off-by: Steve Rae
    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
    END
    Reviewed-by: Tom Rini

    Andre Przywara
     

26 Apr, 2016

3 commits


20 Apr, 2016

3 commits


26 Mar, 2016

1 commit

  • The description was borrowed from kernel. "tristate" type was changed
    to "bool" (I believe we don't support modules for u-boot yet, right?).
    CONFIG_USB_GADGET requires CONFIG_USB to be defined too, so add it along
    as well.

    Definitions were added to defconfig files in a way that
    "make savedefconfig" generates exactly the same file as used defconfig.

    Signed-off-by: Sam Protsenko
    [trini: Add zynq_zc702 conversion]
    Signed-off-by: Tom Rini

    Sam Protsenko
     

22 Nov, 2015

1 commit


19 Nov, 2015

1 commit


26 Jun, 2015

1 commit


13 May, 2015

1 commit

  • In order to reduce merge conflicts and to maintain the simplest possible
    defconfig files, we should be using the savedefconfig feature of Kconfig
    every time a new feature is added. This keeps the defconfig settings to
    a minimum (only those things not default) and keeps them in the same
    order as the Kconfig options.

    Signed-off-by: Joe Hershberger
    Cc: Masahiro Yamada
    Acked-by: Stephen Warren
    Cc: Tom Rini

    Joe Hershberger
     

30 Aug, 2014

1 commit