1. 13 3月, 2016 1 次提交
  2. 24 2月, 2016 1 次提交
  3. 10 9月, 2015 1 次提交
  4. 24 7月, 2015 1 次提交
  5. 28 4月, 2015 1 次提交
  6. 04 4月, 2015 1 次提交
  7. 23 9月, 2014 1 次提交
  8. 12 9月, 2014 1 次提交
  9. 29 5月, 2014 1 次提交
    • K
      ARM: dts: qcom: Update msm8660 device trees · 66a6c317
      Kumar Gala 提交于
      * Move SoC peripherals into an SoC container node
      * Move serial enabling into board file (qcom-msm8660-surf.dts)
      * Cleanup cpu node to match binding spec, enable-method and compatible
        should be per cpu, not part of the container
      * Add GSBI node and configuration of GSBI controller
      Signed-off-by: NKumar Gala <galak@codeaurora.org>
      66a6c317
  10. 21 2月, 2014 1 次提交
  11. 04 2月, 2014 1 次提交
  12. 01 2月, 2014 1 次提交
  13. 11 1月, 2014 1 次提交
  14. 26 9月, 2013 1 次提交
  15. 29 8月, 2013 1 次提交
  16. 13 6月, 2013 1 次提交
  17. 31 5月, 2013 1 次提交
  18. 26 3月, 2013 1 次提交
  19. 23 3月, 2013 1 次提交
    • S
      ARM: msm: Rework timer binding to be more general · eebdb0c1
      Stephen Boyd 提交于
      The msm timer binding I wrote is bad. First off, the clock
      frequency in the binding for the dgt is wrong. Software divides
      down the input rate by 4 to achieve the rate listed in the
      binding. We also treat each individual timer as a separate
      hardware component, when in reality there is one timer block
      (that may be duplicated per cpu) with multiple timers within it.
      Depending on the version of the hardware there can be one or two
      general purpose timers, status and divider control registers, and
      an entirely different register layout.
      
      In the next patch we'll need to know about the different register
      layouts so that we can properly check the status register after
      clearing the count. The current binding makes this complicated
      because the general purpose timer's reg property doesn't indicate
      where that status register is, and in fact it is beyond the size
      of the reg property.
      
      Clean all this up by just having one node for the timer hardware,
      and describe all the interrupts and clock frequencies supported
      while having one reg property that covers the entire timer
      register region. We'll use the compatible field in the future to
      determine different register layouts and if we should read the
      status registers, etc.
      Signed-off-by: NStephen Boyd <sboyd@codeaurora.org>
      Signed-off-by: NDavid Brown <davidb@codeaurora.org>
      eebdb0c1
  20. 14 9月, 2012 1 次提交
  21. 24 4月, 2012 1 次提交
  22. 30 8月, 2011 1 次提交