1. 15 Oct, 2015 1 commit
  2. 14 Oct, 2015 2 commits
  3. 12 Oct, 2015 3 commits
    • Julia Lawall's avatar
      clk: tegra: delete unneeded of_node_put · 4e4f485c
      Julia Lawall authored
      for_each_child_of_node performs an of_node_put on each iteration, so
      putting an of_node_put before a continue results in a double put.
      
      The semantic match that finds this problem is as follows
      (http://coccinelle.lip6.fr):
      
      // <smpl>
      @@
      expression root,e;
      local idexpression child;
      iterator name for_each_child_of_node;
      @@
      
       for_each_child_of_node(root, child) {
         ... when != of_node_get(child)
      *  of_node_put(child);
         ...
      *  continue;
      }
      // </smpl>
      Signed-off-by: default avatarJulia Lawall <Julia.Lawall@lip6.fr>
      Signed-off-by: default avatarStephen Boyd <sboyd@codeaurora.org>
      4e4f485c
    • Stephen Boyd's avatar
      Merge branch 'clk-bcm2835' into clk-next · 67d7188a
      Stephen Boyd authored
      * clk-bcm2835:
        clk: bcm2835: Add support for programming the audio domain clocks
        clk: bcm2835: Add binding docs for the new platform clock driver.
        clk: bcm2835: Move under bcm/ with other Broadcom SoC clk drivers.
      67d7188a
    • Eric Anholt's avatar
      clk: bcm2835: Add support for programming the audio domain clocks · 41691b88
      Eric Anholt authored
      This adds support for enabling, disabling, and setting the rate of the
      audio domain clocks.  It will be necessary for setting the pixel clock
      for HDMI in the VC4 driver and let us write a cpufreq driver.  It will
      also improve compatibility with user changes to the firmware's
      config.txt, since our previous fixed clocks are unaware of it.
      
      The firmware also has support for configuring the clocks through the
      mailbox channel, but the pixel clock setup by the firmware doesn't
      work, and it's Raspberry Pi specific anyway.  The only conflicts we
      should have with the firmware would be if we made firmware calls that
      result in clock management (like opening firmware V3D or ISP access,
      which we don't support in upstream), or on hardware over-thermal or
      under-voltage (when the firmware would rewrite PLLB to take the ARM
      out of overclock).  If that happens, our cached .recalc_rate() results
      would be incorrect, but that's no worse than our current state where
      we used fixed clocks.
      
      The existing fixed clocks in the code are left in place to provide
      backwards compatibility with old device tree files.
      Signed-off-by: default avatarEric Anholt <eric@anholt.net>
      Tested-by: default avatarMartin Sperl <kernel@martin.sperl.org>
      Acked-by: default avatarStephen Warren <swarren@wwwdotorg.org>
      Signed-off-by: default avatarStephen Boyd <sboyd@codeaurora.org>
      41691b88
  4. 09 Oct, 2015 10 commits
  5. 02 Oct, 2015 15 commits
  6. 01 Oct, 2015 9 commits