1. 08 Feb, 2017 1 commit
    • Simon Glass's avatar
      dm: core: Replace of_offset with accessor · e160f7d4
      Simon Glass authored
      At present devices use a simple integer offset to record the device tree
      node associated with the device. In preparation for supporting a live
      device tree, which uses a node pointer instead, refactor existing code to
      access this field through an inline function.
      Signed-off-by: 's avatarSimon Glass <sjg@chromium.org>
  2. 05 Dec, 2016 1 commit
  3. 04 Dec, 2016 2 commits
  4. 15 Jul, 2016 2 commits
  5. 27 May, 2016 1 commit
  6. 14 Apr, 2016 1 commit
  7. 24 Feb, 2016 1 commit
  8. 08 Feb, 2016 1 commit
  9. 27 Jan, 2016 1 commit
  10. 21 Jan, 2016 1 commit
  11. 19 Dec, 2015 1 commit
  12. 12 Dec, 2015 1 commit
  13. 20 Nov, 2015 1 commit
  14. 23 Oct, 2015 1 commit
  15. 22 Oct, 2015 1 commit
    • Nishanth Menon's avatar
      drivers: Introduce a simplified remoteproc framework · ddf56bc7
      Nishanth Menon authored
      Many System on Chip(SoC) solutions are complex with multiple processors
      on the same die dedicated to either general purpose of specialized
      functions. Many examples do exist in today's SoCs from various vendors.
      Typical examples are micro controllers such as an ARM M3/M0 doing a
      offload of specific function such as event integration or power
      management or controlling camera etc.
      Traditionally, the responsibility of loading up such a processor with a
      firmware and communication has been with a High Level Operating
      System(HLOS) such as Linux. However, there exists classes of products
      where Linux would need to expect services from such a processor or the
      delay of Linux and operating system being able to load up such a
      firmware is unacceptable.
      To address these needs, we need some minimal capability to load such a
      system and ensure it is started prior to an Operating System(Linux or
      any other) is started up.
      NOTE: This is NOT meant to be a solve-all solution, instead, it tries to
      address certain class of SoCs and products that need such a solution.
      A very simple model is introduced here as part of the initial support
      that supports microcontrollers with internal memory (no MMU, no
      execution from external memory, or specific image format needs). This
      basic framework can then (hopefully) be extensible to other complex SoC
      processor support as need be.
      Reviewed-by: 's avatarSimon Glass <sjg@chromium.org>
      Signed-off-by: 's avatarNishanth Menon <nm@ti.com>
      Acked-by: 's avatarSimon Glass <sjg@chromium.org>
  16. 26 Aug, 2015 1 commit
  17. 05 Aug, 2015 1 commit
  18. 21 Jul, 2015 1 commit
  19. 15 May, 2015 2 commits
  20. 22 Apr, 2015 1 commit
  21. 18 Apr, 2015 1 commit
  22. 17 Apr, 2015 1 commit
    • Simon Glass's avatar
      dm: pci: Add a uclass for PCI · ff3e077b
      Simon Glass authored
      Add a uclass for PCI controllers and a generic one for PCI devices. Adjust
      the 'pci' command and the existing PCI support to work with this new uclass.
      Keep most of the compatibility code in a separate file so that it can be
      removed one day.
      TODO: Add more header file comments to the new parts of pci.h
      Signed-off-by: 's avatarSimon Glass <sjg@chromium.org>
  23. 12 Feb, 2015 1 commit
  24. 30 Jan, 2015 3 commits
  25. 06 Jan, 2015 1 commit
  26. 21 Nov, 2014 1 commit
  27. 24 Oct, 2014 3 commits
  28. 22 Oct, 2014 3 commits
  29. 23 Jul, 2014 3 commits
    • Simon Glass's avatar
      dm: Add child_pre_probe() and child_post_remove() methods · a327dee0
      Simon Glass authored
      Some devices (particularly bus devices) must track their children, knowing
      when a new child is added so that it can be set up for communication on the
      Add a child_pre_probe() method to provide this feature, and a corresponding
      child_post_remove() method.
      Signed-off-by: 's avatarSimon Glass <sjg@chromium.org>
    • Simon Glass's avatar
      dm: Introduce per-child data for devices · e59f458d
      Simon Glass authored
      Some device types can have child devices and want to store information
      about them. For example a USB flash stick attached to a USB host
      controller would likely use this space. The controller can hold
      information about the USB state of each of its children.
      The data is stored attached to the child device in the 'parent_priv'
      member. It can be auto-allocated by dm when the child is probed. To
      do this, add a per_child_auto_alloc_size value to the parent driver.
      Signed-off-by: 's avatarSimon Glass <sjg@chromium.org>
    • Simon Glass's avatar
      dm: Add functions to access a device's children · 997c87bb
      Simon Glass authored
      Devices can have childen that can be addressed by a simple index, the
      sequence number or a device tree offset. Add functions to access a child
      in each of these ways.
      The index is typically used as a fallback when the sequence number is not
      available. For example we may use a serial UART with sequence number 0 as
      the console, but if no UART has sequence number 0, then we can fall back
      to just using the first UART (index 0).
      The device tree offset function is useful for buses, where they want to
      locate one of their children. The device tree can be scanned to find the
      offset of each child, and that offset can then find the device.
      Signed-off-by: 's avatarSimon Glass <sjg@chromium.org>