1. 01 11月, 2017 1 次提交
  2. 04 4月, 2017 1 次提交
  3. 20 3月, 2017 4 次提交
  4. 17 6月, 2016 1 次提交
    • T
      clk: tegra: Squash sor1 safe/brick/src into a single mux · c1273af4
      Thierry Reding 提交于
      The sor1 clock on Tegra210 is structured in the following way:
      
          +-------+
          | pllp  |---+
          +-------+   |    +--------------+       +-----------+
                      +----|              |       | sor_safe  |
          +-------+        |              |       +-----------+
          | plld  |--------|              |             |
          +-------+        |              |       +-----------+
                           |   sor1_src   |-------|           |
          +-------+        |              |       +-----------+
          | plld2 |--------|              |             |
          +-------+        |              |             |
                      +----|              |             |
          +-------+   |    +--------------+             |
          | clkm  |---+                           +-----------+
          +-------+        +--------------+       |           |
                           |  sor1_brick  |-------|   sor1    |
                           +--------------+       |           |
                                                  +-----------+
      
      This is impractical to represent in a clock tree, though, because there
      is no name for the mux that has sor_safe and sor1_src as parents. It is
      also much more cumbersome to deal with the additional mux because users
      of these clocks (the display driver) would have to juggle with an extra
      mux for no real reason.
      
      To simply things, the above is squashed into two muxes instead, so that
      it looks like this:
      
          +-------+
          | pllp  |---+
          +-------+   |    +--------------+       +-----------+
                      +----|              |       | sor_safe  |
          +-------+        |              |       +-----------+
          | plld  |--------|              |             |
          +-------+        |              |       +-----------+
                           |   sor1_src   |-------|   sor1    |
          +-------+        |              |       +-----------+
          | plld2 |--------|              |           |   |
          +-------+        |              |           |   |
                      +----|              |           |   |
          +-------+   |    +--------------+           |   |
          | clkm  |---+                               |   |
          +-------+        +--------------+           |   |
                           |  sor1_brick  |-----------+---+
                           +--------------+
      
      This still very accurately represents the hardware. Note that sor1 has
      sor1_brick as input twice, that's because bit 1 in the mux selects the
      sor1_brick irrespective of bit 0.
      Signed-off-by: NThierry Reding <treding@nvidia.com>
      c1273af4
  5. 28 4月, 2016 2 次提交
  6. 02 2月, 2016 1 次提交
  7. 17 12月, 2015 1 次提交
  8. 21 11月, 2015 1 次提交
    • R
      clk: tegra: periph: Add new periph clks and muxes for Tegra210 · dc37fec4
      Rhyland Klein 提交于
      Tegra210 has significant differences in muxes for peripheral clocks.
      One of the most important changes is that pll_m isn't to be used
      as a source for peripherals. Therefore, we need to define the new
      muxes and new clocks to use those muxes for Tegra210 support.
      
      Tegra210 has some differences in the PLLP clock tree:
      - Four new output clocks: PLLP_OUT_CPU, PLLP_OUT_ADSP, PLLP_OUT_HSIO,
        and PLLP_OUT_XUSB.
      - PLLP_OUT2 is fixed at 1/2 the rate of PLLP_VCO.
      - PLLP_OUT4 is the child of PLLP_OUT_CPU.
      
      Update the xusb_hs_src mux and add the xusb_ssp_src mux for Tegra210.
      
      Including work by Andrew Bresticker <abrestic@chromium.org> and
      Bill Huang <bilhuang@nvidia.com>.
      Signed-off-by: NRhyland Klein <rklein@nvidia.com>
      Signed-off-by: NThierry Reding <treding@nvidia.com>
      dc37fec4
  9. 02 2月, 2015 1 次提交
  10. 23 5月, 2014 1 次提交
  11. 17 2月, 2014 1 次提交
  12. 27 11月, 2013 2 次提交