[alsa-devel] davici-mcasp: "tx-num-evt" confusion with number of serializers
michal.bachraty at streamunlimited.com
Wed Feb 27 12:36:54 CET 2013
Thanks for your opinion.
> From what I remember (I'm using the davinci to record from up to 8
> codecs chips simultaneously) the value sets a threshold for the DMA
> request (if the FIFO is enabled - and I can't think of a reason why
> anyone would NOT want to enable the fifo...).
Can you tell me, which processor are you using, how many serializers (data
lines) do you use and which mode are you using (TDM - I2S?)?
> Postponing the DMA request until there are #channels data entries in the
> fifo buffer makes sense to me. Setting the txnumevt to a higher value
> might reduce the load on the memory controller (that's what TI claims),
> at the cost of a higher risk of overrunning the fifo, and increased
> latency. Setting it to less than the number of channels isn't useful
> either - which application would be interested in "half" the channel data?
AM335x FIFO waits for data for all enabled serializers. For I2S format, there
are two (L/R) data samples for one sampling time. This data are sended one
after another to dataline. Therefore Am335x serializer need only "half"sample
data, but it works in double sampling time frequency. When more than two
channels will be used, for example four, then two serializers are enabled. For
this example, FIFO need to be filled with two samples in one DMA frame, each
for one serializer. If not, no DMA event is generated.
More information about the Alsa-devel