1. 05 Nov, 2021 2 commits
  2. 06 Oct, 2021 1 commit
  3. 02 Oct, 2021 1 commit
  4. 30 Sep, 2021 1 commit
  5. 21 Sep, 2021 1 commit
  6. 13 Sep, 2021 1 commit
  7. 07 Sep, 2021 1 commit
    • Tom Rini's avatar
      arm: Finish migration of CONFIG_MACH_TYPE · 5f588f83
      Tom Rini authored
      
      
      As this is only useful when booting with ATAGs, which are now largely
      disabled, remove this value for the remaining platforms.  We have a few
      places in the code that had been testing for MACH_TYPE as a sort of
      internal logic.  Update those to use different but still correct CONFIG
      symbols.
      
      Cc: Phil Sutter <phil@nwl.cc>
      Signed-off-by: Tom Rini's avatarTom Rini <trini@konsulko.com>
      5f588f83
  8. 31 Aug, 2021 3 commits
  9. 30 Aug, 2021 9 commits
  10. 02 Aug, 2021 1 commit
  11. 28 Jul, 2021 2 commits
  12. 08 Jul, 2021 1 commit
    • Tom Rini's avatar
      arm: Remove edb9315a board · bc08dc56
      Tom Rini authored
      
      
      These boards have not been converted to CONFIG_DM_USB by the deadline
      and is also missing conversion to CONFIG_DM.  Remove it.
      
      This is also the last PL010_SERIAL using board, so remove those
      references.
      
      Cc: Sergey Kostanbaev <sergey.kostanbaev@fairwaves.ru>
      Signed-off-by: Tom Rini's avatarTom Rini <trini@konsulko.com>
      bc08dc56
  13. 07 Jul, 2021 1 commit
    • Tom Rini's avatar
      ppc: Remove sbc8641d board · 1c58857a
      Tom Rini authored
      
      
      This board has not been converted to CONFIG_DM_PCI by the deadline and is
      also missing conversion to CONFIG_DM.  Remove it.  This is also the last
      of the ARCH_MPC8641/MPC8610 platforms, so remove that support as well.
      
      Cc: Paul Gortmaker <paul.gortmaker@windriver.com>
      Cc: Priyanka Jain <priyanka.jain@nxp.com>
      Signed-off-by: Tom Rini's avatarTom Rini <trini@konsulko.com>
      Reviewed-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
      1c58857a
  14. 28 Apr, 2021 1 commit
    • Rasmus Villemoes's avatar
      allow opting out of WATCHDOG_RESET() from timer interrupt · 17bd5cce
      Rasmus Villemoes authored and Stefan Roese's avatar Stefan Roese committed
      
      
      Having WATCHDOG_RESET() called automatically from the timer interrupt
      runs counter to the idea of a watchdog device - if the board runs into
      an infinite loops with interrupts still enabled, the watchdog will
      never fire.
      
      When using CONFIG_(SPL_)WDT, the watchdog_reset function is a lot more
      complicated than just poking a few SOC-specific registers - it
      involves accessing all kinds of global data, and if the interrupt
      happens at the wrong time (say, in the middle of an WATCHDOG_RESET()
      call from ordinary code), that can end up corrupting said global data.
      
      Allow the board to opt out of calling WATCHDOG_RESET() from the timer
      interrupt handler by setting CONFIG_SYS_WATCHDOG_FREQ to 0 - as that
      setting is currently nonsensical (it would be compile-time
      divide-by-zero), it cannot affect any existing boards.
      
      Add documentation for both the existing and extended meaning of
      CONFIG_SYS_WATCHDOG_FREQ.
      Signed-off-by: default avatarRasmus Villemoes <rasmus.villemoes@prevas.dk>
      17bd5cce
  15. 27 Apr, 2021 1 commit
    • Rasmus Villemoes's avatar
      allow opting out of WATCHDOG_RESET() from timer interrupt · 933ada56
      Rasmus Villemoes authored and Stefan Roese's avatar Stefan Roese committed
      Having WATCHDOG_RESET() called automatically from the timer interrupt
      runs counter to the idea of a watchdog device - if the board runs into
      an infinite loops with interrupts still enabled, the watchdog will
      never fire.
      
      When using CONFIG_(SPL_)WDT, the watchdog_reset function is a lot more
      complicated than just poking a few SOC-specific registers - it
      involves accessing all kinds of global data, and if the interrupt
      happens at the wrong time (say, in the middle of an WATCHDOG_RESET()
      call from ordinary code), that can end up corrupting said global data.
      
      Allow the board to opt out of calling WATCHDOG_RESET() from the timer
      interrupt handler by setting CONFIG_SYS_WATCHDOG_FREQ to 0 - as that
      setting is currently nonsensical (it would be compile-time
      divide-by-zero), it cannot affect any existing boards.
      
      Add documentation for both the existing and extended meaning of
      CONFIG_SYS_WATCHDOG_FREQ.
      
      Signed-off-by: Rasmus Villemoes <rasmus.villemoes@preva...
      933ada56
  16. 28 Feb, 2021 1 commit
  17. 19 Feb, 2021 1 commit
    • André Przywara's avatar
      fdt/sunxi: Remove OF_STDOUT_PATH · e036a1d2
      André Przywara authored
      
      
      OF_STDOUT_PATH was meant to hold the devicetree path to the serial
      console, to be put into the linux,stdout-path property of the chosen node.
      
      The only user of that was sunxi, and it was actually wrong for years
      there: the paths hardcoded in sunxi_common.h were not matching the DTs,
      evident by the leading 0's in nodenames, which have been removed years
      ago.
      
      On top of that, "linux,stdout-path" is now deprecated for a while (Linux
      commit 2a9d832cc9aae from November 2014), and also all modern DTs
      (including those included in U-Boot) carry a "stdout-path" property
      already.
      
      So remove the stanza from sunxi_common.h, and, since this was the last
      user, also remove the associated bits from the rest of U-Boot.
      Signed-off-by: André Przywara's avatarAndre Przywara <andre.przywara@arm.com>
      Reviewed-by: Tom Rini's avatarTom Rini <trini@konsulko.com>
      Reviewed-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
      e036a1d2
  18. 27 Jan, 2021 1 commit
  19. 18 Jan, 2021 1 commit
  20. 01 Dec, 2020 1 commit
  21. 19 Nov, 2020 1 commit
  22. 22 Oct, 2020 6 commits
  23. 18 Oct, 2020 1 commit