1. 31 May, 2021 1 commit
    • Tom Rini's avatar
      Merge https://source.denx.de/u-boot/custodians/u-boot-sunxi · fa68645b
      Tom Rini authored
      This contains the fix to bring back the SD card as MMC0. In the long run
      we are looking into a more robust solution, but for now we need to fix
      this, as this breaks the user experience left, right, and centre.
      Also add the one MAINTAINERS path addition from Samuel.
  2. 30 May, 2021 2 commits
  3. 28 May, 2021 13 commits
  4. 27 May, 2021 8 commits
  5. 26 May, 2021 9 commits
    • Sean Anderson's avatar
      test: Remove duplicate macro · cb6c9c83
      Sean Anderson authored and Tom Rini's avatar Tom Rini committed
      ut_asserteq_strn is defined twice. Remove one definition.
      Fixes: 33d7edfd
       ("test: Add a way to check part of a console line or skip it")
      Signed-off-by: Sean Anderson's avatarSean Anderson <seanga2@gmail.com>
      Reviewed-by: Heinrich Schuchardt's avatarHeinrich Schuchardt <xypron.glpk@gmx.de>
    • Harm Berntsen's avatar
      GitLab: Remove tags for sandbox_noinst tests · b725ed50
      Harm Berntsen authored and Tom Rini's avatar Tom Rini committed
      Commit 712cc962 ("GitLab: Remove "tags" stanzas") removed the 'all'
      tag from all the jobs. The sandbox_noinst_test.py test was added in
      between the author date and commit date (commit 6c914e42
      ("azure/gitlab: Add tests for sandbox_noinst")) which is probably why it
      still contains the tags. This commit fixes that so all jobs now don't
      require tags on the GitLab runners.
      Signed-off-by: default avatarHarm Berntsen <harm.berntsen@nedap.com>
      CC: Simon Glass <sjg@chromium.org>
      Acked-by: default avatarPratyush Yadav <p.yadav@ti.com>
    • Alper Nebi Yasak's avatar
      test: Fix filesystem tests always being skipped · 77bfaad0
      Alper Nebi Yasak authored and Tom Rini's avatar Tom Rini committed
      Commit 1ba21bb0 ("test: Don't unmount not (yet) mounted system")
      fixes an issue in the filesystem tests where the test setup may fail
      to mount an image and still attempt to unmount it. However, the commit
      unintentionally breaks the test setups in two ways.
      The newly created unmounted filesystem images are being immediately
      deleted due to some cleanup steps being misplaced into finally blocks,
      which makes them always run instead of only on failures. The mount calls
      always fail since the images never exist, causing the tests to be always
      skipped. This patch moves these cleanup calls into the except blocks to
      fix this and makes the tests run again.
      There are also unmount calls misplaced into finally blocks, making them
      run after the tests instead of before the tests. These unmount calls
      make the filesystem image file consistent with the changes made to it as
      part of the test setup, and this misplacement is making a number of
      tests fail unexpectedly.
      The unmount calls must be run before the tests use the image, meaning
      before the yield call and not in the finally block. They must also be
      run as a cleanup step when the filesystem setup fails, so they can't be
      placed as the final call in the try blocks since they would be skipped
      on such failures. For these reasons, this patch places the unmount calls
      both in the except blocks and the else blocks of the final setup step.
      This makes the unexpectedly failing tests to succeed again.
      Furthermore, this isolates the mount calls to their own try-except
      statement to avoid reintroducing the original issue of unmounting a
      not-mounted image while fixing the unmount misplacement.
      After these fixes, running "make tests" with guestmount available results
      in two test failures not related to the mentioned commit. If the
      guestmount executables are unavailable, the mounts fallback to using
      sudo and result in no failures.
      Fixes: 1ba21bb0
       ("test: Don't unmount not (yet) mounted system")
      Signed-off-by: default avatarAlper Nebi Yasak <alpernebiyasak@gmail.com>
      Acked-by: default avatarAndy Shevchenko <andriy.shevchenko@linux.intel.com>
    • Michal Simek's avatar
      spl: Kconfig: Use tabs instead of space for alignment · ce869b55
      Michal Simek authored and Tom Rini's avatar Tom Rini committed
      A lot of entries were using spaces instead of tab for alignment that's why
      it is good to fix it to use the same style everywhere.
      Signed-off-by: default avatarMichal Simek <michal.simek@xilinx.com>
      Reviewed-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
    • Marek Vasut's avatar
      fs: btrfs: Add missing cache aligned allocation · 9e8bb078
      Marek Vasut authored and Tom Rini's avatar Tom Rini committed
      The superblock buffer must be cache aligned, since it might be used
      in DMA context, allocate it using ALLOC_CACHE_ALIGN_BUFFER() just
      like it was done in btrfs_read_superblock() and read_tree_node().
      This fixes this output on boot and non-working btrfs on iMX53:
      CACHE: Misaligned operation at range [ced299d0, ced2a9d0]
      Signed-off-by: Marek Vasut's avatarMarek Vasut <marex@denx.de>
      Cc: Marek Behún <marek.behun@nic.cz>
      Cc: Qu Wenruo <wqu@suse.com>
      Reviewed-by: default avatarMarek Behún <marek.behun@nic.cz>
    • Heinrich Schuchardt's avatar
      fs/squashfs: zero out unused fields in fs_dirent · 53ba2c21
      Heinrich Schuchardt authored and Tom Rini's avatar Tom Rini committed
      When reading directories the UEFI sub-system must supply file attributes
      and timestamps. These fields will have to be added to struct fs_dirent.
      SquashFS should not fill these fields with random data. Ensure that they
      are zeroed out.
      Signed-off-by: Heinrich Schuchardt's avatarHeinrich Schuchardt <xypron.glpk@gmx.de>
      Reviewed-by: default avatarMiquel Raynal <miquel.raynal@bootlin.com>
    • Matt Merhar's avatar
      powerpc: fix regression in arch_initr_trap() · f6c0d365
      Matt Merhar authored and Tom Rini's avatar Tom Rini committed
      The assembly output of the arch_initr_trap() function differed by a
      single byte after common.h was removed from traps.c:
       fff49a18 <arch_initr_trap>:
       fff49a18:      94 21 ff f0     stwu    r1,-16(r1)
       fff49a1c:      7c 08 02 a6     mflr    r0
       fff49a20:      90 01 00 14     stw     r0,20(r1)
      -fff49a24:      80 62 00 44     lwz     r3,68(r2)
      +fff49a24:      80 62 00 38     lwz     r3,56(r2)
       fff49a28:      4b ff 76 19     bl      fff41040 <trap_init>
       fff49a2c:      80 01 00 14     lwz     r0,20(r1)
       fff49a30:      38 60 00 00     li      r3,0
       fff49a34:      38 21 00 10     addi    r1,r1,16
       fff49a38:      7c 08 03 a6     mtlr    r0
      This was causing a consistent hard lockup during the MMC read / loading
      of the QoriQ FMan firmware on a P2041RDB board.
      Re-adding the header causes identical assembly to be emitted and allows
      the firmware loading and subsequent boot to succeed.
      Fixes: 401d1c4f
       ("common: Drop asm/global_data.h from common header")
      Signed-off-by: default avatarMatt Merhar <mattmerhar@protonmail.com>
    • Sean Anderson's avatar
      part: Add check for NULL dev_part_str · 26de4296
      Sean Anderson authored and Tom Rini's avatar Tom Rini committed
      Some callers (e.g. cmd/fs.c) of fs_set_blk_dev may use a NULL dev_part_str.
      While blk_get_device_part_str handles this fine,
      part_get_info_by_dev_and_name does not. This fixes commands crashing when
      implicitly using bootdevice.
      The unit test has also been updated to set bootdevice to a known value and
      to restore it after we are done.
      Fixes: 7194527b
       ("cmd: fs: Use part_get_info_by_dev_and_name_or_num to parse partitions")
      Reported-by: Heinrich Schuchardt's avatarHeinrich Schuchardt <xypron.glpk@gmx.de>
      Signed-off-by: Sean Anderson's avatarSean Anderson <seanga2@gmail.com>
      Reviewed-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
    • Vignesh Raghavendra's avatar
      pinctrl: single: Fix probe failure getting register area size · 1e787904
      Vignesh Raghavendra authored and Tom Rini's avatar Tom Rini committed
      If reg property of pinctrl-single node requires address translation then
      probe fails with following message:
      single-pinctrl pinctrl@4301c000: failed to get base register size
      This is because driver uses dev_read_addr_size() to get size which also
      tries to fetch untranslated addr and fails.
      Fix this by using dev_read_addr_size_index() which takes care of address
      translation and also makes following dev_read_addr() call redundant.
      This fixes Ethernet failures on TI's AM654 based EVMs due to lack of
      pinmux configuration.
      Fixes: 9fd8a430
       ("pinctrl: single: get register area size by device API")
      Signed-off-by: default avatarVignesh Raghavendra <vigneshr@ti.com>
  6. 25 May, 2021 7 commits