From: Gary Thomas <gary@mlbassoc.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Jarkko Nikula <jhnikula@gmail.com>,
Peter Ujfalusi <peter.ujfalusi@nokia.com>,
OMAP Linux discussion <linux-omap@vger.kernel.org>
Subject: Re: OMAP Audio
Date: Wed, 17 Feb 2010 11:01:53 -0700 [thread overview]
Message-ID: <4B7C2F11.3010008@mlbassoc.com> (raw)
In-Reply-To: <20100217175602.GG2032@sirena.org.uk>
On 02/17/2010 10:56 AM, Mark Brown wrote:
> On Wed, Feb 17, 2010 at 10:51:11AM -0700, Gary Thomas wrote:
>
>> Thanks. I'd really like to understand how to set things up to generate
>> the data I see in TRM:
>> Figure 21-11 shows an example with 24 bits data (MSB first) and 8 padding bits at ?0?.
>>
>> This matches my CODEC. Any clues?
>
> Does your CODEC actually need the padding bits to be zero? What you're
> describing sounds an awful lot like 32 bit data that just has the LSB
> ignored.
I don't think it matters. The real problem is how to get 24 bits
of data aligned to the right place in the 32 bit frame. TRM implies
that the hardware can do this, I've just not figured out the magic...
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2010-02-17 18:01 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
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 [this message]
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=4B7C2F11.3010008@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jhnikula@gmail.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