1. 12 7月, 2012 2 次提交
    • L
      ARM: integrator: convert to common clock · a613163d
      Linus Walleij 提交于
      This converts the Integrator platform to use common clock
      and the ICST driver. Since from this point not all ARM
      reference platforms use the clock, we define
      CONFIG_PLAT_VERSATILE_CLOCK and select it for all platforms
      except the Integrator.
      
      Open issue: I could not use the .init_early() field of the
      machine descriptor to initialize the clocks, but had to
      move them to .init_irq(), so presumably .init_early() is
      so early that common clock is not up, and .init_machine()
      is too late since it's needed for the clockevent/clocksource
      initialization. Any suggestions on how to solve this is
      very welcome.
      
      Cc: Russell King <linux@arm.linux.org.uk>
      Signed-off-by: NLinus Walleij <linus.walleij@linaro.org>
      [mturquette@linaro.org: use 'select' instead of versatile Kconfig]
      Signed-off-by: NMike Turquette <mturquette@linaro.org>
      a613163d
    • L
      ARM: u300: convert to common clock · 50667d63
      Linus Walleij 提交于
      This converts the U300 clock implementation over to use the common
      struct clk and moves the implementation down into drivers/clk.
      Since VCO isn't used in tree it was removed, it's not hard to
      put it back in if need be.
      Signed-off-by: NLinus Walleij <linus.walleij@linaro.org>
      [mturquette@linaro.org: trivial Makefile conflict]
      Signed-off-by: NMike Turquette <mturquette@linaro.org>
      50667d63
  2. 24 6月, 2012 1 次提交
    • A
      ARM: Orion5x - Restore parts of io.h, with rework · b5e12229
      Andrew Lunn 提交于
      Commit 4d5fc58d (ARM: remove bunch of
      now unused mach/io.h files) removed the orion5x io.h. Unfortunately,
      this is still needed for the definition of IO_SPACE_LIMIT which
      overrides the default 64K. All Orion based systems have 1Mbyte of IO
      space per PCI[e] bus, and try to request_resource() this size. Orion5x
      has two such PCI buses.
      
      It is likely that the original, removed version, was broken. This
      version might be less broken. However, it has not been tested on
      hardware with a PCI card, let alone hardware with a PCI card with IO
      capabilities.
      Signed-off-by: NAndrew Lunn <andrew@lunn.ch>
      Acked-by: NRob Herring <rob.herring@calxeda.com>
      Signed-off-by: NOlof Johansson <olof@lixom.net>
      b5e12229
  3. 17 6月, 2012 1 次提交
    • A
      arm: versatile: fix and enable PCI I/O space · 9b0f7e39
      Arnd Bergmann 提交于
      With commit 4d5fc58d (ARM: remove bunch of now unused
      mach/io.h files), the I/O space setup was completely broken on
      versatile. This patch fixes that and prepares for further
      I/O space clean-up.
      
      I/O space handling on the versatile platform is currently
      broken in multiple ways. Most importantly, the ports do
      not get mapped into the virtual address space at all.
      
      Also, there is some amount of confusion between PCI I/O
      space and other statically mapped MMIO registers in the
      platform code:
      
      * The __io_address() macro that is used to access the
        platform register maps to the same __io macro that gets
        used for I/O space.
      
      * The IO_SPACE_LIMIT is set to a value that is much larger
        than the total available space.
      
      * The I/O resource of the PCI bus is set to the physical
        address of the mapping, which is way outside of the
        actual I/O space limit as well as the address range that
        gets decoded by traditional PCI cards.
      
      * No attempt is made to stay outside of the ISA port range
        that some device drivers try access.
      
      * No resource gets requested as a child of ioport_resource,
        but an IORESOURCE_IO type mapping gets requested
        as a child of iomem_resource.
      
      This patch attempts to correct all of the above. This makes
      it possible to use virtio-pci based virtual devices as well
      as actual PCI cards including those with legacy ISA port
      ranges like VGA.
      
      Some of the issues seem to be duplicated on other platforms.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      [rob: update to 3.5-rc2 and io.h cleanup related changes]
      Signed-off-by: NRob Herring <rob.herring@calxeda.com>
      Tested-by: NRobert Schwebel <r.schwebel@pengutronix.de>
      Signed-off-by: NOlof Johansson <olof@lixom.net>
      9b0f7e39
  4. 04 6月, 2012 1 次提交
  5. 24 5月, 2012 1 次提交
  6. 22 5月, 2012 2 次提交
  7. 21 5月, 2012 5 次提交
  8. 18 5月, 2012 1 次提交
  9. 15 5月, 2012 3 次提交
  10. 13 5月, 2012 2 次提交
  11. 12 5月, 2012 3 次提交
  12. 09 5月, 2012 2 次提交
  13. 08 5月, 2012 1 次提交
  14. 07 5月, 2012 1 次提交
  15. 05 5月, 2012 3 次提交
  16. 04 5月, 2012 1 次提交
    • L
      ARM: 7389/2: plat-versatile: modernize FPGA IRQ controller · 3108e6ab
      Linus Walleij 提交于
      This does two things to the FPGA IRQ controller in the versatile
      family:
      
      - Convert to MULTI_IRQ_HANDLER so we can drop the entry macro
        from the Integrator. The C IRQ handler was inspired from
        arch/arm/common/vic.c, recent bug discovered in this handler was
        accounted for.
      - Convert to using IRQ domains so we can get rid of the NO_IRQ
        mess and proceed with device tree and such stuff.
      
      As part of the exercise, bump all the low IRQ numbers on the
      Integrator PIC to start from 1 rather than 0, since IRQ 0 is
      now NO_IRQ. The Linux IRQ numbers are thus entirely decoupled
      from the hardware IRQ numbers in this controller.
      
      I was unable to split this patch. The main reason is the half-done
      conversion to device tree in Versatile.
      
      Tested on Integrator/AP and Integrator/CP.
      
      Cc: Grant Likely <grant.likely@secretlab.ca>
      Acked-by: NRob Herring <rob.herring@calxeda.com>
      Signed-off-by: NLinus Walleij <linus.walleij@linaro.org>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      3108e6ab
  17. 03 5月, 2012 1 次提交
  18. 27 4月, 2012 1 次提交
  19. 26 4月, 2012 2 次提交
  20. 25 4月, 2012 1 次提交
    • R
      ARM: Remove unnecessary selection of TICK_ONESHOT · 98fab064
      Russell King 提交于
      In 3872c48b (tick: Document TICK_ONESHOT config option) Thomas describes
      the circumstances under which TICK_ONESHOT should be selected.  This is
      an internal time keeping configuration symbol which should not be
      selected by platform or arch code.  So remove our select statements for
      it.
      
      This kills these warnings in OMAP builds:
      
      kernel/time/tick-sched.c:47: warning: 'tick_do_update_jiffies64' defined but not used
      kernel/time/tick-sched.c:89: warning: 'tick_init_jiffy_update' defined but not used
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      98fab064
  21. 23 4月, 2012 1 次提交
  22. 22 4月, 2012 1 次提交
  23. 20 4月, 2012 1 次提交
  24. 18 4月, 2012 1 次提交
  25. 16 4月, 2012 1 次提交