1. 21 11月, 2012 1 次提交
  2. 14 11月, 2012 2 次提交
  3. 12 11月, 2012 1 次提交
  4. 07 11月, 2012 1 次提交
  5. 06 11月, 2012 1 次提交
    • R
      ARM: implement debug_ll_io_init() · e5c5f2ad
      Rob Herring 提交于
      When using DEBUG_LL, the UART's (or other HW's) registers are mapped
      into early page tables based on the results of assembly macro addruart.
      Later, when the page tables are replaced, the same virtual address must
      remain valid. Historically, this has been ensured by using defines from
      <mach/iomap.h> in both the implementation of addruart, and the machine's
      .map_io() function. However, with the move to single zImage, we wish to
      remove <mach/iomap.h>. To enable this, the macro addruart may be used
      when constructing the late page tables too; addruart is exposed as a
      C function debug_ll_addr(), and used to set up the required mapping in
      debug_ll_io_init(), which may called on an opt-in basis from a machine's
      .map_io() function.
      Signed-off-by: NRob Herring <rob.herring@calxeda.com>
      [swarren: Mask map.virtual with PAGE_MASK. Checked for NULL results from
       debug_ll_addr (e.g. when selected UART isn't valid). Fixed compile when
       either !CONFIG_DEBUG_LL or CONFIG_DEBUG_SEMIHOSTING.]
      Signed-off-by: NStephen Warren <swarren@nvidia.com>
      Signed-off-by: NOlof Johansson <olof@lixom.net>
      e5c5f2ad
  6. 05 11月, 2012 2 次提交
  7. 30 10月, 2012 1 次提交
  8. 29 10月, 2012 4 次提交
    • J
      zynq: move static peripheral mappings · f5800776
      Josh Cartwright 提交于
      Shifting them up into the vmalloc region prevents the following warning,
      when booting a zynq qemu target with more than 512mb of RAM:
      
        BUG: mapping for 0xe0000000 at 0xe0000000 out of vmalloc space
      
      In addition, it allows for reuse of these mappings when the proper
      drivers issue requests via ioremap().
      
      There are currently unknown issues with the early uart mapping.  For
      now, the uart will be mapped to a known working address.
      Signed-off-by: NJosh Cartwright <josh.cartwright@ni.com>
      Cc: John Linn <john.linn@xilinx.com>
      Acked-by: NArnd Bergmann <arnd@arndb.de>
      Tested-by: NMichal Simek <michal.simek@xilinx.com>
      f5800776
    • J
      zynq: remove use of CLKDEV_LOOKUP · f7977939
      Josh Cartwright 提交于
      The Zynq support in mainline does not (yet) make use of any of the
      generic clk or clk lookup functionality.  Remove what is upstream for
      now, until the out-of-tree implementation is in suitable form for
      merging.
      
      An important side effect of this patch is that it allows the building of
      a Zynq kernel without running into unresolved symbol problems:
      
         drivers/built-in.o: In function `amba_get_enable_pclk':
         clkdev.c:(.text+0x444): undefined reference to `clk_enable'
         drivers/built-in.o: In function `amba_remove':
         clkdev.c:(.text+0x488): undefined reference to `clk_disable'
         drivers/built-in.o: In function `amba_probe':
         clkdev.c:(.text+0x540): undefined reference to `clk_disable'
         drivers/built-in.o: In function `amba_device_add':
         clkdev.c:(.text+0x77c): undefined reference to `clk_disable'
         drivers/built-in.o: In function `enable_clock':
         clkdev.c:(.text+0x29738): undefined reference to `clk_enable'
         drivers/built-in.o: In function `disable_clock':
         clkdev.c:(.text+0x29778): undefined reference to `clk_disable'
         drivers/built-in.o: In function `__pm_clk_remove':
         clkdev.c:(.text+0x297f8): undefined reference to `clk_disable'
         drivers/built-in.o: In function `pm_clk_suspend':
         clkdev.c:(.text+0x29bc8): undefined reference to `clk_disable'
         drivers/built-in.o: In function `pm_clk_resume':
         clkdev.c:(.text+0x29c28): undefined reference to `clk_enable'
         make[2]: *** [vmlinux] Error 1
         make[1]: *** [sub-make] Error 2
         make: *** [all] Error 2
      
      In addition, eliminate Zynq's "use" of the versatile platform, as it is
      no longer needed.  As Nick Bowler points out:
      
         For the record, I think this was introduced by commit 56a34b03
         ("ARM: versatile: Make plat-versatile clock optional") which forgot to
         select PLAT_VERSATILE_CLOCK on Zynq.  This is not all that surprising,
         because the fact that Zynq "uses" PLAT_VERSATILE is secretly hidden in
         the Makefile.
      
         Nevertheless, the only feature from versatile that Zynq needed was the
         clock support, so this patch should *also* delete the secret use of
         plat-versatile by removing this line from arch/arm/Makefile:
      
            plat-$(CONFIG_ARCH_ZYNQ)      += versatile
      Signed-off-by: NJosh Cartwright <josh.cartwright@ni.com>
      Cc: John Linn <john.linn@xilinx.com>
      Acked-by: NArnd Bergmann <arnd@arndb.de>
      Tested-by: NMichal Simek <michal.simek@xilinx.com>
      f7977939
    • J
      zynq: use pl310 device tree bindings · 0fcfdbca
      Josh Cartwright 提交于
      The Zynq has a PL310 L2 cache controller.  Convert in-tree uses to using
      the device tree.
      Signed-off-by: NJosh Cartwright <josh.cartwright@ni.com>
      Cc: John Linn <john.linn@xilinx.com>
      Acked-by: NArnd Bergmann <arnd@arndb.de>
      Tested-by: NMichal Simek <michal.simek@xilinx.com>
      0fcfdbca
    • J
      zynq: use GIC device tree bindings · f447ed2d
      Josh Cartwright 提交于
      The Zynq uses the cortex-a9-gic.  This eliminates the need to hardcode
      register addresses.
      Signed-off-by: NJosh Cartwright <josh.cartwright@ni.com>
      Cc: John Linn <john.linn@xilinx.com>
      Acked-by: NArnd Bergmann <arnd@arndb.de>
      Tested-by: NMichal Simek <michal.simek@xilinx.com>
      f447ed2d
  9. 27 10月, 2012 4 次提交
  10. 26 10月, 2012 1 次提交
  11. 25 10月, 2012 14 次提交
  12. 24 10月, 2012 3 次提交
  13. 23 10月, 2012 5 次提交
    • M
      ARM: dma-mapping: support debug_dma_mapping_error · 871ae57a
      Ming Lei 提交于
      Without the patch, kind of below warning will be dumped if DMA-API
      debug is enabled:
      
      [   11.069763] ------------[ cut here ]------------
      [   11.074645] WARNING: at lib/dma-debug.c:948 check_unmap+0x770/0x860()
      [   11.081420] ehci-omap ehci-omap.0: DMA-API: device driver failed to
      check map error[device address=0x0000000
      0adb78e80] [size=8 bytes] [mapped as single]
      [   11.095611] Modules linked in:
      
      Cc: Russell King <linux@arm.linux.org.uk>
      Cc: Marek Szyprowski <m.szyprowski@samsung.com>
      Signed-off-by: NMing Lei <ming.lei@canonical.com>
      Signed-off-by: NMarek Szyprowski <m.szyprowski@samsung.com>
      871ae57a
    • K
      ARM: OMAP3: Beagle: fix OPP customization and initcall ordering · 65bf7ca0
      Kevin Hilman 提交于
      After commit 24d7b40a (ARM: OMAP2+:
      PM: MPU DVFS: use generic CPU device for MPU-SS), OPPs are registered
      using an existing CPU device, not the omap_device for MPU-SS.
      
      First, fix the board file to use get_cpu_device() as required by the
      above commit, otherwise custom OPPs will be added to the wrong device.
      
      Second, the board files OPP init is called from the its init_machine
      method, and the generic CPU devices are not yet created when
      init_machine is run.  Therefore OPP initialization will fail.  To fix,
      use a device_initcall() for the board file's OPP customization, and
      make the device_initcall board-specific by using a machine_is check.
      Reported-by: NPaul Walmsley <paul@pwsan.com>
      Signed-off-by: NKevin Hilman <khilman@ti.com>
      65bf7ca0
    • R
      ARM: drop experimental status for hotplug and Thumb2 · 00b7dede
      Russell King 提交于
      Both these features have been around for a long time now, and haven't
      had any recent issues brought up.  So lets drop their experimental
      status.
      
      In any case, hotplugis  selected by other non-experimental options
      which then cause a Kconfig warning.
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      00b7dede
    • T
      ARM: OMAP3: Fix 3430 legacy mux names for ssi1 signals. · 1d8643dd
      Tony Lindgren 提交于
      On n900 uart1 pins are not not used for uart, instead they are
      used to connect to a cell modem over ssi. Looks like we're
      currently missing these signal names for 3430 for some reason,
      and only have some of them listed for 3630. Obviously the signals
      are there for 3430 if n900 is using them and they are documented
      in some TRMs.
      
      Note that these will eventually be replaced by device tree
      based pinctrl-single.c driver. But for now these are needed
      to verify the SSI pins for devices like Nokia N900.
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      1d8643dd
    • T
      ARM: OMAP2+: Fix location of select PINCTRL · 24942e8a
      Tony Lindgren 提交于
      Commit 8f31cefe (ARM: OMAP2+: select PINCTRL in Kconfig)
      added select PINCTRL, but accdentally added it to a wrong
      location.
      
      We want to select if for ARCH_OMAP2PLUS, not for
      ARCH_OMAP2PLUS_TYPICAL.
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      24942e8a