On Wed, 17 Feb 2010 05:01:53 -0700 Gary Thomas <[email protected]> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
