1. 25 8月, 2009 1 次提交
  2. 21 8月, 2009 8 次提交
  3. 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
  4. 28 7月, 2009 1 次提交
  5. 09 2月, 2009 1 次提交
    • R
      [ARM] omap: mcbsp: convert to use fck/ick clocks directly · b820ce4e
      Russell King 提交于
      Rather than introducing a special 'mcbsp_clk' with code behind it in
      mach-omap*/mcbsp.c to handle the SoC specifics, arrange for the mcbsp
      driver to be like any other driver.  mcbsp requests its fck and ick
      clocks directly, and the SoC specific code deals with selecting the
      correct clock.
      
      There is one oddity to deal with - OMAP1 fiddles with the DSP clocks
      and DSP reset, so we move this to the two callback functions.
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      b820ce4e
  6. 30 1月, 2009 1 次提交
    • S
      ARM: OMAP: Fix McBSP spin_lock deadlock · 06151158
      Stanley.Miao 提交于
      A spin_lock deadlock will occur when omap_mcbsp_request() is invoked.
      
      omap_mcbsp_request()
      \- clk_enable(mcbsp->clk)         [takes and holds clockfw_lock]
          \- omap2_clk_enable()
             \- _omap2_clk_enable()
                 \- omap_mcbsp_clk_enable()
                    \- clk_enable(child clock)   [tries for clockfw_lock again]
      
      mcbsp_clk is a virtual clock and it comprises several child clocks. when
      enable mcbsp_clk in omap_mcbsp_request(), the enable function of mcbsp_clk
      will enable its child clocks, then the deadlock occurs.
      
      The solution is to remove the virtual clock and enable these child clocks in
      omap_mcbsp_request() directly.
      Signed-off-by: NStanley.Miao <stanley.miao@windriver.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      
      
      06151158
  7. 15 1月, 2009 1 次提交
    • T
      ARM: OMAP: Fix ASoC by enabling writes to XCCR and RCCR McBSP registers, v3 · 3127f8f8
      Tony Lindgren 提交于
      This patch enables writing to McBSP Transmit Configuration Control
      Register (XCCR) and Receive Configuration Control Register (RCCR)
      for 2430/34xx platforms. It also adds XCCR, RCCR entries in McBSP
      register configuration structure and bit definitions for both
      registers.
      
      If we enable the writing to CCR registers for 2430/34xx and don't
      set the default values (setting 0 as a consequence) in ASoC driver,
      the Transmit/Receive DMA mode gets disabled and the the
      transmission/reception doesn't happen, ending with a
      "write error: Input/Output error" when playing with 'aplay'.
      
      Also define dummy CCR registers for omap1.
      
      Cc: Jarkko Nikula <jarkko.nikula@nokia.com>
      Signed-off-by: NMisael Lopez Cruz <x0052729@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      
      
      
      
      3127f8f8
  8. 09 10月, 2008 1 次提交
    • S
      ARM: OMAP3: Add minimal omap3430 support · cc26b3b0
      Syed Mohammed, Khasim 提交于
      Add minimal omap3430 support based on earlier patches from
      Syed Mohammed Khasim. Also merge in omap34xx SRAM support
      from Karthik Dasu and use consistent naming for sram init
      functions.
      
      Also do following changes that make 34xx support usable:
      
      - Remove unused sram.c functions for 34xx
      
      - Rename IRQ_SIR_IRQ to INTCPS_SIR_IRQ and define it locally
        in entry-macro.S
      
      - Update mach-omap2/io.c to support 2420, 2430, and 34xx
      
      - Also merge in 34xx GPMC changes to add fields wr_access and
        wr_data_mux_bus from Adrian Hunter
      
      - Remove memory initialization call omap2_init_memory() until
        until more generic memory initialization patches are posted.
        It's OK to rely on bootloader initialization until then.
      Signed-off-by: NSyed Mohammed, Khasim <khasim@ti.com>
      Signed-off-by: Karthik Dasu<karthik-dp@ti.com>
      Signed-off-by: NAdrian Hunter <ext-adrian.hunter@nokia.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      
      
      
      cc26b3b0
  9. 08 10月, 2008 3 次提交
  10. 06 9月, 2008 1 次提交
  11. 05 9月, 2008 1 次提交
  12. 07 8月, 2008 2 次提交
  13. 03 7月, 2008 1 次提交
  14. 04 10月, 2006 1 次提交
  15. 03 4月, 2006 1 次提交
  16. 16 11月, 2005 1 次提交
  17. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4