Skip to content
Snippets Groups Projects
  1. May 27, 2016
    • Simon Glass's avatar
      dm: rockchip: Enable CONFIG_BLK · 3c27b6ad
      Simon Glass authored
      
      Enable CONFIG_BLK to move to using driver model for block devices. This
      affects MMC booting in SPL, as well as MMC access in U-Boot proper.
      
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      3c27b6ad
    • Stephen Warren's avatar
      Rename reset to sysreset · 11636258
      Stephen Warren authored
      
      The current reset API implements a method to reset the entire system.
      In the near future, I'd like to introduce code that implements the device
      tree reset bindings; i.e. the equivalent of the Linux kernel's reset API.
      This controls resets to individual HW blocks or external chips with reset
      signals. It doesn't make sense to merge the two APIs into one since they
      have different semantic purposes. Resolve the naming conflict by renaming
      the existing reset API to sysreset instead, so the new reset API can be
      called just reset.
      
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      Acked-by: default avatarSimon Glass <sjg@chromium.org>
      11636258
  2. May 02, 2016
  3. Mar 14, 2016
  4. Mar 10, 2016
  5. Jan 22, 2016
  6. Jan 12, 2016
  7. Dec 14, 2015
  8. Dec 01, 2015
  9. Nov 22, 2015
  10. Oct 03, 2015
    • Sjoerd Simons's avatar
      rockchip: Reconfigure the malloc based to point to system memory · b1f492ca
      Sjoerd Simons authored
      
      When malloc_base initially gets setup in the SPL it is based on the
      current (early) stack pointer, which for rockchip is pointing into SRAM.
      This means simple memory allocations happen in SRAM space, which is
      somewhat unfortunate. Specifically a bounce buffer for the mmc allocated
      in SRAM space seems to cause the mmc engine to stall/fail causing
      timeouts and a failure to load the main u-boot image.
      
      To resolve this, reconfigure the malloc_base to start at the relocated
      stack pointer after DRAM  has been setup.
      
      For reference, things did work fine on rockchip before 596380db was
      merged to fix memalign_simple due to a combination of rockchip SDRAM
      starting at address 0 and the dw_mmc driver not checking errors from
      bounce_buffer_start. As a result, when a bounce buffer needed to be
      allocated mem_align simple would fail and return NULL. The mmc driver
      ignored the error and happily continued with the bounce buffer address
      being set to 0, which just happened to work fine..
      
      Signed-off-by: default avatarSjoerd Simons <sjoerd.simons@collabora.co.uk>
      Reviewed-by: default avatarHans de Goede <hdegoede@redhat.com>
      Acked-by: default avatarSimon Glass <sjg@chromium.org>
      b1f492ca
  11. Sep 03, 2015
Loading