From: Jarkko Nikula <jhnikula@gmail.com>
To: Liam Girdwood <lrg@slimlogic.co.uk>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
Brown <broonie@opensource.wolfsonmicro.com>,
Peter Ujfalusi <peter.ujfalusi@nokia.com>,
Mark@alsa-project.org, Graeme Gregory <gg@slimlogic.co.uk>,
Grazvydas Ignotas <notasas@gmail.com>
Subject: Re: [PATCH V2] ASoC - Add support for upto 16 channels on OMAP MCBSP
Date: Mon, 9 Nov 2009 08:57:22 +0200 [thread overview]
Message-ID: <20091109085722.49d40bd8.jhnikula@gmail.com> (raw)
In-Reply-To: <1257712022.15162.2.camel@vega>
On Sun, 08 Nov 2009 20:27:01 +0000
Liam Girdwood <lrg@slimlogic.co.uk> wrote:
> > Seems to be working fine, tried playing several different sample rates
> > and also recording path. FYI pandora has TWL4030 256FS clock connected
> > to OMAP's CLKS pin.
> >
> > Tested-by: Grazvydas Ignotas <notasas@gmail.com>
>
> Jarkko, Peter,
>
> Any chance we could have your Ack before applying.
>
Definitely. I just sent a patch which must be applied before yours to
the Pandora. It is otherwise the same than I sent before but now with
commit log and 8*32 replaced with 256.
Mark: The omap3pandora.c must be patches before Liam's patch.
http://mailman.alsa-project.org/pipermail/alsa-devel/2009-November/022921.html
http://mailman.alsa-project.org/pipermail/alsa-devel/2009-November/022797.html
Acked-by: Jarkko Nikula <jhnikula@gmail.com>
next prev parent reply other threads:[~2009-11-09 6:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-05 21:00 [PATCH V2] ASoC - Add support for upto 16 channels on OMAP MCBSP Liam Girdwood
2009-11-06 18:24 ` Jarkko Nikula
2009-11-07 20:11 ` Grazvydas Ignotas
2009-11-08 20:27 ` Liam Girdwood
2009-11-09 6:57 ` Jarkko Nikula [this message]
2009-11-09 7:24 ` Peter Ujfalusi
2009-11-09 6:57 ` Peter Ujfalusi
2009-11-09 7:29 ` Peter Ujfalusi
2009-11-09 7:47 ` Jarkko Nikula
2009-11-09 8:14 ` Jarkko Nikula
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=20091109085722.49d40bd8.jhnikula@gmail.com \
--to=jhnikula@gmail.com \
--cc=Mark@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=gg@slimlogic.co.uk \
--cc=lrg@slimlogic.co.uk \
--cc=notasas@gmail.com \
--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