1. 16 10月, 2012 1 次提交
  2. 13 9月, 2012 1 次提交
  3. 08 5月, 2012 1 次提交
  4. 13 4月, 2012 1 次提交
    • P
      ARM: OMAP: add includes for missing prototypes · e2ed89fc
      Paul Walmsley 提交于
      Several C files in arch/arm/mach-omap* and arch/arm/plat-omap declare
      functions that are used by other files, but don't include the header
      file where the prototype is declared.  This results in the following
      warnings from sparse:
      
          arch/arm/mach-omap2/irq.c:114:5: warning: symbol 'omap_irq_pending' was not declared. Should it be static?
          arch/arm/mach-omap2/irq.c:186:13: warning: symbol 'omap2_init_irq' was not declared. Should it be static?
          arch/arm/mach-omap2/irq.c:191:13: warning: symbol 'omap3_init_irq' was not declared. Should it be static?
          arch/arm/mach-omap2/irq.c:196:13: warning: symbol 'ti81xx_init_irq' was not declared. Should it be static?
          arch/arm/mach-omap2/irq.c:233:39: warning: symbol 'omap2_intc_handle_irq' was not declared. Should it be static?
          arch/arm/mach-omap2/irq.c:242:6: warning: symbol 'omap_intc_save_context' was not declared. Should it be static?
          arch/arm/mach-omap2/irq.c:265:6: warning: symbol 'omap_intc_restore_context' was not declared. Should it be static?
          arch/arm/mach-omap2/irq.c:291:6: warning: symbol 'omap3_intc_suspend' was not declared. Should it be static?
          arch/arm/mach-omap2/irq.c:297:6: warning: symbol 'omap3_intc_prepare_idle' was not declared. Should it be static?
          arch/arm/mach-omap2/irq.c:306:6: warning: symbol 'omap3_intc_resume_idle' was not declared. Should it be static?
          arch/arm/mach-omap2/irq.c:312:39: warning: symbol 'omap3_intc_handle_irq' was not declared. Should it be static?
          arch/arm/mach-omap2/omap-secure.c:59:12: warning: symbol 'omap_secure_ram_reserve_memblock' was not declared. Should it be static?
          arch/arm/mach-omap2/board-zoom-display.c:133:13: warning: symbol 'zoom_display_init' was not declared. Should it be static?
          arch/arm/plat-omap/common.c:73:13: warning: symbol 'omap_init_consistent_dma_size' was not declared. Should it be static?
          arch/arm/mach-omap1/irq.c:61:5: warning: symbol 'omap_irq_flags' was not declared. Should it be static?
          arch/arm/mach-omap1/irq.c:179:13: warning: symbol 'omap1_init_irq' was not declared. Should it be static?
          arch/arm/mach-omap1/reset.c:11:6: warning: symbol 'omap1_restart' was not declared. Should it be static?
      
      Fix by including the appropriate header files.
      Signed-off-by: NPaul Walmsley <paul@pwsan.com>
      Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
      Cc: Senthilvadivu Guruswamy <svadivu@ti.com>
      Acked-by: NSantosh Shilimkar <santosh.shilimkar@ti.com>
      
      e2ed89fc
  5. 10 8月, 2011 1 次提交
  6. 21 12月, 2010 5 次提交
  7. 12 10月, 2010 2 次提交
    • P
      OMAP3: DMA: Errata i541: sDMA FIFO draining does not finish · 0e4905c0
      Peter Ujfalusi 提交于
      Implement the suggested workaround for OMAP3 regarding to sDMA draining
      issue, when the channel is disabled on the fly.
      This errata affects the following configuration:
      sDMA transfer is source synchronized
      Buffering is enabled
      SmartStandby is selected.
      
      The issue can be easily reproduced by creating overrun situation while
      recording audio.
      Either introduce load to the CPU:
      nice -19 arecord -D hw:0 -M -B 10000 -F 5000 -f dat > /dev/null & \
      dd if=/dev/urandom of=/dev/null
      
      or suspending the arecord, and resuming it:
      arecord -D hw:0 -M -B 10000 -F 5000 -f dat > /dev/null
      CTRL+Z; fg; CTRL+Z; fg; ...
      
      In case of overrun audio stops DMA, and restarts it (without reseting
      the sDMA channel). When we hit this errata in stop case (sDMA drain did
      not complete), at the coming start the sDMA will not going to be
      operational (it is still draining).
      This leads to DMA stall condition.
      On OMAP3 we can recover with sDMA channel reset, it has been observed
      that by introducing unrelated sDMA activity might also help (reading
      from MMC for example).
      
      The same errata exists for OMAP2, where the suggestion is to disable the
      buffering to avoid this type of error.
      On OMAP3 the suggestion is to set sDMA to NoStandby before disabling
      the channel, and wait for the drain to finish, than configure sDMA to
      SmartStandby again.
      Signed-off-by: NPeter Ujfalusi <peter.ujfalusi@nokia.com>
      Acked-by: NJarkko Nikula <jhnikula@gmail.com>
      Acked-by : Santosh Shilimkar <santosh.shilimkar@ti.com>
      Acked-by : Manjunath Kondaiah G <manjugk@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      0e4905c0
    • J
      omap: dma: Fix buffering disable bit setting for omap24xx · 3e57f162
      Jarkko Nikula 提交于
      An errata workaround for omap24xx is not setting the buffering disable bit
      25 what is the purpose but channel enable bit 7 instead.
      
      Background for this fix is the DMA stalling issue with ASoC omap-mcbsp
      driver. Peter Ujfalusi <peter.ujfalusi@nokia.com> has found an issue in
      recording that the DMA stall could happen if there were a buffer overrun
      detected by ALSA and the DMA was stopped and restarted due that. This
      problem is known to occur on both OMAP2420 and OMAP3. It can recover on
      OMAP3 after dma free, dma request and reconfiguration cycle. However, on
      OMAP2420 it seems that only way to recover is a reset.
      
      Problem was not visible before the commit c12abc01. That commit changed that
      the McBSP transmitter/receiver is released from reset only when needed. That
      is, only enabled McBSP transmitter without transmission was able to prevent
      this DMA stall problem in receiving side and underlying problem did not show
      up until now. McBSP transmitter itself seems to no be reason since DMA
      stall does not recover by enabling the transmission after stall.
      
      Debugging showed that there were a DMA write active during DMA stop time and
      it never completed even when restarting the DMA. Experimenting showed that
      the DMA buffering disable bit could be used to avoid stalling when using
      source synchronized transfers. However that could have performance hit and
      OMAP3 TRM states that buffering disable is not allowed for destination
      synchronized transfers so subsequent patch will implement a method to
      complete DMA writes when stopping.
      
      This patch is based on assumtion that complete lock-up on OMAP2420 is
      different but related problem. I don't have access to OMAP2420 errata but
      I believe this old workaround here is put for a reason but unfortunately
      a wrong bit was typed and problem showed up only now.
      Signed-off-by: NJarkko Nikula <jhnikula@gmail.com>
      Signed-off-by: NPeter Ujfalusi <peter.ujfalusi@nokia.com>
      Acked-by: NManjunath Kondaiah G <manjugk@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      3e57f162
  8. 30 9月, 2010 1 次提交
  9. 02 8月, 2010 1 次提交
  10. 24 2月, 2010 1 次提交
  11. 12 12月, 2009 1 次提交
  12. 12 11月, 2009 1 次提交
  13. 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
  14. 24 7月, 2009 1 次提交
  15. 23 6月, 2009 1 次提交
  16. 29 5月, 2009 3 次提交
  17. 07 8月, 2008 1 次提交
  18. 03 7月, 2008 3 次提交
  19. 09 2月, 2008 1 次提交
  20. 21 9月, 2007 1 次提交
  21. 09 5月, 2007 1 次提交
  22. 25 9月, 2006 2 次提交
  23. 27 6月, 2006 2 次提交
  24. 03 4月, 2006 1 次提交
  25. 04 1月, 2006 2 次提交
  26. 10 11月, 2005 1 次提交
  27. 08 9月, 2005 1 次提交
  28. 11 7月, 2005 1 次提交