From: Ryan Mallon <ryan@bluewatersys.com>
To: Liam Girdwood <lrg@slimlogic.co.uk>,
Russell King <rmk@arm.linux.org.uk>,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: john.cooper@third-harmonic.com, alsa-devel@alsa-project.org,
chasedouglas@gmail.com, buytenh@wantstofly.org,
r&d4@dave-tech.it, hartleys@visionengravers.com,
marshall@coolbananas.co.nz, linux-arm-kernel@lists.infradead.org,
dhuggins@cs.cmu.edu
Subject: Re: [RFC PATCH v3 0/3] ep93xx i2s audio
Date: Tue, 08 Jun 2010 08:38:19 +1200 [thread overview]
Message-ID: <4C0D58BB.5030505@bluewatersys.com> (raw)
In-Reply-To: <1275914732.3045.105.camel@odin>
Liam Girdwood wrote:
> On Fri, 2010-06-04 at 17:11 +1200, Ryan Mallon wrote:
>> The following patch series adds support for i2s audio on the ep93xx,
>> with the Snapper CL15 used as an example implementation.
>>
>> This version fixes a number of things from the previous round:
>> - Removed unused #defines
>> - Set symmetric rates for the cpu dai
>> - Fixed the sdiv/lrdiv calculation loop
>> - Moved the cpu dai registration
>> - Removed empty ep93xx_pcm_prepare callback
>> - Fixed enable/disable when both capture and playback are running
>>
>> Capture still does not work. The dma is running, but the captured data
>> is all zeros (tested used arecord and loopback). I have a 2.6.20
>> kernel with ep93xx i2s audio working an capture works there on the
>> same hardware. I have spent sometime looking into this, but can't see
>> the problem. Would appreciate if someone can lend some insight as to
>> what I have done wrong.
>>
>> Ryan Mallon (3):
>> ep93xx i2s core support
>> ep93xx i2s audio driver
>> Snapper cl15 audio support
>
> All
>
> Acked-by: Liam Girdwood <lrg@slimlogic.co.uk>
Russell, Mark has picked up patch 2/3 via the alsa tree. Should I submit
1/3 and 3/3 via the arm patch system with Liam's ack?
Thanks,
~Ryan
--
Bluewater Systems Ltd - ARM Technology Solution Centre
Ryan Mallon 5 Amuri Park, 404 Barbadoes St
ryan@bluewatersys.com PO Box 13 889, Christchurch 8013
http://www.bluewatersys.com New Zealand
Phone: +64 3 3779127 Freecall: Australia 1800 148 751
Fax: +64 3 3779135 USA 1800 261 2934
WARNING: multiple messages have this Message-ID (diff)
From: ryan@bluewatersys.com (Ryan Mallon)
To: linux-arm-kernel@lists.infradead.org
Subject: [alsa-devel] [RFC PATCH v3 0/3] ep93xx i2s audio
Date: Tue, 08 Jun 2010 08:38:19 +1200 [thread overview]
Message-ID: <4C0D58BB.5030505@bluewatersys.com> (raw)
In-Reply-To: <1275914732.3045.105.camel@odin>
Liam Girdwood wrote:
> On Fri, 2010-06-04 at 17:11 +1200, Ryan Mallon wrote:
>> The following patch series adds support for i2s audio on the ep93xx,
>> with the Snapper CL15 used as an example implementation.
>>
>> This version fixes a number of things from the previous round:
>> - Removed unused #defines
>> - Set symmetric rates for the cpu dai
>> - Fixed the sdiv/lrdiv calculation loop
>> - Moved the cpu dai registration
>> - Removed empty ep93xx_pcm_prepare callback
>> - Fixed enable/disable when both capture and playback are running
>>
>> Capture still does not work. The dma is running, but the captured data
>> is all zeros (tested used arecord and loopback). I have a 2.6.20
>> kernel with ep93xx i2s audio working an capture works there on the
>> same hardware. I have spent sometime looking into this, but can't see
>> the problem. Would appreciate if someone can lend some insight as to
>> what I have done wrong.
>>
>> Ryan Mallon (3):
>> ep93xx i2s core support
>> ep93xx i2s audio driver
>> Snapper cl15 audio support
>
> All
>
> Acked-by: Liam Girdwood <lrg@slimlogic.co.uk>
Russell, Mark has picked up patch 2/3 via the alsa tree. Should I submit
1/3 and 3/3 via the arm patch system with Liam's ack?
Thanks,
~Ryan
--
Bluewater Systems Ltd - ARM Technology Solution Centre
Ryan Mallon 5 Amuri Park, 404 Barbadoes St
ryan at bluewatersys.com PO Box 13 889, Christchurch 8013
http://www.bluewatersys.com New Zealand
Phone: +64 3 3779127 Freecall: Australia 1800 148 751
Fax: +64 3 3779135 USA 1800 261 2934
next prev parent reply other threads:[~2010-06-07 20:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 5:11 [RFC PATCH v3 0/3] ep93xx i2s audio Ryan Mallon
2010-06-04 5:11 ` Ryan Mallon
2010-06-04 5:11 ` [RFC PATCH v3 1/3] ep93xx i2s core support Ryan Mallon
2010-06-04 5:11 ` Ryan Mallon
2010-06-04 5:11 ` [RFC PATCH v3 2/3] ep93xx i2s audio driver Ryan Mallon
2010-06-04 5:11 ` Ryan Mallon
2010-06-04 5:11 ` [RFC PATCH v3 3/3] Snapper cl15 audio support Ryan Mallon
2010-06-04 5:11 ` Ryan Mallon
2010-06-07 21:55 ` [RFC PATCH v3 1/3] ep93xx i2s core support H Hartley Sweeten
2010-06-07 21:55 ` H Hartley Sweeten
2010-06-07 22:21 ` Ryan Mallon
2010-06-07 22:21 ` Ryan Mallon
2010-06-07 12:45 ` [RFC PATCH v3 0/3] ep93xx i2s audio Liam Girdwood
2010-06-07 12:45 ` [alsa-devel] " Liam Girdwood
2010-06-07 20:38 ` Ryan Mallon [this message]
2010-06-07 20:38 ` Ryan Mallon
2010-06-07 23:52 ` Mark Brown
2010-06-07 23:52 ` [alsa-devel] " Mark Brown
2010-06-08 0:38 ` Ryan Mallon
2010-06-08 0:38 ` [alsa-devel] " Ryan Mallon
2010-06-07 13:26 ` Mark Brown
2010-06-07 13:26 ` [alsa-devel] " Mark Brown
2010-06-07 20:35 ` Ryan Mallon
2010-06-07 20:35 ` [alsa-devel] " Ryan Mallon
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=4C0D58BB.5030505@bluewatersys.com \
--to=ryan@bluewatersys.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=buytenh@wantstofly.org \
--cc=chasedouglas@gmail.com \
--cc=dhuggins@cs.cmu.edu \
--cc=hartleys@visionengravers.com \
--cc=john.cooper@third-harmonic.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lrg@slimlogic.co.uk \
--cc=marshall@coolbananas.co.nz \
--cc=r&d4@dave-tech.it \
--cc=rmk@arm.linux.org.uk \
/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.