29 Feb, 2020

1 commit


07 Feb, 2020

1 commit


23 Jan, 2020

1 commit


16 Jan, 2020

1 commit


04 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
     

13 Nov, 2019

1 commit


08 Nov, 2019

1 commit


04 Nov, 2019

1 commit

  • After the following commit:
    commit 772b55723bcb ("imx: Introduce CONFIG_SPL_FORCE_MMC_BOOT to force MMC
    boot on falcon mode")
    it is possible to set the CONFIG_SPL_FORCE_MMC_BOOT flag, which allows
    using MMC device as boot device regardless of the device used by Boot ROM
    (FBL) as the first boot medium.

    Display5 board needs this flag set to allow falcon boot from eMMC device.

    Signed-off-by: Lukasz Majewski

    Lukasz Majewski
     

09 Oct, 2019

1 commit


08 Oct, 2019

6 commits


23 Sep, 2019

1 commit


26 Aug, 2019

2 commits


24 Aug, 2019

1 commit


20 Jul, 2019

1 commit


23 Jun, 2019

1 commit


27 May, 2019

1 commit


05 May, 2019

1 commit

  • This converts the following to Kconfig:
    CONFIG_SUPPORT_EMMC_BOOT

    As requested by Michal Simek , these boards
    have no eMMC so CONFIG_SUPPORT_EMMC_BOOT has not been migrated:

    xilinx_zynqmp_zc1275_revB
    xilinx_zynqmp_zc1751_xm018_dc4
    xilinx_zynqmp_zc1751_xm019_dc5
    xilinx_zynqmp_zcu100_revC
    xilinx_zynqmp_zcu102_rev1_0
    xilinx_zynqmp_zcu102_revA
    xilinx_zynqmp_zcu102_revB
    xilinx_zynqmp_zcu104_revA
    xilinx_zynqmp_zcu104_revC
    xilinx_zynqmp_zcu106_revA
    xilinx_zynqmp_zcu111_revA

    Signed-off-by: Alex Kiernan
    Acked-by: Lukasz Majewski
    Acked-by: Patrick Delaunay
    Acked-by: Ramon Fried
    Reviewed-by: Andy Shevchenko
    Tested-by: Sébastien Szymanski

    Alex Kiernan
     

30 Apr, 2019

2 commits


26 Mar, 2019

1 commit

  • This converts the following to Kconfig:
    CONFIG_SF_DEFAULT_BUS
    CONFIG_SF_DEFAULT_CS
    CONFIG_SF_DEFAULT_MODE
    CONFIG_SF_DEFAULT_SPEED

    I use moveconfig script and then manual check on generated u-boot.cfg
    to solve the remaining issue.

    Signed-off-by: Patrick Delaunay

    Patrick Delaunay
     

07 Feb, 2019

1 commit

  • Now that new SPI NOR layer uses stateless 4 byte opcodes by default,
    don't enable SPI_FLASH_BAR. For SPI controllers that cannot support
    4-byte addressing, (stm32_qspi.c, fsl_qspi.c, mtk_qspi.c, ich.c,
    renesas_rpc_spi.c) add an imply clause to enable SPI_FLASH_BAR so as to
    not break functionality.

    Signed-off-by: Vignesh R
    Tested-by: Simon Goldschmidt
    Tested-by: Stefan Roese
    Tested-by: Horatiu Vultur
    Reviewed-by: Jagan Teki
    Tested-by: Jagan Teki #zynq-microzed

    Vignesh R
     

19 Jan, 2019

1 commit

  • The bounce buffer is used by a few drivers (most of the MMC drivers)
    to overcome limitations in their respective DMA implementation.

    This moves the configuration to Kconfig and makes it user-selectable
    (even though it will be a required feature to make those drivers
    work): the expected usage is for drivers depending on this to 'select'
    it unconditionally from their respective Kconfig (see follow-up
    patches).

    This commit includes a full migration using moveconfig.py to ensure
    that each commit compiles. To ensure bisectability we update
    dependencies of various drivers to now select BOUNCE_BUFFER when needed.

    [trini: Squash all patches to ensure bisectability]
    Signed-off-by: Tom Rini
    Signed-off-by: Philipp Tomsich
    Reviewed-by: Otavio Salvador [dw_mmc portion]
    Reviewed-by: Fabio Estevam [mxsmmc portion]
    Reviewed-by: Simon Glass [tegra portion]

    Philipp Tomsich
     

14 Nov, 2018

2 commits


22 Oct, 2018

1 commit


04 Sep, 2018

1 commit


18 Aug, 2018

3 commits

  • This converts the following to Kconfig:
    CONFIG_MISC_INIT_R

    Signed-off-by: Adam Ford
    [trini: Update the defaults logic slightly]
    Signed-off-by: Tom Rini

    Adam Ford
     
  • Migrate boards which set bootlimit in the environment to Kconfig.

    We exclude gurnard_defconfig which includes a bootlimit=, but doesn't set
    CONFIG_BOOTCOUNT_LIMIT, so we'd fail to include a bootlimit setting
    if we migrated it.

    display5_defconfig and display5_factory_defconfig share a SYS_CONFIG_NAME,
    but only display5_defconfig enables CONFIG_BOOTCOUNT_LIMIT, so we fail to
    set bootlimit= in display5_factory_defconfig. This is okay because the
    display5_factory_defconfig doesn't need to have it set, as it is only
    meant to prepare the board in the factory.

    Environment changes for all modified configs as seen from buildman:

    boards.cfg is up to date. Nothing to do.
    Summary of 3 commits for 32 boards (8 threads, 1 job per thread)
    01: Merge git://git.denx.de/u-boot-x86
    arm: + draco etamin rastaban pxm2 display5 thuban rut
    02: Add BOOTCOUNT_BOOTLIMIT to set reboot limit
    03: Migrate bootlimit to Kconfig
    - display5_factory: bootlimit=3

    Signed-off-by: Alex Kiernan
    Reviewed-by: Lukasz Majewski

    Alex Kiernan
     
  • This converts the following to Kconfig:
    CONFIG_MII
    CONFIG_DRIVER_TI_EMAC

    Signed-off-by: Adam Ford
    Acked-by: Jagan Teki
    Acked-by: Joe Hershberger

    Adam Ford
     

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
     

23 Jul, 2018

1 commit


10 Jul, 2018

1 commit