1. 01 10月, 2018 1 次提交
  2. 18 9月, 2018 1 次提交
  3. 11 9月, 2018 1 次提交
    • A
      clk: Introduce TI System Control Interface (TI SCI) clock driver · e585bef1
      Andreas Dannenberg 提交于
      Some TI Keystone 2 and K3 family of SoCs contain a system controller
      (like the Power Management Micro Controller (PMMC) on 66AK2G SoCs and
      the Device Management and Security Controller on AM65x SoCs) that manage
      the low-level device control (like clocks, resets etc) for the various
      hardware modules present on the SoC. These device control operations are
      provided to the host processor OS through a communication protocol
      called the TI System Control Interface (TI SCI) protocol.
      
      This patch adds a clock driver that communicates to the system
      controller over the TI SCI protocol for performing clock management of
      various devices present on the SoC. Various clock functionality is
      achieved by the means of different TI SCI device operations provided by
      the TI SCI framework.
      
      This code is loosely based on the drivers/clk/keystone/sci-clk.c driver
      of the Linux kernel.
      Reviewed-by: NTom Rini <trini@konsulko.com>
      Signed-off-by: NAndreas Dannenberg <dannenberg@ti.com>
      Signed-off-by: NVignesh R <vigneshr@ti.com>
      Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com>
      e585bef1
  4. 10 8月, 2018 1 次提交
  5. 10 7月, 2018 1 次提交
  6. 14 5月, 2018 1 次提交
    • M
      driver: clk: Add support for clocks on Armada 37xx · 82a248df
      Marek Behún 提交于
      The drivers are based on Linux driver by Gregory Clement.
      
      The TBG clocks support only the .get_rate method.
        - since setting rate is not supported, the driver computes the rates
          when probing and so subsequent calls to the .get_rate method do not
          read the corresponding registers again
      
      The peripheral clocks support methods .get_rate, .enable and .disable.
      
        - the .set_parent method theoretically could be supported on some clocks
          (the parent would have to be one of the TBG clocks)
      
        - the .set_rate method would have to try all the divider values to find
          the best approximation of a given rate, and it doesn't seem like
          this should be needed in U-Boot, therefore not implemented
      Signed-off-by: NMarek Behun <marek.behun@nic.cz>
      Reviewed-by: NStefan Roese <sr@denx.de>
      Signed-off-by: NStefan Roese <sr@denx.de>
      82a248df
  7. 09 5月, 2018 1 次提交
  8. 20 3月, 2018 1 次提交
  9. 11 12月, 2017 1 次提交
  10. 30 11月, 2017 1 次提交
  11. 15 9月, 2017 1 次提交
  12. 13 8月, 2017 2 次提交
  13. 03 8月, 2017 1 次提交
  14. 10 5月, 2017 1 次提交
  15. 17 2月, 2017 1 次提交
  16. 10 1月, 2017 1 次提交
  17. 21 9月, 2016 1 次提交
  18. 16 8月, 2016 2 次提交
  19. 25 5月, 2016 1 次提交
  20. 14 2月, 2016 1 次提交
  21. 21 1月, 2016 1 次提交
  22. 19 8月, 2015 1 次提交
  23. 22 7月, 2015 1 次提交
    • S
      dm: Add a clock uclass · f26c8a8e
      Simon Glass 提交于
      Clocks are an important feature of platforms and have become increasing
      complex with time. Most modern SoCs have multiple PLLs and dozens of clock
      dividers which distribute clocks to on-chip peripherals.
      
      Some SoC implementations have a clock API which is private to that SoC family,
      e.g. Tegra and Exynos. This is useful but it would be better to have a
      common API that can be understood and used throughout U-Boot.
      
      Add a simple clock API as a starting point. It supports querying and setting
      the rate of a clock. Each clock is a device. To reduce memory and processing
      overhead the concept of peripheral clocks is provided. These do not need to
      be explicit devices - it is possible to write a driver that can adjust the
      I2C clock (for example) without an explicit I2C clock device. This can
      dramatically reduce the number of devices (and associated overhead) in a
      complex SoC.
      
      Clocks are referenced by a number, and it is expected that SoCs will define
      that numbering themselves via an enum.
      Signed-off-by: NSimon Glass <sjg@chromium.org>
      f26c8a8e