1. 25 8月, 2009 3 次提交
  2. 21 8月, 2009 13 次提交
  3. 10 8月, 2009 3 次提交
  4. 07 8月, 2009 1 次提交
    • J
      ARM: OMAP: McBSP: Fix ASoC on OMAP1510 by fixing API of omap_mcbsp_start/stop · c12abc01
      Jarkko Nikula 提交于
      Simultaneous audio playback and capture on OMAP1510 can cause that second
      stream is stalled if there is enough delay between startup of the audio
      streams.
      
      Current implementation of the omap_mcbsp_start is starting both transmitter
      and receiver at the same time and it is called only for firstly started
      audio stream from the OMAP McBSP based ASoC DAI driver.
      
      Since DMA request lines on OMAP1510 are edge sensitive, the DMA request is
      missed if there is no DMA transfer set up at that time when the first word
      after McBSP startup is transmitted. The problem hasn't noted before since
      later OMAPs are using level sensitive DMA request lines.
      
      Fix the problem by changing API of omap_mcbsp_start and omap_mcbsp_stop by
      allowing to start and stop individually McBSP transmitter and receiver
      logics. Then call those functions individually for both audio playback
      and capture streams. This ensures that DMA transfer is setup before
      transmitter or receiver is started.
      
      Thanks to Janusz Krzysztofik <jkrzyszt@tis.icnet.pl> for detailed problem
      analysis and Peter Ujfalusi <peter.ujfalusi@nokia.com> for info about DMA
      request line behavior differences between the OMAP generations.
      Reported-and-tested-by: NJanusz Krzysztofik <jkrzyszt@tis.icnet.pl>
      Signed-off-by: NJarkko Nikula <jhnikula@gmail.com>
      Acked-by: NTony Lindgren <tony@atomide.com>
      Acked-by: NPeter Ujfalusi <peter.ujfalusi@nokia.com>
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      c12abc01
  5. 06 8月, 2009 3 次提交
  6. 05 8月, 2009 1 次提交
  7. 28 7月, 2009 2 次提交
  8. 25 7月, 2009 3 次提交
    • P
      OMAP2/3 clock: split, rename omap2_wait_clock_ready() · 72350b29
      Paul Walmsley 提交于
      Some OMAP2/3 hardware modules have CM_IDLEST attributes that are not
      handled by the current omap2_wait_clock_ready() code.  In preparation
      for patches that fix the unusual devices, rename the function
      omap2_wait_clock_ready() to omap2_wait_module_ready() and split it
      into three parts:
      
      1. A clkops-specific companion clock return function (by default,
         omap2_clk_dflt_find_companion())
      
      2. A clkops-specific CM_IDLEST register address and bit shift return
         function (by default, omap2_clk_dflt_find_idlest())
      
      3. Code to wait for the CM to indicate that the module is ready
         (omap2_cm_wait_idlest())
      
      Clocks can now specify their own custom find_companion() and find_idlest()
      functions; used in subsequent patches.
      Signed-off-by: NPaul Walmsley <paul@pwsan.com>
      72350b29
    • J
      OMAP3: Setup MUX settings for SDRC CKE signals · 9fb97412
      Jean Pihet 提交于
      This patches ensures the MUX settings are correct for the SDRC
      CKE signals to SDRAM. This allows the self-refresh to work when
      2 chip-selects are in use.
      
      A warning is thrown away in case the initial muxing is incorrect,
      in order to track faulty or old-dated bootloaders.
      Note: The CONFIG_OMAP_MUX and CONFIG_OMAP_MUX_WARNINGS options
      must be enabled for the mux code to have effect.
      Signed-off-by: NJean Pihet <jpihet@mvista.com>
      Signed-off-by: NPaul Walmsley <paul@pwsan.com>
      9fb97412
    • J
      OMAP3 SDRC: add support for 2 SDRAM chip selects · 58cda884
      Jean Pihet 提交于
      Some OMAP3 boards (Beagle Cx, Overo, RX51, Pandora) have 2
      SDRAM parts connected to the SDRC.
      
      This patch adds the following:
      - add a new argument of type omap_sdrc_params struct*
      to omap2_init_common_hw and omap2_sdrc_init for the 2nd CS params
      - adapted the OMAP boards files to the new prototype of
      omap2_init_common_hw
      - add the SDRC 2nd CS registers offsets defines
      - adapt the sram sleep code to configure the SDRC for the 2nd CS
      
      Note: If the 2nd param to omap2_init_common_hw is NULL, then the
      parameters are not programmed into the SDRC CS1 registers
      
      Tested on 3430 SDP and Beagleboard rev C2 and B5, with
      suspend/resume and frequency changes (cpufreq).
      Signed-off-by: NJean Pihet <jpihet@mvista.com>
      Signed-off-by: NPaul Walmsley <paul@pwsan.com>
      58cda884
  9. 24 7月, 2009 1 次提交
  10. 23 6月, 2009 6 次提交
  11. 20 6月, 2009 3 次提交
  12. 09 6月, 2009 1 次提交