1. 25 Apr, 2018 1 commit
  2. 13 Mar, 2018 1 commit
  3. 09 Jan, 2018 1 commit
  4. 21 Nov, 2017 1 commit
  5. 13 Aug, 2017 2 commits
  6. 23 Jun, 2017 1 commit
  7. 07 Jun, 2017 2 commits
  8. 01 Jun, 2017 1 commit
    • Simon Glass's avatar
      dm: Rename dev_addr..() functions · a821c4af
      Simon Glass authored
      
      
      These support the flat device tree. We want to use the dev_read_..()
      prefix for functions that support both flat tree and live tree. So rename
      the existing functions to avoid confusion.
      
      In the end we will have:
      
         1. dev_read_addr...()    - works on devices, supports flat/live tree
         2. devfdt_get_addr...()  - current functions, flat tree only
         3. of_get_address() etc. - new functions, live tree only
      
      All drivers will be written to use 1. That function will in turn call
      either 2 or 3 depending on whether the flat or live tree is in use.
      
      Note this involves changing some dead code - the imx_lpi2c.c file.
      Signed-off-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
      a821c4af
  9. 10 May, 2017 1 commit
  10. 30 Oct, 2016 1 commit
  11. 06 Aug, 2016 1 commit
  12. 05 Aug, 2016 1 commit
  13. 19 Jun, 2016 1 commit
    • Stephen Warren's avatar
      clk: convert API to match reset/mailbox style · 135aa950
      Stephen Warren authored and Simon Glass's avatar Simon Glass committed
      
      
      The following changes are made to the clock API:
      * The concept of "clocks" and "peripheral clocks" are unified; each clock
        provider now implements a single set of clocks. This provides a simpler
        conceptual interface to clients, and better aligns with device tree
        clock bindings.
      * Clocks are now identified with a single "struct clk", rather than
        requiring clients to store the clock provider device and clock identity
        values separately. For simple clock consumers, this isolates clients
        from internal details of the clock API.
      * clk.h is split so it only contains the client/consumer API, whereas
        clk-uclass.h contains the provider API. This aligns with the recently
        added reset and mailbox APIs.
      * clk_ops .of_xlate(), .request(), and .free() are added so providers
        can customize these operations if needed. This also aligns with the
        recently added reset and mailbox APIs.
      * clk_disable() is added.
      * All users of the current clock APIs are updated.
      * Sandbox clock tests are updated to exercise clock lookup via DT, and
        clock enable/disable.
      * rkclk_get_clk() is removed and replaced with standard APIs.
      
      Buildman shows no clock-related errors for any board for which buildman
      can download a toolchain.
      
      test/py passes for sandbox (which invokes the dm clk test amongst
      others).
      Signed-off-by: Stephen Warren's avatarStephen Warren <swarren@nvidia.com>
      Acked-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
      135aa950
  14. 27 May, 2016 1 commit
    • Stephen Warren's avatar
      Rename reset to sysreset · 11636258
      Stephen Warren authored and Simon Glass's avatar Simon Glass committed
      
      
      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: Stephen Warren's avatarStephen Warren <swarren@nvidia.com>
      Acked-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
      11636258
  15. 22 Jan, 2016 2 commits
    • Simon Glass's avatar
      rockchip: clk: Make rkclk_get_clk() SoC-specific · 5ddf5d77
      Simon Glass authored
      
      
      The current method assumes that clocks are numbered from 0 and we can
      determine a clock by its number. It is safer to use an ID in the clock's
      platform data to avoid the situation where another clock is bound before
      the one we expect.
      
      Move the existing code into rk3036 since it still works there. Add a new
      implementation for rk3288.
      Signed-off-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
      5ddf5d77
    • Simon Glass's avatar
      rockchip: Use a separate clock ID for clocks · 898d6439
      Simon Glass authored
      
      
      At present we use the same peripheral ID for clocks and pinctrl. While this
      works it is probably better to use the device tree clock binding ID for
      clocks. We can use the clk_get_by_index() function to find this.
      
      Update the clock drivers and the code that uses them.
      Signed-off-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
      898d6439
  16. 21 Jan, 2016 1 commit
  17. 01 Dec, 2015 1 commit