1. 30 Sep, 2021 3 commits
  2. 28 Sep, 2021 2 commits
  3. 27 Sep, 2021 2 commits
  4. 25 Sep, 2021 5 commits
  5. 24 Sep, 2021 1 commit
  6. 18 Sep, 2021 1 commit
  7. 17 Sep, 2021 1 commit
  8. 16 Sep, 2021 1 commit
  9. 11 Sep, 2021 4 commits
  10. 10 Sep, 2021 1 commit
  11. 09 Sep, 2021 1 commit
  12. 04 Sep, 2021 5 commits
  13. 03 Sep, 2021 2 commits
  14. 02 Sep, 2021 2 commits
  15. 01 Sep, 2021 2 commits
    • Stephan Gerhold's avatar
      board: stemmy: Update documentation · f629895f
      Stephan Gerhold authored and Tom Rini's avatar Tom Rini committed
      Over the time, the "stemmy" U-Boot board was tested on several other
      Samsung smartphones based on ST-Ericsson NovaThor Ux500. Convert the
      documentation to reStructuredText at doc/board/ste/stemmy.rst and
      make the device list complete. Also note that the board now boots
      into USB Fastboot instead of just ending up at the U-Boot prompt.
      
      The device table is mostly taken from the postmarketOS wiki article
      (https://wiki.postmarketos.org/wiki/ST-Ericsson_NovaThor_U8500
      
      ).
      All the newly added devices were tested by Linus Walleij.
      Signed-off-by: default avatarStephan Gerhold <stephan@gerhold.net>
      f629895f
    • Tom Rini's avatar
      scripts/checkpatch.pl: Resync with v5.13 · e199fb35
      Tom Rini authored
      
      
      This resyncs us with the version found in v5.13 of the Linux kernel with
      the following exceptions:
      - Keep our u-boot specific tests / code area.
      - Change the location of checkpatch.rst (which we now import)
      - Drop the "use strscpy" test as we don't have that, but do have strlcpy
        and want that used now.
      - Keep debug/printf in the list for $logFunctions
      
      And note that we now also include the spdxcheck.py tool that
      checkpatch.pl supports calling out to, and include upstream's
      checkpatch.rst in our develop section of the documentation.
      Signed-off-by: Tom Rini's avatarTom Rini <trini@konsulko.com>
      e199fb35
  16. 31 Aug, 2021 3 commits
    • Tom Rini's avatar
      Convert CONFIG_SKIP_LOWLEVEL_INIT et al to Kconfig · a2ac2b96
      Tom Rini authored
      
      
      This converts the following to Kconfig:
         CONFIG_SKIP_LOWLEVEL_INIT
         CONFIG_SKIP_LOWLEVEL_INIT_ONLY
      
      In order to do this, we need to introduce SPL and TPL variants of these
      options so that we can clearly disable these options only in SPL in some
      cases, and both instances in other cases.
      Signed-off-by: Tom Rini's avatarTom Rini <trini@konsulko.com>
      a2ac2b96
    • Tom Rini's avatar
      qfw: Switch to CONFIG_SYS_LOAD_ADDR from CONFIG_LOADADDR · 2f45b304
      Tom Rini authored
      
      
      All platforms define CONFIG_SYS_LOAD_ADDR, but only some define
      CONFIG_LOADADDR.  Very very rarely are these not the same address, and
      qemu-ppce500 is one such case.  However, based on reading the history of
      the code, this mismatched value was simply a copy-paste from other
      PowerPC platforms where it is this unused currently.  Switch the code to
      use CONFIG_SYS_LOAD_ADDR and update the documentation.
      
      Cc: Bin Meng <bmeng.cn@gmail.com>
      Signed-off-by: Tom Rini's avatarTom Rini <trini@konsulko.com>
      Reviewed-by: Bin Meng's avatarBin Meng <bmeng.cn@gmail.com>
      2f45b304
    • Rasmus Villemoes's avatar
      watchdog: add gpio watchdog driver · 2ac84904
      Rasmus Villemoes authored and Stefan Roese's avatar Stefan Roese committed
      A rather common kind of external watchdog circuit is one that is kept
      alive by toggling a gpio. Add a driver for handling such a watchdog.
      
      The corresponding linux driver apparently has support for some
      watchdog circuits which can be disabled by tri-stating the gpio, but I
      have never actually encountered such a chip in the wild; the whole
      point of adding an external watchdog is usually that it is not in any
      way under software control. For forward-compatibility, and to make DT
      describe the hardware, the current driver only supports devices that
      have the always-running property. I went a little back and forth on
      whether I should fail ->probe or only ->start, and ended up deciding
      ->start was the right place.
      
      The compatible string is probably a little odd as it has nothing to do
      with linux per se - however, I chose that to make .dts snippets
      reusable between device trees used with U-Boot and linux, and this is
      the (only) compatible string that linux' corresponding driver and DT
      binding accepts. I have asked whether one should/could add "wdt-gpio"
      to that binding, but the answer was no:
      
        https://lore.kernel.org/lkml/CAL_JsqKEGaFpiFV_oAtE+S_bnHkg4qry+bhx2EDs=NSbVf_giA@mail.gmail.com/
      
      
      
      If someone feels strongly about this, I can certainly remove the
      "linux," part from the string - it probably wouldn't the only place where
      one can't reuse a DT snippet as-is between linux and U-Boot.
      Reviewed-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
      Reviewed-by: Stefan Roese's avatarStefan Roese <sr@denx.de>
      Signed-off-by: default avatarRasmus Villemoes <rasmus.villemoes@prevas.dk>
      2ac84904
  17. 22 Aug, 2021 1 commit
  18. 17 Aug, 2021 3 commits