1. 13 5月, 2015 2 次提交
    • R
      ARM: pxa: Transition pxa25x, pxa27x, pxa3xx to clk framework · a1c0a6ad
      Robert Jarzmik 提交于
      Transition the PXA25x, PXA27x and PXA3xx CPUs to the clock framework.
      This transition still enables legacy platforms to run without device
      tree as before, ie relying on platform data encoded in board specific
      files.
      
      This is the last step of clock framework transition for pxa
      platforms. It was tested on lubbock (pxa25x), mioa701 (pxa27x) and
      zylonite (pxa3xx).
      Signed-off-by: NRobert Jarzmik <robert.jarzmik@free.fr>
      a1c0a6ad
    • R
      ARM: pxa: change clocks init sequence · 5e1d0128
      Robert Jarzmik 提交于
      Since pxa clocks were ported to the clock framework, an ordering issue
      appears between clocks and clocksource initialization. As a consequence,
      the pxa timer clock cannot be acquired in pxa_timer, and is disabled by
      clock framework because it is "unused".
      
      The ordering issue is that in the kernel boot sequence :
        start_kernel()
          ...
          time_init()
            -> pxa_timer()
              -> here the clocksource is initialized
          ...
          rest_init()
            kernel_init()
      	initcalls
      	  -> here the clocks are initialized
      
      In the current sequence, the clocks are initialized way after pxa_timer,
      which cannot acquire the OSTIMER0 clock.
      
      To solve this issue, the clocks initialization is moved to pxa_timer(),
      so that clocks are initialized before clocksource for non device-tree.
      For device-tree, the standard arm time_init() will take care of the
      ordering.
      Reviewed-by: NMichael Turquette <mturquette@linaro.org>
      Signed-off-by: NRobert Jarzmik <robert.jarzmik@free.fr>
      5e1d0128
  2. 09 9月, 2014 1 次提交
  3. 23 7月, 2014 1 次提交
  4. 13 7月, 2014 2 次提交
  5. 04 7月, 2014 1 次提交
  6. 29 3月, 2012 1 次提交
  7. 08 8月, 2011 1 次提交
  8. 15 1月, 2011 1 次提交
    • R
      ARM: Fix build regression on SA11x0, PXA, and H720x targets · 671289c2
      Russell King 提交于
      Build errors similar this appeared in todays kautobuild for the above
      targets:
      
      In file included from arch/arm/include/asm/pgtable.h:461,
                       from arch/arm/mach-pxa/generic.c:26:
      include/asm-generic/pgtable.h: In function 'ptep_test_and_clear_young':
      include/asm-generic/pgtable.h:29: error: dereferencing pointer to incomplete type
      
      None of the .c files including asm/pgtable.h with this error is using
      this header, so simply remove the include.
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      671289c2
  9. 18 12月, 2010 1 次提交
  10. 16 12月, 2010 4 次提交
  11. 09 10月, 2010 2 次提交
  12. 11 5月, 2010 1 次提交
  13. 09 3月, 2009 2 次提交
  14. 29 12月, 2008 1 次提交
  15. 08 10月, 2008 1 次提交
  16. 25 9月, 2008 1 次提交
  17. 07 8月, 2008 2 次提交
  18. 05 8月, 2008 1 次提交
  19. 10 7月, 2008 1 次提交
  20. 03 6月, 2008 1 次提交
  21. 30 4月, 2008 1 次提交
  22. 19 4月, 2008 1 次提交
  23. 06 2月, 2008 1 次提交
  24. 04 2月, 2008 1 次提交
  25. 26 1月, 2008 5 次提交
  26. 16 10月, 2007 2 次提交
  27. 13 10月, 2007 1 次提交
    • E
      [ARM] 4559/1: pxa: make PXA_LAST_GPIO a run-time variable · 30f0b408
      eric miao 提交于
      This definition produces processor specific code in generic function
      pxa_gpio_mode(), thus creating inconsistencies for support of pxa25x
      and pxa27x in a single zImage.
      
      As David Brownell suggests, make it a run-time variable and initialize
      at run-time according to the number of GPIOs on the processor. For now
      the initialization happens in pxa_init_irq_gpio(),  since there is
      already a parameter for that, besides, this is and MUST be earlier
      than any subsequent calls to pxa_gpio_mode().
      Signed-off-by: Neric miao <eric.y.miao@gmail.com>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      30f0b408