public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Nikula <jhnikula@gmail.com>
To: Peter Ujfalusi <peter.ujfalusi@nokia.com>
Cc: "Valentin Eduardo (Nokia-D/Helsinki)"
	<eduardo.valentin@nokia.com>,
	Linux-OMAP <linux-omap@vger.kernel.org>,
	ALSA-Devel <alsa-devel@vger.kernel.org>,
	"Nurkkala Eero.An (EXT-Offcode/Oulu)"
	<ext-Eero.Nurkkala@nokia.com>
Subject: Re: [PATCHv3 00/20] OMAP ASoC changes in DMA utilization
Date: Mon, 17 Aug 2009 12:07:37 +0300	[thread overview]
Message-ID: <20090817120737.caff7f92.jhnikula@gmail.com> (raw)
In-Reply-To: <200908171122.30731.peter.ujfalusi@nokia.com>

On Mon, 17 Aug 2009 11:22:30 +0300
Peter Ujfalusi <peter.ujfalusi@nokia.com> wrote:

> On Thursday 13 August 2009 17:35:13 Valentin Eduardo (Nokia-D/Helsinki) wrote:
> > Hello again guys,
> >
> > Here is version 3 of these changes. I've changed just 2
> > things:
> > - all mcbsp instances are in element mode by default
> > - moved all mcbsp related code to omap-mcbsp.c
> > (although a single callback is still needed)
> >
> > Jarkko, I think we can add your patch for reading strings
> > for dma op mode later on.
> 
> In my opinion we can take this series as it is now, what do you think Jarkko?
> At least I don't see too (any?) big problems with it...
> 
Good to remind me. I was almost making a reviewing to this and Janusz's
patches yesterday but ended up testing the MUSB and watching some
aircrafts instead :-)

But shortly going through the 3rd version of the set, only major issue I
point that it's not based on top of my patch below so most probably
patches 4 and 18 don't apply. Also changed API of
omap_mcbsp_start/-stop would allow to remove new exported functions
omap_mcbsp_xmit_enable and omap_mcbsp_recv_enable.

commit c12abc012e18b362204345c323536f228d65c4db
Author: Jarkko Nikula <jhnikula@gmail.com>
Date:   Fri Aug 7 09:59:47 2009 +0300

    ARM: OMAP: McBSP: Fix ASoC on OMAP1510 by fixing API of
omap_mcbsp_start/sto 

Otherwise set looks fine since omap-mcbp.c and omap-pcm.c are not hard
glued together and the element mode is the default.


-- 
Jarkko

  reply	other threads:[~2009-08-17  9:06 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-13 14:35 [PATCHv3 00/20] OMAP ASoC changes in DMA utilization Eduardo Valentin
2009-08-13 14:35 ` [PATCHv3 01/20] OMAP: McBSP: Provide functions for ASoC frame syncronization Eduardo Valentin
2009-08-13 14:35   ` [PATCHv3 02/20] OMAP: McBSP: Add IRQEN, IRQSTATUS, THRESHOLD2 and THRESHOLD1 registers Eduardo Valentin
2009-08-13 14:35     ` [PATCHv3 03/20] OMAP: McBSP: Use appropriate value for startup delay Eduardo Valentin
2009-08-13 14:35       ` [PATCHv3 04/20] OMAP: McBSP: Add transmit/receive threshold handler Eduardo Valentin
2009-08-13 14:35         ` [PATCHv3 05/20] OMAP: McBSP: Create and export max_(r|t)x_thres property Eduardo Valentin
2009-08-13 14:35           ` [PATCHv3 06/20] OMAP3: McBSP: Lower the maximum buffersize for McBSP1,3,4,5 Eduardo Valentin
2009-08-13 14:35             ` [PATCHv3 07/20] OMAP: McBSP: Rename thres sysfs symbols Eduardo Valentin
2009-08-13 14:35               ` [PATCHv3 08/20] OMAP: McBSP: Add link DMA mode selection Eduardo Valentin
2009-08-13 14:35                 ` [PATCHv3 09/20] OMAP: McBSP: Wakeups utilized Eduardo Valentin
2009-08-13 14:35                   ` [PATCHv3 10/20] OMAP: McBSP: Change wakeup signals Eduardo Valentin
2009-08-13 14:35                     ` [PATCHv3 11/20] OMAP: McBSP: Retain McBSP FCLK clockactivity Eduardo Valentin
2009-08-13 14:35                       ` [PATCHv3 12/20] OMAP: McBSP: Configure NO IDLE mode for DMA mode different of threshold Eduardo Valentin
2009-08-13 14:35                         ` [PATCHv3 13/20] OMAP: McBSP: Do not enable wakeups for no-idle mode Eduardo Valentin
2009-08-13 14:35                           ` [PATCHv3 14/20] OMAP: McBSP: Let element DMA mode hit retention also Eduardo Valentin
2009-08-13 14:35                             ` [PATCHv3 15/20] ASoC: OMAP: Make DMA 64 aligned Eduardo Valentin
2009-08-13 14:35                               ` [PATCHv3 16/20] ASoC: OMAP: Enable DMA burst mode Eduardo Valentin
2009-08-13 14:35                                 ` [PATCHv3 17/20] ASoC: Add runtime check for RFIG and XFIG Eduardo Valentin
2009-08-13 14:35                                   ` [PATCHv3 18/20] ASoC: Always syncronize audio transfers on frames Eduardo Valentin
2009-08-13 14:35                                     ` [PATCHv3 19/20] ASoC: OMAP: Use McBSP threshold to playback and capture Eduardo Valentin
2009-08-13 14:35                                       ` [PATCHv3 20/20] ASoC: OMAP: Use DMA operating mode of McBSP Eduardo Valentin
2009-08-14  3:19                             ` [PATCHv3 14/20] OMAP: McBSP: Let element DMA mode hit retention also Woodruff, Richard
2009-08-14  4:40                               ` Eero Nurkkala
2009-08-17  8:22 ` [PATCHv3 00/20] OMAP ASoC changes in DMA utilization Peter Ujfalusi
2009-08-17  9:07   ` Jarkko Nikula [this message]
2009-08-17 11:36     ` Eduardo Valentin
2009-08-17 11:52       ` Mark Brown
2009-08-17 11:45         ` Eduardo Valentin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090817120737.caff7f92.jhnikula@gmail.com \
    --to=jhnikula@gmail.com \
    --cc=alsa-devel@vger.kernel.org \
    --cc=eduardo.valentin@nokia.com \
    --cc=ext-Eero.Nurkkala@nokia.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=peter.ujfalusi@nokia.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox