1. 21 5月, 2015 1 次提交
  2. 09 10月, 2013 1 次提交
  3. 04 7月, 2013 1 次提交
  4. 12 1月, 2013 1 次提交
    • T
      ARM: OMAP2+: Use omap initcalls · b76c8b19
      Tony Lindgren 提交于
      This way the initcalls don't run on other SoCs on multiplatform
      kernels. Otherwise we'll get something like this when booting
      on vexpress:
      
      omap_hwmod: _ensure_mpu_hwmod_is_setup: MPU initiator hwmod mpu not yet registered
      ...
      WARNING: at arch/arm/mach-omap2/pm.c:82 _init_omap_device+0x74/0x94()
      _init_omap_device: could not find omap_hwmod for mpu
      ...
      omap-dma-engine omap-dma-engine: OMAP DMA engine driver
      ...
      Tested-by: NEzequiel Garcia <ezequiel.garcia@free-electrons.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      b76c8b19
  5. 18 12月, 2012 1 次提交
    • T
      ARM: OMAP: Split fb.c to remove last remaining cpu_is_omap usage · 16d60bb8
      Tony Lindgren 提交于
      Looks like we missed plat-omap/fb.c for cpu_is_omap usage
      mach-omap2. This is the last user of cpu_is_omap, so let's
      quickly fix it up so we can finally remove plat/cpu.h for
      omap2lus.
      
      We want to limit cpu_is_omap macro usage to mach-omap2 only so
      we can make plat/cpu.h private. After this we can finally drop
      plat/cpu.h for omap2+.
      
      Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      16d60bb8
  6. 13 11月, 2012 1 次提交
  7. 03 11月, 2012 1 次提交
  8. 17 10月, 2012 1 次提交
    • T
      OMAP: VRFB: convert vrfb to platform device · 406c8563
      Tomi Valkeinen 提交于
      This patch converts vrfb library into a platform device, in an effort to
      remove omap dependencies.
      
      The platform device is registered in arch/arm/plat-omap/fb.c and
      assigned resources depending on whether running on omap2 or omap3.
      
      The vrfb driver will parse those resources and use them to access vrfb
      configuration registers and the vrfb virtual rotation areas.
      Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      Cc: Tony Lindgren <tony@atomide.com>
      406c8563
  9. 11 9月, 2012 1 次提交
  10. 09 3月, 2012 1 次提交
  11. 23 2月, 2012 5 次提交
  12. 23 10月, 2010 4 次提交
  13. 09 10月, 2010 1 次提交
    • M
      OMAP: plat-omap: Fix static function warnings · b0a330dc
      Manjunath Kondaiah G 提交于
      This patch fixes sparse warnings due non declarations of static functions.
      
      arch/arm/plat-omap/sram.c:130:13: warning: symbol 'omap_detect_sram' was not declared. Should it be static?
      arch/arm/plat-omap/sram.c:216:13: warning: symbol 'omap_map_sram' was not declared. Should it be static?
      arch/arm/plat-omap/sram.c:450:12: warning: symbol 'omap_sram_init' was not declared. Should it be static?
      arch/arm/plat-omap/sram.c:348:12: warning: symbol 'omap242x_sram_init' was not declared. Should it be static?
      arch/arm/plat-omap/sram.c:369:12: warning: symbol 'omap243x_sram_init' was not declared. Should it be static?
      arch/arm/plat-omap/sram.c:425:12: warning: symbol 'omap34xx_sram_init' was not declared. Should it be static?
      arch/arm/plat-omap/sram.c:441:12: warning: symbol 'omap44xx_sram_init' was not declared. Should it be static
      
      arch/arm/plat-omap/mcbsp.c:36:6: warning: symbol 'omap_mcbsp_write' was not declared. Should it be static?
      arch/arm/plat-omap/mcbsp.c:50:5: warning: symbol 'omap_mcbsp_read' was not declared. Should it be static?
      arch/arm/plat-omap/mcbsp.c:65:6: warning: symbol 'omap_mcbsp_st_write' was not declared. Should it be static?
      arch/arm/plat-omap/mcbsp.c:70:5: warning: symbol 'omap_mcbsp_st_read' was not declared. Should it be static?
      arch/arm/plat-omap/mcbsp.c:1648:15: warning: symbol 'omap_st_add' was not declared. Should it be static?
      
      arch/arm/plat-omap/fb.c:414:15: warning: symbol 'omapfb_reserve_sram' was not declared. Should it be static?
      arch/arm/plat-omap/cpu-omap.c:43:5: warning: symbol 'omap_verify_speed' was not declared. Should it be static?
      arch/arm/plat-omap/cpu-omap.c:61:14: warning: symbol 'omap_getspeed' was not declared. Should it be static?
      Signed-off-by: NManjunath Kondaiah G <manjugk@ti.com>
      Cc: linux-arm-kernel@lists.infradead.org
      Cc: Nishanth Menon <nm@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      b0a330dc
  14. 08 10月, 2010 1 次提交
  15. 04 8月, 2010 2 次提交
  16. 27 7月, 2010 1 次提交
  17. 16 7月, 2010 1 次提交
    • R
      ARM: OMAP: Cleanup OMAP FB SDRAM reservation · a1af0fbb
      Russell King 提交于
      The logic in this file is rather convoluted, but essentially:
      
      1. region type 0 is SDRAM
      2. referring to the code fragment
                      if (set_fbmem_region_type(&rg, OMAPFB_MEMTYPE_SDRAM,
                                                sdram_start, sdram_size) < 0 ||
                          (rg.type != OMAPFB_MEMTYPE_SDRAM))
                              continue;
         - if rg.type is not OMAPFB_MEMTYPE_SDRAM, set_fbmem_region_type()
           returns zero immediately (since rg.type is non-zero), and so we
           'continue'.
         - if rg.type is OMAPFB_MEMTYPE_SDRAM, and rg.paddr is zero,
           we fall through.
         - if rg.type is OMAPFB_MEMTYPE_SDRAM, and the region lies within
           SDRAM, we fall through.
         - if rg.type is OMAPFB_MEMTYPE_SDRAM, and the region is not within
           SDRAM, we 'continue'.
      3. check_fbmem_region seems unnecessary.
         - we know rg.type is OMAPFB_MEMTYPE_SDRAM
         - we can check rg.size independently
         - bootmem_reserve() can check for overlapping reservations itself
         - we've already validated that the requested region lies within SDRAM.
      4. avoid BUG()ing if the region entry is already set; print an error,
         and mark the configuration invalid - at least we'll continue booting
         so the error message has a chance of being logged/visible via serial
         console.
      
      With these changes in place, it makes the code much easier to understand
      and hence easier to convert to LMB.
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      a1af0fbb
  18. 09 12月, 2009 2 次提交
  19. 21 10月, 2009 1 次提交
    • T
      omap: headers: Move remaining headers from include/mach to include/plat · ce491cf8
      Tony Lindgren 提交于
      Move the remaining headers under plat-omap/include/mach
      to plat-omap/include/plat. Also search and replace the
      files using these headers to include using the right path.
      
      This was done with:
      
      #!/bin/bash
      mach_dir_old="arch/arm/plat-omap/include/mach"
      plat_dir_new="arch/arm/plat-omap/include/plat"
      headers=$(cd $mach_dir_old && ls *.h)
      omap_dirs="arch/arm/*omap*/ \
      drivers/video/omap \
      sound/soc/omap"
      other_files="drivers/leds/leds-ams-delta.c \
      drivers/mfd/menelaus.c \
      drivers/mfd/twl4030-core.c \
      drivers/mtd/nand/ams-delta.c"
      
      for header in $headers; do
      	old="#include <mach\/$header"
      	new="#include <plat\/$header"
      	for dir in $omap_dirs; do
      		find $dir -type f -name \*.[chS] | \
      			xargs sed -i "s/$old/$new/"
      	done
      	find drivers/ -type f -name \*omap*.[chS] | \
      		xargs sed -i "s/$old/$new/"
      	for file in $other_files; do
      		sed -i "s/$old/$new/" $file
      	done
      done
      
      for header in $(ls $mach_dir_old/*.h); do
      	git mv $header $plat_dir_new/
      done
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      ce491cf8
  20. 12 5月, 2009 1 次提交
  21. 06 9月, 2008 1 次提交
  22. 07 8月, 2008 3 次提交
  23. 25 7月, 2008 2 次提交
  24. 08 2月, 2008 1 次提交
    • B
      Introduce flags for reserve_bootmem() · 72a7fe39
      Bernhard Walle 提交于
      This patchset adds a flags variable to reserve_bootmem() and uses the
      BOOTMEM_EXCLUSIVE flag in crashkernel reservation code to detect collisions
      between crashkernel area and already used memory.
      
      This patch:
      
      Change the reserve_bootmem() function to accept a new flag BOOTMEM_EXCLUSIVE.
      If that flag is set, the function returns with -EBUSY if the memory already
      has been reserved in the past.  This is to avoid conflicts.
      
      Because that code runs before SMP initialisation, there's no race condition
      inside reserve_bootmem_core().
      
      [akpm@linux-foundation.org: coding-style fixes]
      [akpm@linux-foundation.org: fix powerpc build]
      Signed-off-by: NBernhard Walle <bwalle@suse.de>
      Cc: <linux-arch@vger.kernel.org>
      Cc: "Eric W. Biederman" <ebiederm@xmission.com>
      Cc: Vivek Goyal <vgoyal@in.ibm.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      72a7fe39
  25. 06 11月, 2007 1 次提交
  26. 09 5月, 2007 3 次提交