1. 03 6月, 2015 9 次提交
  2. 30 3月, 2015 3 次提交
  3. 24 3月, 2015 1 次提交
  4. 13 3月, 2015 6 次提交
  5. 12 3月, 2015 1 次提交
    • S
      ARM: imx: fix struct clk pointer comparing · a51139fd
      Shawn Guo 提交于
      Since commit 035a61c3 ("clk: Make clk API return per-user struct clk
      instances"), clk API users can no longer check if two struct clk
      pointers are pointing to the same hardware clock, i.e. struct clk_hw, by
      simply comparing two pointers.  That's because with the per-user clk
      change, a brand new struct clk is created whenever clients try to look
      up the clock by calling clk_get() or sister functions like clk_get_sys()
      and of_clk_get().  This changes the original behavior where the struct
      clk is only created for once when clock driver registers the clock to
      CCF in the first place.  The net change here is before commit
      035a61c3 the struct clk pointer is unique for given hardware
      clock, while after the commit the pointers returned by clk lookup calls
      become different for the same hardware clock.
      
      That said, the struct clk pointer comparing in the code doesn't work any
      more.  Call helper function clk_is_match() instead to fix the problem.
      Signed-off-by: NShawn Guo <shawn.guo@linaro.org>
      Signed-off-by: NMichael Turquette <mturquette@linaro.org>
      Signed-off-by: NStephen Boyd <sboyd@codeaurora.org>
      a51139fd
  6. 11 3月, 2015 4 次提交
  7. 08 3月, 2015 1 次提交
    • S
      irqchip: vf610-mscm-ir: Add support for Vybrid MSCM interrupt router · 0494e11a
      Stefan Agner 提交于
      This adds support for Vybrid's interrupt router. On VF6xx models,
      almost all peripherals can be used by either of the two CPU's,
      the Cortex-A5 or the Cortex-M4. The interrupt router routes the
      peripheral interrupts to the configured CPU.
      
      This IRQ chip driver configures the interrupt router to route
      the requested interrupt to the CPU the kernel is running on.
      The driver makes use of the irqdomain hierarchy support. The
      parent is given by the device tree. This should be one of the
      two possible parents either ARM GIC or the ARM NVIC interrupt
      controller. The latter is currently not yet supported.
      
      Note that there is no resource control mechnism implemented to
      avoid concurrent access of the same peripheral. The user needs
      to make sure to use device trees which assign the peripherals
      orthogonally. However, this driver warns the user in case the
      interrupt is already configured for the other CPU. This provides
      a poor man's resource controller.
      Acked-by: NMarc Zyngier <marc.zyngier@arm.com>
      Signed-off-by: NStefan Agner <stefan@agner.ch>
      Link: https://lkml.kernel.org/r/1425249689-32354-2-git-send-email-stefan@agner.chSigned-off-by: NJason Cooper <jason@lakedaemon.net>
      0494e11a
  8. 06 3月, 2015 1 次提交
  9. 03 3月, 2015 3 次提交
  10. 02 3月, 2015 5 次提交
  11. 26 2月, 2015 1 次提交
  12. 19 2月, 2015 1 次提交
  13. 20 1月, 2015 2 次提交
  14. 13 1月, 2015 2 次提交