1. 20 11月, 2012 6 次提交
  2. 19 11月, 2012 1 次提交
  3. 07 11月, 2012 3 次提交
  4. 30 10月, 2012 1 次提交
  5. 29 10月, 2012 2 次提交
  6. 27 10月, 2012 4 次提交
  7. 26 10月, 2012 1 次提交
  8. 25 10月, 2012 14 次提交
  9. 24 10月, 2012 3 次提交
  10. 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