01 Jul, 2022

1 commit

08 Apr, 2021

1 commit

25 Aug, 2020

1 commit

16 Apr, 2020

1 commit

29 Oct, 2019

2 commits

  • Optee has 4MB shared memory at its top space which was assigned to
    non-secure OS partition in ATF. By default this memory is added to
    u-boot DDR banks and will pass to kernel. This means kernel has possibility
    to allocate from this memory for system usage. At same time this memory is
    used by optee and mem-remapped by optee kernel driver. So it is possible to
    have conflict and cause kernel crash.

    Fix the issue by removing the shared memory from u-boot DDR banks. Then it
    is not visible for both u-boot and kernel and can avoid such issue.

    Signed-off-by: Ye Li
    Reviewed-by: Anson Huang
    (cherry picked from commit 164279c42de0d058b7abe198cc154ee683087e6a)

    Ye Li
  • In MLK-22582, write memcmp incorrectly as memcpy.

    Signed-off-by: Alice Guo
    (cherry picked from commit 16a073f563a25401f1ec289db1c82dd8dab61601)

    Alice Guo

28 Oct, 2019

8 commits

25 Oct, 2019

4 commits

24 Oct, 2019

4 commits

  • Refine trusty logs output to make it more

    Test: boots.

    Change-Id: Id94fc245206c5f78e0dbcb0baf5db6475c9f744d
    Signed-off-by: Ji Luo

    Ji Luo
  • Since commit c98b47f1ff60 ("MLK-22749 imx8mq: Add workaround to fix sticky
    bits lock up") it's not possible to build i.MX8MM and i.MX8MN targets with

    CC cmd/version.o
    arch/arm/mach-imx/imx8m/soc.c:326:23: error: ‘CONFIG_IMX_UNIQUE_ID’ undeclared \
    (first use in this function); did you mean ‘CONFIG_IMX_VIDEO_SKIP’?
    if (!is_uid_matched(CONFIG_IMX_UNIQUE_ID))

    The OCOTP sticky bit workaround is only needed for i.MX8MQ devices, other devices
    should not build the secure_lockup() function.

    Add CONFIG_IMX8MQ to the conditional compilation to avoid such issue.

    Fixes: c98b47f1ff60 ("MLK-22749 imx8mq: Add workaround to fix sticky bits lock up")
    Signed-off-by: Breno Lima
    Reviewed-by: Ye Li
    (cherry picked from commit be033bff3c718e8bd7d4ac5ecfe4361892fc6e61)

    Breno Lima
  • When enabled randomizer during ECC reading, the controller reported it's
    erased page. Checking zero count will cause data get modified to all
    0xFF. Stop checking during randomizer to workaround this issue.

    Signed-off-by: Han Xu
    (cherry picked from commit f88f68f29026b084396db003c60e0c15995d1670)

    Han Xu
  • add the missing bch register debug0

    Signed-off-by: Han Xu
    (cherry picked from commit 0883946855f7e1eabe26787fbc8529ac412047e7)

    Han Xu

22 Oct, 2019

1 commit

17 Oct, 2019

4 commits

  • According to i.MX7ULP Reference Manual we should wait for WDOG unlock
    and reconfiguration to complete.

    Section "59.5.3 Configure Watchdog" provides the following example:

    DisableInterrupts; //disable global interrupt
    WDOG_CNT = 0xD928C520; //unlock watchdog
    while(WDOG_CS[ULK]==0); //wait until registers are unlocked
    WDOG_TOVAL = 256; //set timeout value
    while(WDOG_CS[RCS]==0); //wait until new configuration takes effect
    EnableInterrupts; //enable global interrupt

    Update U-Boot WDOG driver to align with i.MX7ULP reference manual.

    Reviewed-by: Ye Li
    Signed-off-by: Breno Lima
    (cherry picked from commit 3ffee301cb4570e0e7681448ec434f0689bcbaa3)

    Breno Lima
  • remove the unnecessary space in imx6sx sabreauto mtdparts

    Signed-off-by: Han Xu
    (cherry picked from commit c8bbf2b43767fe7be69a0383ab426172b5083ee1)

    Han Xu
  • Enable the mtdparts for imx6sx sabreauto platform

    Signed-off-by: Han Xu
    (cherry picked from commit d76d7e0a28c04a51265b8777a82033bd2e74eda5)

    Han Xu
  • With Android10 code, to build GSI image for devices launching with
    Android10, the target should be "aosp_$arch-user". Google releases GSI
    images is so built in user mode.

    To do CTS-on-GSI test, a debug ramdisk containing .prop file to enable
    adb root permission and GSI keys to verify the GSI image is needed, this
    ramdisk is in boot image. so ramdisk in boot image need to be loaded by
    uboot even in non-recovery mode.

    To save boot time, only standard Android use ramdisk to boot up Android,
    Android Auto keeps the original way: kernel be responsible for verify
    and mount system partition. Let the customers to decide whether to use
    recovery ramdisk to boot the system. and under this condition, user-debug
    Android Auto GSI image need to be used for VTS-on-GSI test.

    when use ramdisk to bootup Android, info provided by "dm=" bootarg is
    not used by kernel to setup dm-verity, so it is removed from the
    bootargs. The 4.19 kernel used together with this uboot does not handle
    "skip_initramfs", so it's also removed.

    Change-Id: Ia8b8fa8b85a44acda2670b46504038a009ce01a8
    Signed-off-by: faqiang.zhu


16 Oct, 2019

4 commits

15 Oct, 2019

6 commits

12 Oct, 2019

2 commits

11 Oct, 2019

1 commit

  • Current flexspi driver enables the Quad DTR read, so the measured
    100Mhz SCLK is actually for DTR mode not SDR. However, according to
    MT25QU256ABA datasheet, this flash only supports max DTR at 90Mhz and
    max SDR at 166Mhz. It means current clock setting violate the flash
    spec. So change back the flexspi clock to align with imx8mm.

    Signed-off-by: Ye Li
    Reviewed-by: Peng Fan
    (cherry picked from commit 3bf41bae974003550b70ea1a8b44ccb3117d818f)
    (cherry picked from commit 4a369b527c3842751a4edf0171562a0e40c331ba)

    Ye Li