10 Mar, 2020

1 commit

  • Convert imx6sabresd ethernet to driver model to fix the following warning:

    ===================== WARNING ======================
    This board does not use CONFIG_DM_ETH (Driver Model
    for Ethernet drivers). Please update the board to use
    CONFIG_DM_ETH before the v2020.07 release. Failure to
    update by the deadline may result in board removal.
    See doc/driver-model/migration.rst for more info.
    ====================================================

    Signed-off-by: Alifer Moraes
    Reviewed-by: Fabio Estevam

    Alifer Moraes
     

09 Feb, 2020

1 commit

  • Convert imx6sabresd PCI to driver model to fix the following warning:

    ===================== WARNING ======================
    This board does not use CONFIG_DM_PCI Please update
    the board to use CONFIG_DM_PCI before the v2019.07 release.
    Failure to update by the deadline may result in board removal.
    See doc/driver-model/MIGRATION.txt for more info.
    ====================================================

    After the conversion the following commands were used for testing:

    => pci enum
    PCI: Failed autoconfig bar 10
    PCI: Failed autoconfig bar 10
    => pci 1
    Scanning PCI devices on bus 1
    BusDevFun VendorId DeviceId Device Class Sub-Class
    Reviewed-by: Fabio Estevam

    Alifer Moraes
     

07 Feb, 2020

1 commit

  • This partially reverts changes by commit 2cc393f32fd9
    ("video: make BPP and ANSI configs optional") since it
    caused issues with other boards (missing LCD console
    output on pinebook, x86 platform or sandbox). Enable
    all disabled options again and opt out of not supported
    color depth in board defconfigs.

    Signed-off-by: Anatolij Gustschin
    Reported-by: Vagrant Cascadian

    Anatolij Gustschin
     

23 Jan, 2020

1 commit


06 Dec, 2019

1 commit

  • Many boards do not use all selected framebuffer depth
    configurations, for such boards there is some unused
    code in video and console uclass routines. Make depth
    specific code optional to avoid dead code and slightly
    reduce binary size. Also make ANSI code optional for
    the same reason. When i.e. using only VIDEO_BPP16 the
    code size shrinks (below values when using gcc-7.3.0):

    $ ./tools/buildman/buildman -b video-wip -sS wandboard
    ...
    01: Merge git://git.denx.de/u-boot-sh
    02: video: add guards around 16bpp/32bbp code
    03: video: make BPP and ANSI configs optional
    arm: (for 1/1 boards) all -776.0 bss -8.0 text -768.0

    Signed-off-by: Anatolij Gustschin
    Tested-by: Eugen Hristev
    Tested-by: Patrice Chotard
    Tested-by: Steffen Dirkwinkel

    Anatolij Gustschin
     

05 Dec, 2019

2 commits


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


08 Oct, 2019

2 commits

  • Enable CONFIG_DM_REGULATOR_FIXED to let vbus regulator work.

    Signed-off-by: Peng Fan

    Peng Fan
     
  • Currently the SPL binary is 67 kB, which leaves only 1 kB of free
    internal RAM space.

    The following options can be safely removed to save some precious
    SPL space:

    - CONFIG_SPL_FS_EXT4: u-boot-dtb.img is stored in raw sector via dd
    command (at offset 69 kB)
    - CONFIG_SPL_I2C_SUPPORT: I2C is not used during SPL
    - CONFIG_SPL_OS_BOOT: no need to make Falcon mode supported
    by default

    After this change the SPL binary size gets down to 51 kB.

    Signed-off-by: Fabio Estevam
    Reviewed-by: Peng Fan

    Fabio Estevam
     

23 Sep, 2019

1 commit


21 Sep, 2019

1 commit


24 Aug, 2019

1 commit


23 Jun, 2019

1 commit


21 Jun, 2019

1 commit


11 Jun, 2019

2 commits

  • With the conversion to DM we should select the pinctrl driver.

    Signed-off-by: Fabio Estevam

    Fabio Estevam
     
  • Currently the mx6qsabresd board does not boot:

    U-Boot SPL 2019.07-rc2 (May 16 2019 - 14:28:55 -0300)
    Trying to boot from MMC1
    spl: could not find mmc device 0. error: -19
    SPL: failed to boot from all boot devices
    ### ERROR ### Please RESET the board ###

    The reason for the boot failure is that that the SPL
    size got greater than the 68KB limit (4KB header + 64KB max
    size) as explained in include/configs/imx6_spl.h.

    Remove the CONFIG_SPL_DM option, so that the SPL binary could
    fit into the allowed size and the board can boot again.

    Signed-off-by: Fabio Estevam

    Fabio Estevam
     

20 May, 2019

1 commit

  • Meet the following boot hang.
    "
    U-Boot SPL 2019.04-00661-gdc80a012e4 (Apr 25 2019 - 10:31:57 +0800)
    Trying to boot from MMC1

    U-Boot 2019.04-00661-gdc80a012e4 (Apr 25 2019 - 10:31:57 +0800)

    CPU: Freescale i.MX6Q rev1.5 996 MHz (running at 792 MHz)
    CPU: Automotive temperature grade (-40C to 125C)Reset cause: POR
    Model: Freescale i.MX6 Quad SABRE Smart Device Board
    Board: MX6-SabreSD
    I2C: ready
    DRAM: 1 GiB
    Video device 'ipu@2400000' cannot allocate frame buffer memory -ensure the device is set up before relocation
    Error binding driver 'ipuv3_video': -28
    Video device 'ipu@2800000' cannot allocate frame buffer memory -ensure the device is set up before relocation
    Error binding driver 'ipuv3_video': -28
    Some drivers failed to bind
    Error binding driver 'generic_simple_bus': -28
    Some drivers failed to bind
    initcall sequence 4ffe4500 failed at call 1780dfb7 (err=-28)
    "

    1. fdtdec_get_alias_seq will use "video" as base, however in alias node,
    we use ipux, so add new alias for U-Boot dts.
    2. DM_VIDEO is enabled, however reserve_video is called before
    relocation, so to make DM_VIDEO work before relocation, need to
    set SYS_MALLOC_F_LEN
    3. defconfig is updated with savedefconfig

    Note: I do not have a video panel to test, but with this patch, U-Boot
    boots up again, below log.

    "
    U-Boot SPL 2019.04-00662-g0b62453bff (Apr 25 2019 - 10:36:31 +0800)
    Trying to boot from MMC1

    U-Boot 2019.04-00662-g0b62453bff (Apr 25 2019 - 10:36:31 +0800)

    CPU: Freescale i.MX6Q rev1.5 996 MHz (running at 792 MHz)
    CPU: Automotive temperature grade (-40C to 125C) at 34C
    Reset cause: POR
    Model: Freescale i.MX6 Quad SABRE Smart Device Board
    Board: MX6-SabreSD
    I2C: ready
    DRAM: 1 GiB
    PMIC: PFUZE100 ID=0x10
    MMC: FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 3
    Loading Environment from MMC... *** Warning - bad CRC, using default environment

    PCI: pcie phy link never came up
    In: serial
    Out: serial
    Err: serial
    Net: FEC [PRIME]
    Hit any key to stop autoboot: 0
    "

    Signed-off-by: Peng Fan
    Reviewed-by: Anatolij Gustschin

    Peng Fan
     

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


14 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
     

22 Feb, 2019

1 commit


16 Feb, 2019

4 commits


01 Feb, 2019

1 commit


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
     

11 Jan, 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
     

04 Jun, 2018

1 commit


30 May, 2018

1 commit

  • Separate CMD_FASTBOOT from FASTBOOT and move code and configuration to
    drivers/fastboot.

    Switch dependencies on FASTBOOT to USB_FUNCTION_FASTBOOT as anyone who wants
    FASTBOOT before this series wants USB_FUNCTION_FASTBOOT. Split
    USB_FUNCTION_FASTBOOT from FASTBOOT so they retain their existing
    behaviour.

    Signed-off-by: Alex Kiernan
    Reviewed-by: Simon Glass
    Acked-by: Joe Hershberger

    Alex Kiernan
     

28 Apr, 2018

1 commit

  • This converts the following to Kconfig:
    CONFIG_SPI

    This partly involves updating code that assumes that CONFIG_SPI implies
    things that are specific to the MPC8xx SPI driver. For now, just update
    the CONFIG tests. This also involves reworking the default for
    CONFIG_SYS_DEF_EEPROM_ADDR so that we don't set it when we cannot make a
    reasonable default, as it does not cause any compile failures.

    Signed-off-by: Adam Ford
    Signed-off-by: Tom Rini

    Adam Ford
     

09 Apr, 2018

1 commit