1. 30 Aug, 2020 20 commits
  2. 28 Aug, 2020 1 commit
    • Tom Rini's avatar
      Merge branch '2020-08-27-misc-fixes' · 9f04a634
      Tom Rini authored
      - Fix for gd->ram_top and bootm_size calculations
      - Assorted Kconfig entry cleanups / fixes.
      - Make checkpatch.pl error on fdt_high/initrd_high=0xffffffff
      - Resync scripts/setlocalversion
      - Other minor bugfixes
  3. 27 Aug, 2020 11 commits
    • Rasmus Villemoes's avatar
      scripts/setlocalversion: sync with linux 5.8 · 2ed1b242
      Rasmus Villemoes authored
      The linux changes since v3.16 are
      78283edf2c01 kbuild: setlocalversion: print error to STDERR
      b24413180f56 License cleanup: add SPDX GPL-2.0 license identifier to files with no license
      6147b1cf1965 scripts/setlocalversion: git: Make -dirty check more robust
      8ef14c2c41d9 Revert "scripts/setlocalversion: git: Make -dirty check more robust"
      ff64dd485730 scripts/setlocalversion: Improve -dirty check with git-status --no-optional-locks
      7a82e3fa28f1 scripts/setlocalversion: clear local variable to make it work for sh
      991b78fbd223 scripts: setlocalversion: fix a bashism
      3c96bdd0ebfa scripts: setlocalversion: replace backquote to dollar parenthesis
      and it's ff64dd485730 that is the motivation for this sync. It fixes
      false positive "-dirty" added to the version string when building with
      There has been one U-Boot specific patch since this was synced with
      linux 3.16: 81630a3b (scripts: setlocalversion: safely extract
      variables from auto.conf using awk).  Keep these changes applied.
      Signed-off-by: default avatarRasmus Villemoes <rasmus.villemoes@prevas.dk>
      [trini: Re-add 81630a3b and reword message]
      Signed-off-by: Tom Rini's avatarTom Rini <trini@konsulko.com>
    • Baruch Siach's avatar
      image: don't exceed gd->ram_top in bootm_size · 7f98b4ee
      Baruch Siach authored
      When board_get_usable_ram_top() limits gd->ram_top, env_get_bootm_size()
      must not exceed that limit. Otherwise, boot_relocate_fdt() might put fdt
      out of the allowed RAM range.
      The similar commit 8ce1f10c ("ARM: bootm: take into account
      gd->ram_top") exposed this bug.
      This fixes boot on Armada 8040 based Clearfog GT-8K where ram_top is set
      to 0x80000000 (2GB), but bi_dram[0].size might be up to 0xc0000000
      (3GB). Note the relocated fdt address (0xbfff4000) in the console output
      listed below:
      Found /extlinux/extlinux.conf
      Retrieving file: /extlinux/extlinux.conf
      62 bytes read in 21 ms (2 KiB/s)
      1:	linux
      Retrieving file: /extlinux/Image
      13740544 bytes read in 1266 ms (10.4 MiB/s)
      Retrieving file: /extlinux/armada-8040-clearfog-gt-8k.dtb
      33368 bytes read in 31 ms (1 MiB/s)
         Booting using the fdt blob at 0x4f00000
         Loading Device Tree to 00000000bfff4000, end 00000000bffff257 ... "Synchronous Abort" handler, esr 0x96000045
      elr: 000000000006e1cc lr : 0000000000068fd8 (reloc)
      elr: 000000007ffa91cc lr : 000000007ffa3fd8
      x0 : ffffffffffffffff x1 : 00000000bfffc258
      x2 : 0000000000000000 x3 : ffffffffffff7da7
      x4 : 0000000004f08258 x5 : 00000000bfff4000
      x6 : 00000000bfff4000 x7 : 000000000000000f
      x8 : 000000007fb23bf8 x9 : 0000000000000008
      x10: 00000000bffff257 x11: 00000000bffff257
      x12: 0000000000000000 x13: fffffffffffff000
      x14: 00000000bfff4000 x15: 0000000000000021
      x16: 000000007ff7bc38 x17: 0000000000000000
      x18: 000000007fb2add0 x19: 00000000bfff4000
      x20: 0000000004f00000 x21: 000000000000b258
      x22: 0000000058820000 x23: 0000000000000010
      x24: 000000007ffe3c40 x25: 000000007fb23cb8
      x26: 00000000c0000000 x27: 0000000000000000
      x28: 000000007fc3fd50 x29: 000000007fb23bd0
      Code: 54000061 aa0603e0 d65f03c0 38606882 (38206822)
      Resetting CPU ...
      Thanks to Patrice CHOTARD who directed me to the right way.
      Signed-off-by: default avatarBaruch Siach <baruch@tkos.co.il>
    • Michal Simek's avatar
      cmd: mem: Remove already removed CONFIG_SYS_MEMTEST_SCRATCH · 0b2b9b85
      Michal Simek authored
      The commit e519f03a ("cmd: mem: Remove CONFIG_SYS_MEMTEST_SCRATCH
      mapping") removed CONFIG_SYS_MEMTEST_SCRATCH but commit 09140113
      ("command: Remove the cmd_tbl_t typedef") has added it back. That's why
      symbol is still in the tree that's why remove it again.
      Fixes: 09140113 ("command: Remove the cmd_tbl_t typedef
      Signed-off-by: default avatarMichal Simek <michal.simek@xilinx.com>
      Reviewed-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
    • Heinrich Schuchardt's avatar
      lib/rsa: correct check after allocation in fdt_add_bignum() · de959309
      Heinrich Schuchardt authored
      After allocating to pointer ctx we should check that pointer and not
      another pointer already checked above.
      Signed-off-by: Heinrich Schuchardt's avatarHeinrich Schuchardt <xypron.glpk@gmx.de>
      Reviewed-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
    • Heinrich Schuchardt's avatar
      test: undefined reference to 'sscanf' · 4431a988
      Heinrich Schuchardt authored
      Compiling with CONFIG_UNIT_TEST=y leads to:
      test/lib/sscanf.c:50: undefined reference to `sscanf'
      Add missing build dependency.
      Fixes:e87dfb05 ("lib: sscanf: add sscanf implementation")
      Signed-off-by: Heinrich Schuchardt's avatarHeinrich Schuchardt <xypron.glpk@gmx.de>
    • Tom Rini's avatar
      checkpatch.pl: Make fdt / initrd relocation disabling an error · 12178b51
      Tom Rini authored
      Entirely disabling relocation of the device tree or initrd is almost
      never the right answer.  Doing this by default leads to hard to diagnose
      run-time failures.
      Signed-off-by: Tom Rini's avatarTom Rini <trini@konsulko.com>
    • Michal Simek's avatar
      env: Kconfig: Add missing dependency for ENV_IS_IN_EXT4 · 07661784
      Michal Simek authored
      ENV_IS_IN_EXT4 also need to enable FS_EXT4 which is not covered in Kconfig.
      Kconfig reports this as:
      WARNING: unmet direct dependencies detected for EXT4_WRITE
        Depends on [n]: FS_EXT4 [=n]
        Selected by [y]:
        - ENV_IS_IN_EXT4 [=y] && !CHAIN_OF_TRUST [=n]
      Signed-off-by: default avatarMichal Simek <michal.simek@xilinx.com>
      Reviewed-by: Tom Rini's avatarTom Rini <trini@konsulko.com>
    • Michal Simek's avatar
      arc: Kconfig: Add missing DM dependency · 7b56432c
      Michal Simek authored
      ARC is selecting TIMER which depends on DM but DM is not selected and
      doesn't need to be enabled. Fix it by selecting DM for ARC architecture.
      Kconfig is showing this missing dependency by:
      WARNING: unmet direct dependencies detected for TIMER
        Depends on [n]: DM [=n]
        Selected by [y]:
        - ARC [=y] && <choice>
      Signed-off-by: default avatarMichal Simek <michal.simek@xilinx.com>
      Reviewed-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
    • Michal Simek's avatar
      cmd: Kconfig: Change dependency for CMD_ADC · 6e741cfa
      Michal Simek authored
      CMD_ADC selected DM_REGULATOR unconditionally without enabling DM.
      That's why change select to depends on to cover it.
      Kconfig is showing this issue as:
      WARNING: unmet direct dependencies detected for REGMAP
        Depends on [n]: DM [=n]
        Selected by [y]:
        - DM_REGULATOR_PBIAS [=y] && DM_REGULATOR [=y]
      Signed-off-by: default avatarMichal Simek <michal.simek@xilinx.com>
      Reviewed-by: Tom Rini's avatarTom Rini <trini@konsulko.com>
      [trini: Update CMD_ADC=y configs to enable DM_REGULATOR now]
      Signed-off-by: Tom Rini's avatarTom Rini <trini@konsulko.com>
    • Michal Simek's avatar
      pci: kconfig: Setup proper dependency for PCIE_ROCKCHIP · a261fdce
      Michal Simek authored
      There is missing dependency for PCIE_ROCKCHIP which selects
      PHY_ROCKCHIP_PCIE which directly depends on ARCH_ROCKCHIP.
      WARNING: unmet direct dependencies detected for PHY_ROCKCHIP_PCIE
        Depends on [n]: ARCH_ROCKCHIP [=n]
        Selected by [y]:
        - PCIE_ROCKCHIP [=y] && PCI [=y]
      Signed-off-by: default avatarMichal Simek <michal.simek@xilinx.com>
      Reviewed-by: Tom Rini's avatarTom Rini <trini@konsulko.com>
    • Ruben Di Battista's avatar
      drivers: usb: Fix config indentation · 67e62c74
      Ruben Di Battista authored
      The indentation was messing up with the scripts/build-whitelist.sh that
      was marking SYS_USB_EVENT_POLL_VIA_INT_QUEUE (and probably also the
      other indented options) erroneously as ad-hoc configure option with the
      following error:
      Error: You must add new CONFIG options using Kconfig
      The following new ad-hoc CONFIG options were detected:
  4. 26 Aug, 2020 3 commits
  5. 25 Aug, 2020 5 commits