From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter Ujfalusi <peter.ujfalusi@nokia.com>
Cc: alsa-devel@alsa-project.org, linux-omap@vger.kernel.org,
lrg@slimlogic.co.uk, jhnikula@gmail.com, tony@atomide.com,
ext-eero.nurkkala@nokia.com, eduardo.valentin@nokia.com
Subject: Re: [PATCH v3 0/5] OMAP/ASoC: McBSP: FIFO handling related fixes
Date: Tue, 1 Jun 2010 13:30:02 +0100 [thread overview]
Message-ID: <20100601123002.GC863@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1275391104-26387-1-git-send-email-peter.ujfalusi@nokia.com>
On Tue, Jun 01, 2010 at 02:18:19PM +0300, Peter Ujfalusi wrote:
> Changes since RFC v2:
> - Comments added explaining the changes, and documenting the API in patch2
> - In patch5:
> - Variable names changed in the hw_rule function
> - hw_rule function got renamed
> - The snd_pcm_hw_rule_add calls moved so it anly got set on OMAP3
All of these look sensible enough from an ASoC point of view, though I
can't say too much about the OMAP specifics.
Acked-by: Mark Brown <broonie@opensource.wolsfonmicro.com>
next prev parent reply other threads:[~2010-06-01 12:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 11:18 [PATCH v3 0/5] OMAP/ASoC: McBSP: FIFO handling related fixes Peter Ujfalusi
2010-06-01 11:18 ` [PATCH v3 1/5] OMAP: McBSP: Function to query the FIFO size Peter Ujfalusi
2010-06-01 11:18 ` [PATCH v3 2/5] OMAP2: McBSP: Change the way how the FIFO is handled Peter Ujfalusi
2010-06-01 11:18 ` [PATCH v3 3/5] OMAP2: McBSP: Use the port's buffer_size when calculating tx delay Peter Ujfalusi
2010-06-01 11:18 ` [PATCH v3 4/5] ASoC: omap-mcbsp: Save, and use wlen for threshold configuration Peter Ujfalusi
2010-06-01 11:18 ` [PATCH v3 5/5] ASoC: omap-mcbsp: Place correct constraints for streams Peter Ujfalusi
2010-06-01 12:19 ` Peter Ujfalusi
2010-06-01 11:40 ` [PATCH v3 0/5] OMAP/ASoC: McBSP: FIFO handling related fixes Jarkko Nikula
2010-06-01 12:30 ` Mark Brown [this message]
2010-06-02 9:05 ` [alsa-devel] " Peter Ujfalusi
2010-06-02 9:15 ` Liam Girdwood
2010-06-02 12:14 ` Peter Ujfalusi
2010-06-10 6:27 ` [alsa-devel] " Tony Lindgren
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=20100601123002.GC863@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=eduardo.valentin@nokia.com \
--cc=ext-eero.nurkkala@nokia.com \
--cc=jhnikula@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=peter.ujfalusi@nokia.com \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.