Skip to content
Snippets Groups Projects
  1. Jan 07, 2016
    • Przemyslaw Marczak's avatar
      fdt: fix address cell count checking in fdt_translate_address() · 71105f50
      Przemyslaw Marczak authored and Simon Glass's avatar Simon Glass committed
      
      Commit: dm: core: Enable optional use of fdt_translate_address()
      
      Enables use of this function as default, but after this it's not
      possible to get dev address for the case in which: '#size-cells == 0'
      
      This causes errors when getting address for some GPIOs, for which
      the '#size-cells' is set to 0.
      
      Example error:
      '__of_translate_address: Bad cell count for gpx0'
      
      Allowing for that case by modifying the macro 'OF_CHECK_COUNTS',
      (called from )__of_translate_address(), fixes the issue.
      
      Now, this macro doesn't check, that '#size-cells' is greater than 0.
      
      This is possible from the specification point of view, but I'm not sure
      that it doesn't introduce a regression for other configs.
      
      Please test and share the results.
      
      Tested-on: Odroid U3, Odroid X2, Odroid XU3, Sandbox.
      
      Signed-off-by: default avatarPrzemyslaw Marczak <p.marczak@samsung.com>
      Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
      Cc: Lukasz Majewski <l.majewski@samsung.com>
      Cc: Jaehoon Chung <jh80.chung@samsung.com>
      Cc: Stefan Roese <sr@denx.de>
      Cc: Simon Glass <sjg@chromium.org>
      Cc: Bin Meng <bmeng.cn@gmail.com>
      Cc: Marek Vasut <marex@denx.de>
      Tested-by: default avatarJaehoon Chung <jh80.chung@samsung.com>
      Tested-by: default avatarLukasz Majewski <l.majewski@samsung.com>
      71105f50
    • Simon Glass's avatar
      dm: usb: Add a remove() method for USB keyboards · 8a834870
      Simon Glass authored
      
      At present USB keyboards are not properly removed with driver model. Add the
      code to handle this.
      
      Signed-off-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
      Reviewed-by: default avatarMarek Vasut <marex@denx.de>
      8a834870
    • Simon Glass's avatar
      usb: Allow up to 7 storage devices · 70caa971
      Simon Glass authored
      
      The current limit of 5 is not enough for the driver model USB tests. Really
      we should not have a limit but the driver model code still uses the
      usb_dev_desc[] array, which has a limit.
      
      Increasing the limit by 2 should not bother anyone. Adjust it.
      
      Signed-off-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
      Reviewed-by: default avatarMarek Vasut <marex@denx.de>
      70caa971
  2. Jan 04, 2016
  3. Dec 31, 2015
  4. Dec 17, 2015
    • Stephen Warren's avatar
      usb: kbd: don't use int xfers when polling via ctrl xfers · e4b70d80
      Stephen Warren authored and Marek Vasut's avatar Marek Vasut committed
      
      When CONFIG_SYS_USB_EVENT_POLL_VIA_CONTROL_EP is enabled, use a
      GET_REPORT control transfer to retrieve the initial state of the
      keyboard. This matches the technique used to poll the keyboard state.
      This is useful since it eliminates the remaining use of interrupt
      transfers from the USB keyboard driver, which allows it to work with
      USB HCD that don't support interrupt transfers.
      
      Cc: Hans de Goede <hdegoede@redhat.com>
      Signed-off-by: Stephen Warren's avatarStephen Warren <swarren@nvidia.com>
      e4b70d80
  5. Dec 16, 2015
    • Alexey Brodkin's avatar
      eeprom: fix eeprom write procedure · 52bc7c7e
      Alexey Brodkin authored and Tom Rini's avatar Tom Rini committed
      
      This fixes commit 1a37889b:
      ----------------------->8--------------------
      eeprom: Pull out the RW loop
      
      Unify the code for doing read/write into single function, since the
      code for both the read and write is almost identical. This again
      trims down the code duplication.
      ----------------------->8--------------------
      
      where the same one routine is utilized for both EEPROM writing and
      reading. The only difference was supposed to be a "read" flag which
      in both cases was set with 1 somehow.
      
      That lead to a missing delay in case of writing which lead to write
      failure (in my case no data was written).
      
      Signed-off-by: default avatarAlexey Brodkin <abrodkin@synopsys.com>
      Acked-by: default avatarMarek Vasut <marex@denx.de>
      Cc: Simon Glass <sjg@chromium.org>
      Cc: Tom Rini <trini@konsulko.com>
      Cc: Heiko Schocher <hs@denx.de>
      52bc7c7e
  6. Dec 15, 2015
    • Aneesh Bansal's avatar
      armv8/ls1043ardb: add SECURE BOOT target for NOR · 9711f528
      Aneesh Bansal authored
      
      LS1043ARDB Secure Boot Target from NOR has been added.
      - Configs defined to enable esbc_validate.
      - ESBC Address in header is made 64 bit.
      - SMMU is re-configured in Bypass mode.
      
      Signed-off-by: default avatarAneesh Bansal <aneesh.bansal@freescale.com>
      Reviewed-by: default avatarYork Sun <yorksun@freescale.com>
      9711f528
    • York Sun's avatar
      common: Rewrite hiding the end of memory · aabd7ddb
      York Sun authored
      
      As the name may be confusing, the CONFIG_SYS_MEM_TOP_HIDE reserves
      some memory from the end of ram, tracked by gd->ram_size. It is not
      always the top of u-boot visible memory. Rewrite the macro with a
      weak function to provide flexibility for complex calcuation. Legacy
      use of this macro is still supported.
      
      Signed-off-by: default avatarYork Sun <yorksun@freescale.com>
      Reviewed-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
      aabd7ddb
    • York Sun's avatar
      Reserve secure memory · e8149522
      York Sun authored
      
      Secure memory is at the end of memory, separated and reserved
      from OS, tracked by gd->secure_ram. Secure memory can host
      MMU tables, security monitor, etc. This is different from PRAM
      used to reserve private memory. PRAM offers memory at the top
      of u-boot memory, not necessarily the real end of memory for
      systems with very large DDR. Using the end of memory simplifies
      MMU setup and avoid memory fragmentation.
      
      "bdinfo" command shows gd->secure_ram value if this memory is
      marked as secured.
      
      Signed-off-by: default avatarYork Sun <yorksun@freescale.com>
      e8149522
  7. Dec 14, 2015
  8. Dec 12, 2015
  9. Dec 09, 2015
  10. Dec 07, 2015
  11. Dec 05, 2015
  12. Dec 03, 2015
  13. Dec 02, 2015
  14. Dec 01, 2015
Loading