From: Jarkko Nikula <jhnikula@gmail.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: OMAP Linux discussion <linux-omap@vger.kernel.org>
Subject: Re: OMAP Audio
Date: Wed, 17 Feb 2010 09:03:39 +0200 [thread overview]
Message-ID: <20100217090339.c11d2e8a.jhnikula@gmail.com> (raw)
In-Reply-To: <4B7AE1AD.7080400@mlbassoc.com>
On Tue, 16 Feb 2010 11:19:25 -0700
Gary Thomas <gary@mlbassoc.com> wrote:
> I need to connect the OMAP (3530) to a 24bit CODEC. So far
> my attempts at getting this to go have not gone well. Then
> I ran across this comment in sound/soc/omap/omap-pcm.c:
> /*
> * Note: Regardless of interface data formats supported by OMAP McBSP
> * or EAC blocks, internal representation is always fixed 16-bit/sample
> */
>
> Does this mean that this setup is just not supported? even though
> the hardware can handle it?
>
Yep, comment is bit misleading but true until some patch will remove
it. IRCC, the EAC was limited to 16-bit and also there wasn't need and
HW to test other formats than S16_LE in McBSP DAI.
> Thanks for any pointers or ideas on how to get this going.
>
I would first start adding support for the S32_LE into omap-pcm.c (DMA
part). Worth to look this thread:
http://mailman.alsa-project.org/pipermail/alsa-devel/2010-January/024704.html
Then add support for this format to the omap-mcbsp.c (link
configuration part).
Next step would be to add support for the S24_LE on 4-byte boundaries.
I.e. the DMA is moving 32-bit samples between the memory and McBSP but
only 24-bits are transferred over the McBSP and codec.
--
Jarkko
next prev parent reply other threads:[~2010-02-17 6:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-16 18:19 OMAP Audio Gary Thomas
2010-02-17 7:03 ` Jarkko Nikula [this message]
2010-02-17 10:26 ` Peter Ujfalusi
2010-02-17 10:43 ` Gary Thomas
2010-02-17 11:17 ` Peter Ujfalusi
2010-02-17 12:01 ` Gary Thomas
2010-02-17 17:45 ` Jarkko Nikula
2010-02-17 17:51 ` Gary Thomas
2010-02-17 17:56 ` Mark Brown
2010-02-17 18:01 ` Gary Thomas
2010-02-26 10:09 ` Stehle, Vincent
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=20100217090339.c11d2e8a.jhnikula@gmail.com \
--to=jhnikula@gmail.com \
--cc=gary@mlbassoc.com \
--cc=linux-omap@vger.kernel.org \
/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.