10 Mar, 2020

1 commit

  • Booting a mainline kernel in secure mode on i.MX7D causes only
    one CPU to be brought up.

    Change it to booting in non secure mode by default, which
    allows the two CPUs to be brought up.

    It does have a side effect of not probing the CAAM driver.
    If CAAM driver is needed then a secure world OS such as OPTEE needs
    to be used.

    Signed-off-by: Fabio Estevam

    Fabio Estevam
     

23 Jan, 2020

1 commit


07 Jan, 2020

2 commits


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
     

08 Nov, 2019

1 commit


05 Oct, 2019

1 commit


24 Aug, 2019

1 commit


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

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

1 commit


04 Sep, 2018

2 commits

  • CONFIG_CMD_MII is set without CONFIG_MII, build is broken.

    Signed-off-by: Stefano Babic

    Stefano Babic
     
  • On iMX7D SabreSD board, the QSPI has pins conflict with EPDC (default).
    To use QSPI, users have to rework the board (de-populate R388-R391, R396-R399
    populate R392-R395, R299, R300). So we add new DTS file and new defconfig
    dedicated for QSPI.

    Other changes to support the DM QSPI:
    - Add QSPI node and alias spi0.
    - Modify spi4 (spi-gpio) node and add alias spi5 for it to avoid req
    conflict
    - Add EPDC node in imx7d.dtsi and disable it in imx7d-sdb-qspi.dts to
    align with kernel and also present the conflict.
    - Add -u-boot.dtsi to modify compatible string of mx25l51245g@0 to
    "spi-flash"
    - Remove iomux settings of qspi in board codes which is not needed
    for DM driver.

    Signed-off-by: Ye Li

    Ye Li