1. 19 May, 2021 13 commits
  2. 18 May, 2021 14 commits
  3. 17 May, 2021 11 commits
    • Ley Foon Tan's avatar
      MAINTAINERS, git-mailrc: socfpga: Update email address for Ley Foon · af02975e
      Ley Foon Tan authored and Tom Rini's avatar Tom Rini committed
      My mail address doesn't work any longer, change to gmail.
      Signed-off-by: default avatarLey Foon Tan <ley.foon.tan@intel.com>
    • Simon Glass's avatar
      Makefile: Handle building in a very old build directory · a7d03d53
      Simon Glass authored and Tom Rini's avatar Tom Rini committed
      Versions of U-Boot before 2014.01 created a symlink from include/asm to
      the architecture-specific header directory.
      If an ARM board is build with that old version, then sandbox is built on
      a more recent version (both with in-tree builds), the include/asm symlink
      confuses the build system. It picks up the ARM headers when it should be
      using the sandbox ones.
      Since 2014 U-Boot has only created a symlink inside the include/asm/
      directory and only for out-of-tree builds. So for in-tree builds it does
      not expect to see an include/asm symlink. It is not removed by
      'make mrproper'. It does show up with 'git status' but is easy enough to
      Add include/asm to the files to remove with 'make mkproper'. For recent
      U-Boot builds this has no effect, since include/asm is a directory, not a
      file. If the include/asm symlink is there, it will be removed.
      Reported-by: default avatarMarek Szyprowski <m.szyprowski@samsung.com>
      Signed-off-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
    • Igor Opaniuk's avatar
      psci: rename psci_features function · eefa9d7f
      Igor Opaniuk authored and Tom Rini's avatar Tom Rini committed
      s/psci_features/request_psci_features/g for the case when both
      ARCH_SUPPORT_PSCI=y and ARM_PSCI_FW=y, that leads to these
      compilation issues:
      drivers/firmware/psci.c:69:12: error: conflicting types for 'psci_features'
         69 | static int psci_features(u32 psci_func_id)
            |            ^~~~~~~~~~~~~
      In file included from drivers/firmware/psci.c:23:
      ./arch/arm/include/asm/system.h:548:5: note: previous declaration of 'psci_features' was here
        548 | s32 psci_features(u32 function_id, u32 psci_fid);
            |     ^~~~~~~~~~~~~
      Tested-by: default avatarAlexandru Gagniuc <mr.nuke.me@gmail.com>
      Reported-by: default avatarAlexandru Gagniuc <mr.nuke.me@gmail.com>
      Fixes: b7135b03
       ("psci: add features/reset2 support")
      Signed-off-by: default avatarIgor Opaniuk <igor.opaniuk@foundries.io>
    • peng.wang@smartm.com's avatar
      cli: slighly more clear error messages · 6c353b34
      peng.wang@smartm.com authored and Tom Rini's avatar Tom Rini committed
      This patch tries to distinguish two error messages.
      Signed-off-by: default avatarpeng.wang@smartm.com <peng.wang@smartm.com>
    • Andrey Zhizhikin's avatar
      Makefile: allow to override python3 · f68ed0bc
      Andrey Zhizhikin authored and Tom Rini's avatar Tom Rini committed
      Python3 taken from the PATH causes build issues when pylibfdt bindings are
      generated with Yocto SDK.
      Python3 provided as a part of SDK is not compatible with host Python3,
      therefore binding build breaks with following errors:
      scripts/dtc/pylibfdt/libfdt_wrap.c:154:11: fatal error: Python.h: No such file or directory
        154 | # include <Python.h>
            |           ^~~~~~~~~~
      Do not enforce the python3 from the PATH and make it conditionally-assigned
      so it can be overridden from outside of build system. Keep the default
      assignment to point to version that is taken from the PATH.
      Similar fix has been introduced in b48bfc74
       ("tools: allow to override
      python"), where conditional assignment is used for python executable to
      address similar build errors.
      Signed-off-by: default avatarAndrey Zhizhikin <andrey.zhizhikin@leica-geosystems.com>
      Cc: Simon Glass <sjg@chromium.org>
      Fixes: e91610da
       ("kconfig: re-sync with Linux 4.17-rc4")
      Reviewed-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
    • Tom Rini's avatar
      Merge https://source.denx.de/u-boot/custodians/u-boot-marvell · feddbdb5
      Tom Rini authored
      - Add base support for Marvell OcteonTX2 CN9130 DB (mostly done
        by Kostya)
      - Sync Armada 8k MMU setup with Marvell version (misc Marvell
      - spi: kirkwood: Some fixes especially for baudrate generation
        (misc Marvell authors)
      - mvebu: x530: Reduce SPL image size (Stefan)
      - Rename "rx_training" to "mvebu_comphy_rx_training" (Stefan)
    • Bin Meng's avatar
      riscv: Group assembly optimized implementation of memory routines into a submenu · 89419279
      Bin Meng authored
      Currently all assembly optimized implementation of memory routines
      show up at the top level of the RISC-V architecture Kconfig menu.
      Let's group them together into a submenu.
      Signed-off-by: Bin Meng's avatarBin Meng <bmeng.cn@gmail.com>
    • Bin Meng's avatar
      riscv: Fix memmove and optimise memcpy when misalign · 703b84ec
      Bin Meng authored
      At present U-Boot SPL fails to boot on SiFive Unleashed board, due
      to a load address misaligned exception happens when loading the FIT
      image in spl_load_simple_fit(). The exception happens in memmove()
      which is called by fdt_splice_().
      Commit 8f0dc4cf introduces an assembly version of memmove but
      it does take misalignment into account (it checks if length is a
      multiple of machine word size but pointers need also be aligned).
      As a result it will generate misaligned load/store for the majority
      of cases and causes significant performance regression on hardware
      that traps misaligned load/store and emulate them using firmware.
      The current behaviour of memcpy is that it checks if both src and
      dest pointers are co-aligned (aka congruent modular SZ_REG). If
      aligned, it will copy data word-by-word after first aligning
      pointers to word boundary. If src and dst are not co-aligned,
      however, byte-wise copy will be performed.
      This patch was taken from the Linux kernel patch [1], which has not
      been applied at the time being. It fixes the memmove and optimises
      memcpy for misaligned cases. It will first align destination pointer
      to word-boundary regardless whether src and dest are co-aligned or
      not. If they indeed are, then wordwise copy is performed. If they
      are not co-aligned, then it will load two adjacent words from src
      and use shifts to assemble a full machine word. Some additional
      assembly level micro-optimisation is also performed to ensure more
      instructions can be compressed (e.g. prefer a0 to t6).
      With this patch, U-Boot boots again on SiFive Unleashed board.
      [1] https://patchwork.kernel.org/project/linux-riscv/patch/20210216225555.4976-1-gary@garyguo.net/
      Fixes: 8f0dc4cf
       ("riscv: assembler versions of memcpy, memmove, memset")
      Signed-off-by: Bin Meng's avatarBin Meng <bmeng.cn@gmail.com>
    • Sean Anderson's avatar
      riscv: Fix arch_fixup_fdt always failing without /chosen · e90cb0db
      Sean Anderson authored
      If /chosen was missing, chosen_offset would never get updated with the new
      /chosen node. This would cause fdt_setprop_u32 to fail. This patch fixes
      this by setting chosen_offset. In addition, log any errors from setting
      boot-hartid as well.
      Fixes: 5370478d
       ("riscv: Add boot hartid to device tree")
      Signed-off-by: Sean Anderson's avatarSean Anderson <seanga2@gmail.com>
      Reviewed-by: Bin Meng's avatarBin Meng <bmeng.cn@gmail.com>
      Reviewed-by: Rick Chen's avatarRick Chen <rick@andestech.com>
      Reviewed-by: default avatarAtish Patra <atish.patra@wdc.com>
    • Bin Meng's avatar
      riscv: Split SiFive CLINT support between SPL and U-Boot proper · a6d7e8c9
      Bin Meng authored
      At present there is only one Kconfig option CONFIG_SIFIVE_CLINT to
      control the enabling of SiFive CLINT support in both SPL (M-mode)
      and U-Boot proper (S-mode). So for a typical SPL config that the
      SiFive CLINT driver is enabled in both SPL and U-Boot proper, that
      means the S-mode U-Boot tries to access the memory-mapped CLINT
      registers directly, instead of the normal 'rdtime' instruction.
      This was not a problem before, as the hardware does not forbid the
      access from S-mode. However this becomes an issue now with OpenSBI
      commit 8b569803475e ("lib: utils/sys: Add CLINT memregion in the root domain")
      that the SiFive CLINT register space is protected by PMP for M-mode
      access only. U-Boot proper does not boot any more with the latest
      OpenSBI, that access exceptions are fired forever from U-Boot when
      trying to read the timer value via the SiFive CLINT driver in U-Boot.
      To solve this, we need to split current SiFive CLINT support between
      SPL and ...
    • Bin Meng's avatar
      riscv: ax25-ae350: doc: Fix minor format issues · 2b039940
      Bin Meng authored
      This fixes two minor format issues of the ax25-ae350 reST file.
      Signed-off-by: Bin Meng's avatarBin Meng <bmeng.cn@gmail.com>
      Reviewed-by: Rick Chen's avatarRick Chen <rick@andestech.com>
  4. 16 May, 2021 2 commits