1. 08 10月, 2013 3 次提交
  2. 07 10月, 2013 1 次提交
    • S
      clk: armada-370: fix tclk frequencies · 1022c75f
      Simon Guinot 提交于
      This patch fixes the tclk frequency array for the Armada-370 SoC.
      This bug has been introduced by commit 6b72333d
      ("clk: mvebu: add Armada 370 SoC-centric clock init").
      
      A wrong tclk frequency affects the following drivers: mvsdio, mvneta,
      i2c-mv64xxx and mvebu-devbus. This list may be incomplete.
      
      About the mvneta Ethernet driver, note that the tclk frequency is used
      to compute the Rx time coalescence. Then, this bug harms the coalescence
      configuration and also degrades the networking performances with the
      default values.
      Signed-off-by: NSimon Guinot <simon.guinot@sequanux.org>
      Cc: Andrew Lunn <andrew@lunn.ch>
      Cc: Gregory CLEMENT <gregory.clement@free-electrons.com>
      Cc: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
      Acked-by: NJason Cooper <jason@lakedaemon.net>
      Cc: stable@vger.kernel.org
      Signed-off-by: NMichael Turquette <mturquette@deferred.io>
      1022c75f
  3. 02 10月, 2013 1 次提交
  4. 30 9月, 2013 9 次提交
  5. 23 9月, 2013 1 次提交
    • L
      clk: nomadik: set all timers to use 2.4 MHz TIMCLK · eb6b036d
      Linus Walleij 提交于
      This fixes a regression for the Nomadik on the main system
      timers.
      
      The Nomadik seemed a bit slow and its heartbeat wasn't looking
      healthy. And it was not strange, because it has been connected
      to the 32768 Hz clock at boot, while being told by the clock driver
      that it was 2.4MHz. Actually connect the TIMCLK to 2.4MHz by
      default as this is what we want for nice scheduling, clocksource
      and clock event.
      
      Cc: stable@vger.kernel.org
      Signed-off-by: NLinus Walleij <linus.walleij@linaro.org>
      eb6b036d
  6. 10 9月, 2013 1 次提交
    • A
      clk: only call get_parent if there is one · 12d29886
      Alex Elder 提交于
      In __clk_init(), after a clock is mostly initialized, a scan is done
      of the orphan clocks to see if the clock being registered is the
      parent of any of them.
      
      This code assumes that any clock that provides a get_parent method
      actually has at least one parent, and that's not a valid assumption.
      
      As a result, an orphan clock with no parent can return *something*
      as the parent index, and that value is blindly used to dereference
      the orphan's parent_names[] array (which will be ZERO_SIZE_PTR or
      NULL).
      
      Fix this by ensuring get_parent is only called for orphans with at
      least one parent.
      Signed-off-by: NAlex Elder <elder@linaro.org>
      Signed-off-by: NMike Turquette <mturquette@linaro.org>
      12d29886
  7. 07 9月, 2013 13 次提交
  8. 04 9月, 2013 1 次提交
  9. 31 8月, 2013 2 次提交
  10. 30 8月, 2013 6 次提交
  11. 29 8月, 2013 2 次提交