1. 25 Apr, 2019 33 commits
  2. 24 Apr, 2019 4 commits
    • Tom Rini's avatar
      Merge branch '2019-04-22-master-imports' · 3fbd2dce
      Tom Rini authored
      - Add and enable brcmnand driver on a number of relevant platforms.
        Also add and enable LED drivers on more bcm platforms.
      - Various ARMv8 fixes/improvements, including extending PSCI
      - fs_loader improvments
      - Various FIT/SPL improvements
      - PCI bugfixes
      - Poplar platform ethernet support
      - MediaTek MMC improvements
      - Android boot improvements
    • Eugeniu Rosca's avatar
      image: android: fix 'iminfo' typo · 74a7e001
      Eugeniu Rosca authored and Tom Rini's avatar Tom Rini committed
      Fix below CP warning triggered by the 'iminfo' output in another patch:
      WARNING: 'addrress' may be misspelled - perhaps 'address'?
      Fixes: 4f1318b2
       ("common: image: minimal android image iminfo support")
      Signed-off-by: default avatarEugeniu Rosca <erosca@de.adit-jv.com>
      Acked-by: default avatarMarek Vasut <marek.vasut@gmail.com>
    • Eugeniu Rosca's avatar
      image: android: allow booting lz4-compressed kernels · 829ceb28
      Eugeniu Rosca authored and Tom Rini's avatar Tom Rini committed
      According to Android image format [1], kernel image resides at 1 page
      offset from the boot image address. Grab the magic number from there
      and allow U-Boot to handle LZ4-compressed KNL binaries instead of
      hardcoding compression type to IH_COMP_NONE. Other compression types,
      if needed, can be added later.
      Tested on H3ULCB-KF using the image detailed in [2].
      [1] Excerpt from include/android_image.h
          | boot header     | 1 page
          | kernel          | n pages
          | ramdisk         | m pages
          | second stage    | o pages
      [2] => iminfo 4c000000
          ## Checking Image at 4c000000 ...
          Android image found
          kernel size:      85b9d1
          kernel address:   48080000
          ramdisk size:     54ddbc
          ramdisk addrress: 4a180000
          second size:      0
          second address:   48000800
          tags address:     48000100
          page size:        800
          os_version:       1200012a (ver: 0.9.0, level: 2018.10)
          cmdline:          buildvariant=userdebug
      Signed-off-by: default avatarEugeniu Rosca <erosca@de.adit-jv.com>
    • Heinrich Schuchardt's avatar
      test: env: Enable env unit tests by default · 0efe2b8f
      Heinrich Schuchardt authored and Tom Rini's avatar Tom Rini committed
      If CONFIG_UNIT_TEST is enabled we should enable the individual tests by
      default to ensure good test coverage.
      Reviewed-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
      Signed-off-by: Heinrich Schuchardt's avatarHeinrich Schuchardt <xypron.glpk@gmx.de>
  3. 23 Apr, 2019 3 commits
    • Lars Povlsen's avatar
      ARMv8: PSCI: Fix PSCI_TABLE relocation issue · 25c07c72
      Lars Povlsen authored and Tom Rini's avatar Tom Rini committed
      This fixes relaction isses with the PSCI_TABLE entries in
      the psci_32_table and psci_64_table.
      When using 32-bit adress pointers relocation was not being applied to
      the tables, causing PSCI handlers to point to the un-relocated code
      area. By using 64-bit data relocation is properly applied. The
      handlers are thus in the "secure data" area, which is protected by
      /memreserve/ in the FDT.
      Signed-off-by: default avatarLars Povlsen <lars.povlsen@microchip.com>
    • Trent Piepho's avatar
      bootm: Simplying cache flush code · b4353b37
      Trent Piepho authored and Tom Rini's avatar Tom Rini committed
      The cache flush of the kernel load area needs to be aligned outward to
      the DMA cache alignment.  The operations are simpler if we think of this
      as aligning the start down, ALIGN_DOWN(load, ARCH_DMA_MINALIGN), and
      aligning the end up, ALIGN(load_end, ARCH_DMA_MINALIGN), and then find
      the length of the flushed region by subtracting the former from the
      Cc: Tom Rini <trini@konsulko.com>
      Cc: Simon Glass <sjg@chromium.org>
      Cc: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
      Signed-off-by: default avatarTrent Piepho <tpiepho@impinj.com>
      Reviewed-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
    • Andreas Dannenberg's avatar
      malloc: Fix memalign not honoring alignment prior to full malloc init · 4c6be01c
      Andreas Dannenberg authored and Tom Rini's avatar Tom Rini committed
      When using memalign() in a scenario where U-Boot is configured for full
      malloc support with simple malloc not explicitly enabled and before the
      full malloc support is initialized, a memory block is being allocated
      and returned without the alignment parameter getting honored.
      Fix this issue by replacing the existing memalign pre-full malloc init
      logic with a call to memalign_simple() this way ensuring proper alignment
      of the returned memory block.
      Fixes: ee038c58
       ("malloc: Use malloc simple before malloc is fully initialized in memalign()")
      Signed-off-by: default avatarAndreas Dannenberg <dannenberg@ti.com>
      Reviewed-by: Lokesh Vutla's avatarLokesh Vutla <lokeshvutla@ti.com>