From: Jarkko Nikula <jhnikula@gmail.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Peter Ujfalusi <peter.ujfalusi@nokia.com>,
OMAP Linux discussion <linux-omap@vger.kernel.org>
Subject: Re: OMAP Audio
Date: Wed, 17 Feb 2010 19:45:01 +0200 [thread overview]
Message-ID: <20100217194501.7e49ac0c.jhnikula@gmail.com> (raw)
In-Reply-To: <4B7BDAB1.3020503@mlbassoc.com>
On Wed, 17 Feb 2010 05:01:53 -0700
Gary Thomas <gary@mlbassoc.com> wrote:
> > After looking at the TRM of OMAP, the sDMA has support for 8, 16 and 32 bit data
> > types. So I'm not really sure how to configure McBSP and sDMA in case of 24 bit
> > packed format.
> > I would go with a trial and error method and find it out how it is working...
> >
So it looks that the memory representation must be 32-bit.
> How about sending padded data (24 bits in 32) which is what my
> CODEC wants anyway? Would this be easier to set up? How?
>
> (Again, I'm a bit fuzzy on how to tell omap_pcm_prepare that I
> need to be moving 24 or 32 bit chunks)
>
Internal representation and link configuration are separate things:
DMA <-> McBSP rx/tx reg <- [FIFO] -> McBSP receiver/transmitter
As Peter found, due the DMA and McBSP FIFO, the DMA configuration must
be 32-bit. But I suppose the McBSP receiver/ransmitter could be
configured to transmit only 24-bits.
The OMAP35x Applications Processor Multi-Channel Buffered Serial Port
(McBSP) TRM (SPRUFD1C) seems to have some examples for different data
lengths than internal word length. Worth to look and try with trial and
error method using oscilloscope :-)
--
Jarkko
next prev parent reply other threads:[~2010-02-17 17:39 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 [this message]
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=20100217194501.7e49ac0c.jhnikula@gmail.com \
--to=jhnikula@gmail.com \
--cc=gary@mlbassoc.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