1. 27 Jul, 2021 1 commit
  2. 26 Jul, 2021 20 commits
  3. 24 Jul, 2021 14 commits
  4. 23 Jul, 2021 5 commits
    • Chen Baozi's avatar
      serial: pl011: Resend the character if FIFO is full in debug uart · 19820150
      Chen Baozi authored and Tom Rini's avatar Tom Rini committed
      
      
      pl01x_putc() might return -EAGAIN if there was no space in FIFO. In that
      case, high-level caller should wait until there is space and resend the
      character.
      Signed-off-by: default avatarChen Baozi <chenbaozi@phytium.com.cn>
      Reviewed-by: Stefan Roese's avatarStefan Roese <sr@denx.de>
      Reviewed-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
      19820150
    • Siew Chin Lim's avatar
      command: Fix SMC and HVC maximum number of arguments · 8f20c480
      Siew Chin Lim authored and Tom Rini's avatar Tom Rini committed
      
      
      smc and hvc commands take upto 8 user input arguments, the maximum
      number of arguments of the U_BOOT_CMD macro should set to 9.
      
      Besides, fix the typo (arg7 -> arg6) in hvc command's help message.
      Signed-off-by: default avatarSiew Chin Lim <elly.siew.chin.lim@intel.com>
      Reviewed-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
      8f20c480
    • Peter Hoyes's avatar
      armv8: Initialize CNTFRQ if at highest exception level · c48fec6e
      Peter Hoyes authored and Tom Rini's avatar Tom Rini committed
      
      
      CNTFRQ_EL0 is only writable from the highest supported exception
      level on the platform. For Armv8-A, this is typically EL3, but
      technically EL2 and EL3 are optional so it may need to be
      initialized at EL2 or EL1. For Armv8-R, the highest exception
      level is always EL2.
      
      This patch moves the initialization outside of the switch_el
      block and uses a new macro branch_if_not_highest_el which
      dynamically detects whether it is at the highest supported
      exception level.
      
      Linux's docs state that CNTFRQ_EL0 should be initialized by the
      bootloader. If not set, the the U-Boot prompt countdown hangs.
      Signed-off-by: default avatarPeter Hoyes <Peter.Hoyes@arm.com>
      c48fec6e
    • Stephan Gerhold's avatar
      serial: serial_msm: Delay initialization to let pins stabilize · ad7e9677
      Stephan Gerhold authored and Tom Rini's avatar Tom Rini committed
      
      
      For some reason, the DragonBoard 410c aborts autoboot immediately if
      U-Boot is started without LK. It looks like it picks up a single broken
      character via serial and therefore believes a key was pressed to abort
      autoboot.
      
      After some debugging, it seems like adding some delay after pinctrl
      setup but before UART initialization fixes the issue. It's also worth
      mentioning that unlike when booting from LK, the pinctrl setup is
      actually necessary when booting U-Boot without LK since UART is broken
      if the pinctrl line is removed.
      
      I suspect that reconfiguring the pins might take some time to stabilize
      and if the UART controller is enabled too quickly it will pick up some
      random noise. Adding a few milliseconds of delay fixes the issue and
      shouldn't have any other negative side effects.
      
      3ms seems to be the minimum delay required in my tests, use 5ms instead
      just to be sure.
      Signed-off-by: default avatarStephan Gerhold <stephan@gerhold.net>
      ad7e9677
    • Stephan Gerhold's avatar
      board: dragonboard410c: Fix fastboot · ccb8de23
      Stephan Gerhold authored and Tom Rini's avatar Tom Rini committed
      At the moment pressing the volume down key does not actually launch
      fastboot. This is because setting "bootdelay" to "-1" actually
      disables autoboot and drops to the U-Boot console. It does not execute
      the "bootcmd".
      
      The correct value for "bootdelay" here would be "-2", which disables
      the delay and key checking and would immediately execute the "bootcmd".
      
      However, even better in this case is using "preboot" to trigger Fastboot.
      The advantage is that running "fastboot continue" will actually continue
      the autoboot process instead of ending up in the U-Boot shell.
      
      Also make sure to unset "preboot" again immediately in case the user
      saves the environment after triggering fastboot.
      
      Cc: Ramon Fried <rfried.dev@gmail.com>
      Fixes: aa043ee9
      
       ("db410c: automatically launch fastboot")
      Signed-off-by: default avatarStephan Gerhold <stephan@gerhold.net>
      Reviewed-by: Ramon Fried's avatarRamon Fried <rfried.dev@gmail.com>
      ccb8de23